I am really new to the puppet code base and could use some help. Could someone provide me with a working knowledge of how the indirector defines and provides termini ?
If you are looking to submit code back into the core, please take a
look at the CONTRIBUTING.md document for some of the guidelines for
submitting code.
> I am really new to the puppet code base and could use some help. Could
> someone provide me with a working knowledge of how the indirector defines
> and provides termini ?
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-dev/-/L_EyS--EnZ4J.
> To post to this group, send email to puppet-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
Thanks for the quick reply and useful information.
I have read contributing.md and, while I would love to start committing code, I need to take some more time to look at the source (-_-). I hope to help out real soon.
On Thursday, August 9, 2012 2:35:27 PM UTC-7, Andy Parker wrote:
> Hi Kevin,
> Glad you are interested in hacking on the puppet codebase. The > indirector is not really well documented, unfortunately. The best > thing out there that I know of is Brice's write up on puppet extension > points: > http://www.masterzen.fr/2011/12/11/the-indirector-puppet-extensions-p...
> If you are looking to submit code back into the core, please take a > look at the CONTRIBUTING.md document for some of the guidelines for > submitting code.
> Andy
> On Thu, Aug 9, 2012 at 11:27 AM, kp-v > <kevin.grenvi...@gmail.com <javascript:>> wrote: > > Hey folks;
> > I am really new to the puppet code base and could use some help. Could > > someone provide me with a working knowledge of how the indirector > defines > > and provides termini ?
> > -- > > You received this message because you are subscribed to the Google > Groups > > "Puppet Developers" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/puppet-dev/-/L_EyS--EnZ4J. > > To post to this group, send email to puppe...@googlegroups.com<javascript:>.
> > To unsubscribe from this group, send email to > > puppet-dev+...@googlegroups.com <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/puppet-dev?hl=en.
kp-v wrote:
> Thanks for the quick reply and useful information.
> I have read contributing.md and, while I would love to start committing
> code, I need to take some more time to look at the source (-_-). I hope
> to help out real soon.
Hi Kevin
What were you planning to add or change about the indirector? Perhaps
there is some code we can point you at?
Regards
James
-- James Turnbull
Puppet Labs
1-503-734-8571
To schedule a meeting with me: http://tungle.me/jamtur01
I was originally coming at this because of an issue with an implementation I was working on. I was working off of 2.6.16 and decided I wanted to try and /opt install of puppet. To make a long story short, puppet was only searching /etc/puppet/auth.conf for the ACL file and not /opt directory. Anyhow, I figured my problem was something to do with the indirector not specifying the correct terminus point. Eventually I submitted that the easiest way was to symlink my ACL file to the /etc/puppet/auth.conf; however this defeats the purpose of a /opt dir install and would be wrong sysadmin-fu. I figured it would be nice to document this and perhaps prepare a patch for any adventurous puppet professionals/enthusiasts who think shooting themselves in the foot is fun.
I am a big fan of IT automation and would love to help contribute in any way I can. It would be great if you could point out any issues that have been on the back burner for some time and need hacking apart.
On Friday, August 10, 2012 6:29:12 PM UTC-7, James Turnbull wrote:
> kp-v wrote: > > Thanks for the quick reply and useful information.
> > I have read contributing.md and, while I would love to start > committing > > code, I need to take some more time to look at the source (-_-). I hope > > to help out real soon.
> Hi Kevin
> What were you planning to add or change about the indirector? Perhaps > there is some code we can point you at?
> Regards
> James
> -- > James Turnbull > Puppet Labs > 1-503-734-8571 > To schedule a meeting with me: http://tungle.me/jamtur01
<kevin.grenville.phill...@gmail.com> wrote:
> I was originally coming at this because of an issue with an implementation I
> was working on. I was working off of 2.6.16 and decided I wanted to try and
> /opt install of puppet. To make a long story short, puppet was only
> searching /etc/puppet/auth.conf for the ACL file and not /opt directory.
> Anyhow, I figured my problem was something to do with the indirector not
> specifying the correct terminus point. Eventually I submitted that the
> easiest way was to symlink my ACL file to the /etc/puppet/auth.conf; however
> this defeats the purpose of a /opt dir install and would be wrong
> sysadmin-fu. I figured it would be nice to document this and perhaps prepare
> a patch for any adventurous puppet professionals/enthusiasts who think
> shooting themselves in the foot is fun.
Hmm, I would have expected the --confdir parameter to change it to
look in the right directory.
> I am a big fan of IT automation and would love to help contribute in any way
> I can. It would be great if you could point out any issues that have been on
> the back burner for some time and need hacking apart.
Looking at the open tickets in Redmine and picking something that
seems like you might
know something about is a great way to start. There is a large number
in there of varying
levels of difficulty. If you have access to platforms that may not be
very easy for us to get at
(AIX, HP-UX, less common BSDs or Linuxes), then that might be a great
place to start.
> On Friday, August 10, 2012 6:29:12 PM UTC-7, James Turnbull wrote:
>> kp-v wrote:
>> > Thanks for the quick reply and useful information.
>> > I have read contributing.md and, while I would love to start committing
>> > code, I need to take some more time to look at the source (-_-). I hope
>> > to help out real soon.
>> Hi Kevin
>> What were you planning to add or change about the indirector? Perhaps
>> there is some code we can point you at?
>> Regards
>> James
>> --
>> James Turnbull
>> Puppet Labs
>> 1-503-734-8571
>> To schedule a meeting with me: http://tungle.me/jamtur01
> To post to this group, send email to puppet-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
<kevin.grenville.phill...@gmail.com> wrote:
> I was originally coming at this because of an issue with an implementation I
> was working on. I was working off of 2.6.16 and decided I wanted to try and
> /opt install of puppet. To make a long story short, puppet was only
> searching /etc/puppet/auth.conf for the ACL file and not /opt directory.
I'll try and chase it down, but I'm pretty sure we had a bug at that
point in time with the install.rb --destdir option, and auth.conf not
honoring it correctly.
Is that how you were installing Puppet rooted at /opt ?
> Anyhow, I figured my problem was something to do with the indirector not
> specifying the correct terminus point. Eventually I submitted that the
> easiest way was to symlink my ACL file to the /etc/puppet/auth.conf; however
> this defeats the purpose of a /opt dir install and would be wrong
> sysadmin-fu. I figured it would be nice to document this and perhaps prepare
> a patch for any adventurous puppet professionals/enthusiasts who think
> shooting themselves in the foot is fun.
> I am a big fan of IT automation and would love to help contribute in any way
> I can. It would be great if you could point out any issues that have been on
> the back burner for some time and need hacking apart.
> On Friday, August 10, 2012 6:29:12 PM UTC-7, James Turnbull wrote:
>> kp-v wrote:
>> > Thanks for the quick reply and useful information.
>> > I have read contributing.md and, while I would love to start committing
>> > code, I need to take some more time to look at the source (-_-). I hope
>> > to help out real soon.
>> Hi Kevin
>> What were you planning to add or change about the indirector? Perhaps
>> there is some code we can point you at?
>> Regards
>> James
>> --
>> James Turnbull
>> Puppet Labs
>> 1-503-734-8571
>> To schedule a meeting with me: http://tungle.me/jamtur01
> To post to this group, send email to puppet-dev@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
> I'll try and chase it down, but I'm pretty sure we had a bug at that
> point in time with the install.rb --destdir option, and auth.conf not
> honoring it correctly.
I will try and chase down the old bug to see if it is similar to this issue. I will post here when/if I find it and an analysis whether the issue is a bug or user snafu.
> Is that how you were installing Puppet rooted at /opt ?
I rooted the install.rb to /opt. I specified --confdir --usrdir --bindir --destdir.
>> I'll try and chase it down, but I'm pretty sure we had a bug at that
>> point in time with the install.rb --destdir option, and auth.conf not
>> honoring it correctly.
> I will try and chase down the old bug to see if it is similar to this issue. I will post here when/if I find it and an analysis whether the issue is a bug or user snafu.
>> Is that how you were installing Puppet rooted at /opt ?
> I rooted the install.rb to /opt. I specified --confdir --usrdir --bindir --destdir.
Ugh. Looks like this might not actually be fixed...
