As jieryn wrote, this is not a topic for the dev list.

> On 07.10.2016, at 07:23, Irfan Sayed <[email protected]> wrote:
> 
> i am extending this to puppet,chef and ansible as well.
> All these tools requires bootstrapping (irrespective of agentless/agentfull 
> design)
> 
> regards,
> 
> On Sun, Sep 25, 2016 at 7:31 PM, Irfan Sayed <[email protected]> wrote:
> thanks.
> roughly, this is how it will work.
> plugin will
>       • contact puppetmaster using some protocol ssh, com.dcom (windows)
>       • download the certificate 
>       • run few commands and register the node with puppet master 
>       • will accept the array (node list). this may accept the Jenkins build 
> slaves list as well to be bootstrapped
> plz suggest 
> regards
> 
> 
> On Sat, Sep 24, 2016 at 12:06 AM, jieryn <[email protected]> wrote:
> First, this probably should be on the -user list.
> 
> Second, it seems strange to me to have a non-bootstrapped node which
> already has Jenkins on it.
> 
> 
> On Fri, Sep 23, 2016 at 2:29 PM, Irfan Sayed <[email protected]> wrote:
> > please suggest
> > Regards
> >
> >
> > On Fri, Sep 23, 2016 at 11:23 AM, Irfan Sayed <[email protected]> wrote:
> >>
> >> Hi,
> >> Is it worth enough to have/write plugin to bootstrap the puppet node and
> >> register with puppet master.
> >>
> >> following use case planning to include:
> >>
> >> provision the node and bootstrap
> >>
> >> bare metal provisioning using razor can be included
> >>
> >> consider puppet master as a CA server for authentication
> >> parallel bootstrap for "n" nodes
> >>
> >> just wanted to get the expert feedback from you folks before i attemt to
> >> do something.
> >>
> >> plz suggest
> >> Regards,
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJbypBJb1Vm5HSzrK8ZqCzto8wG2SBshSJ%3DoybTG4tt02w%40mail.gmail.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYaNrpf7%2B6jJNEuZ3xZp6rW1ug75EeqXURbegYtBEP1%3DA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJbLHeHEPsoyb2YvmrTkqLTC5e1%3DNW0rrA-wEHbkr6rQXQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D37FE2DE-AA18-47E5-8E2A-0CC5174AA482%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to