Puppet users - Nov 2010 - preferred directory structure for multiple environments

Hello All,

Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred
directory structure for using multiple environments? Does it work much
different in 2.6 than in 2.5? When I made the move I assumed (I know)
that my current structure and configurations would just roll over but
that isn''t the case.

Thanks,

Jim

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

techn0gichida <jglouisjr@gmail.com> writes:
> Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred
> directory structure for using multiple environments? Does it work much
> different in 2.6 than in 2.5?
Not really substantially, no.
> When I made the move I assumed (I know) that my current structure and
> configurations would just roll over but that isn''t the case.
It would be super-great if you could let us know what the problems were.
(Perhaps you have in other messages, but better to ask twice than never hear
 what problems folks are hitting, I figure. :)

Regards,
        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Thanks Daniel,

in puppet.conf on the server: (we are just trying to get a file installed to
the int environment client)

[main]
    vardir = /var/lib/puppet
    logdir = /var/log/puppet
    rundir = /var/run/puppet
    ssldir = $vardir/ssl
    pidfile=$rundir/puppetmaster.pid

[int]
#    modulepath = /etc/puppet/modules/int
#    manifest = /etc/puppet/manifests/int/site.pp
manifest = /etc/puppet/int/site.pp
modulepath = /etc/puppet/int/modules

[pfm]
    modulepath = /etc/puppet/modules/pfm
    manifest = /etc/puppet/manifests/pfm/site.pp

[site2]
    modulepath = /etc/puppet/modules/site2
    manifest = /etc/puppet/manifests/site2/site.pp

[agent]
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig

    # libdir
/usr/local/puppet-dashboard/lib:/usr/local/puppet-dashboard/lib/puppet

[master]
    reports = http, store
    environments = pfm,int,site2
#    environment = pfm

-----------------------------------------------------------------------------------

the client puppet.conf:

[main]
    vardir = /var/lib/puppet
    logdir = /var/log/puppet
    rundir = /var/run/puppet
    ssldir = $vardir/ssl

[agent]
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig

    runinterval = 300
    environment=int
    report = true

------------------------------------------------------------------------------------

# /etc/puppet/int/site.pp

import "modules"
import "nodes"

node default {
  include barfoo
}

------------------------------------------------------------------------------------

#/etc/puppet/int/modules/barfoo/manifests/init.pp

class barfoo {

        file { "/tmp/myFile":
                owner   => root,
                group   => root,
                mode    => 666,
                source  => "puppet:///modules/barfoo/myFile"
                }

}

------------------------------------------------------------------------------------

/etc/puppet/int/modules/barfoo/files/myFile exists but it doesn''t get
put on
the agent in the int environment. There must be something we are not seeing
here.




On Thu, Nov 11, 2010 at 4:27 PM, Daniel Pittman <daniel@rimspace.net>
wrote:
> techn0gichida <jglouisjr@gmail.com> writes:
>
> > Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred
> > directory structure for using multiple environments? Does it work much
> > different in 2.6 than in 2.5?
>
> Not really substantially, no.
>
> > When I made the move I assumed (I know) that my current structure and
> > configurations would just roll over but that isn''t the case.
>
> It would be super-great if you could let us know what the problems were.
> (Perhaps you have in other messages, but better to ask twice than never
> hear
>  what problems folks are hitting, I figure. :)
>
> Regards,
>        Daniel
> --
> ✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155
> 707
>               ♽ made with 100 percent post-consumer electrons
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
“Twenty years from now you will be more disappointed by the things that you
didn’t do than by the ones you did do. So throw off the bowlines. Sail away
from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
Discover.”
– Mark Twain

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
directive wasn''t commented out. Shouldn''t this be commented on
that it
needs to be commented out for multiple environment use?

Thanks

On Nov 12, 10:52 am, James Louis <jgloui...@gmail.com>
wrote:
> Thanks Daniel,
>
> in puppet.conf on the server: (we are just trying to get a file installed
to
> the int environment client)
>
> [main]
>     vardir = /var/lib/puppet
>     logdir = /var/log/puppet
>     rundir = /var/run/puppet
>     ssldir = $vardir/ssl
>     pidfile=$rundir/puppetmaster.pid
>
> [int]
> #    modulepath = /etc/puppet/modules/int
> #    manifest = /etc/puppet/manifests/int/site.pp
> manifest = /etc/puppet/int/site.pp
> modulepath = /etc/puppet/int/modules
>
> [pfm]
>     modulepath = /etc/puppet/modules/pfm
>     manifest = /etc/puppet/manifests/pfm/site.pp
>
> [site2]
>     modulepath = /etc/puppet/modules/site2
>     manifest = /etc/puppet/manifests/site2/site.pp
>
> [agent]
>     classfile = $vardir/classes.txt
>     localconfig = $vardir/localconfig
>
>     # libdir >
/usr/local/puppet-dashboard/lib:/usr/local/puppet-dashboard/lib/puppet
>
> [master]
>     reports = http, store
>     environments = pfm,int,site2
> #    environment = pfm
>
>
-----------------------------------------------------------------------------------
>
> the client puppet.conf:
>
> [main]
>     vardir = /var/lib/puppet
>     logdir = /var/log/puppet
>     rundir = /var/run/puppet
>     ssldir = $vardir/ssl
>
> [agent]
>     classfile = $vardir/classes.txt
>     localconfig = $vardir/localconfig
>
>     runinterval = 300
>     environment=int
>     report = true
>
>
------------------------------------------------------------------------------------
>
> # /etc/puppet/int/site.pp
>
> import "modules"
> import "nodes"
>
> node default {
>   include barfoo
>
> }
>
>
------------------------------------------------------------------------------------
>
> #/etc/puppet/int/modules/barfoo/manifests/init.pp
>
> class barfoo {
>
>         file { "/tmp/myFile":
>                 owner   => root,
>                 group   => root,
>                 mode    => 666,
>                 source  => "puppet:///modules/barfoo/myFile"
>                 }
>
> }
>
>
------------------------------------------------------------------------------------
>
> /etc/puppet/int/modules/barfoo/files/myFile exists but it doesn''t
get put on
> the agent in the int environment. There must be something we are not seeing
> here.
>
>
>
> On Thu, Nov 11, 2010 at 4:27 PM, Daniel Pittman <dan...@rimspace.net>
wrote:
> > techn0gichida <jgloui...@gmail.com> writes:
>
> > > Moving from 2.5 to 2.6.2 and I was wondering if there is a
preferred
> > > directory structure for using multiple environments? Does it work
much
> > > different in 2.6 than in 2.5?
>
> > Not really substantially, no.
>
> > > When I made the move I assumed (I know) that my current structure
and
> > > configurations would just roll over but that isn''t the
case.
>
> > It would be super-great if you could let us know what the problems
were.
> > (Perhaps you have in other messages, but better to ask twice than
never
> > hear
> >  what problems folks are hitting, I figure. :)
>
> > Regards,
> >        Daniel
> > --
> > ✣ Daniel Pittman            ✉ dan...@rimspace.net            ☎ +61 401
155
> > 707
> >               ♽ made with 100 percent post-consumer electrons
>
> > --
> > You received this message because you are subscribed to the Google
Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
>
> --
> “Twenty years from now you will be more disappointed by the things that you
> didn’t do than by the ones you did do. So throw off the bowlines. Sail away
> from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
> Discover.”
> – Mark Twain
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 12.11.2010 19:22, techn0gichida wrote:
> I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
> directive wasn''t commented out. Shouldn''t this be
commented on that it
> needs to be commented out for multiple environment use?
I don''t really see your point. Yes, there is a commented out line in
the
posted config. Randomly commenting out such a line from your conf surely 
won''t fix a problem you''re having?

Besides, theres a perfectly functional manifest= line just below it:
>> [int]
>> #    modulepath = /etc/puppet/modules/int
>> #    manifest = /etc/puppet/manifests/int/site.pp
>> manifest = /etc/puppet/int/site.pp
>> modulepath = /etc/puppet/int/modules
Regards,
Felix

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Don''t know what to tell you. Commenting out the line in that file fixed
the
problem. And it''s been working great since.

On Thu, Nov 18, 2010 at 5:51 PM, Felix Frank <
Felix.Frank@alumni.tu-berlin.de> wrote:
> On 12.11.2010 19:22, techn0gichida wrote:
>
>> I found the problem in /etc/sysconfig/puppetmaster. The MANIFEST
>> directive wasn''t commented out. Shouldn''t this be
commented on that it
>> needs to be commented out for multiple environment use?
>>
>
> I don''t really see your point. Yes, there is a commented out line
in the
> posted config. Randomly commenting out such a line from your conf surely
> won''t fix a problem you''re having?
>
> Besides, theres a perfectly functional manifest= line just below it:
>
>
>  [int]
>>> #    modulepath = /etc/puppet/modules/int
>>> #    manifest = /etc/puppet/manifests/int/site.pp
>>> manifest = /etc/puppet/int/site.pp
>>> modulepath = /etc/puppet/int/modules
>>>
>>
> Regards,
> Felix
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
“Twenty years from now you will be more disappointed by the things that you
didn’t do than by the ones you did do. So throw off the bowlines. Sail away
from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
Discover.”
– Mark Twain

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Nov 18, 6:32 pm, James Louis <jgloui...@gmail.com>
wrote:
> Don''t know what to tell you. Commenting out the line in that file
fixed the
> problem. And it''s been working great since.
I''m glad your problem is fixed.

Folks around here have previously informed me that the whole /etc/
sysconfig interface dates from a time before Puppet had its own
configuration files.  There is nothing you can configure that way that
you cannot also configure via the main config file, but the reverse is
not true, so you might consider consolidating your Puppet
configuration into /etc/puppet/puppet.conf.


Cheers,

John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

That''s good to know. I originally installed on OpenSuse and it set up
the
sysconfig file automagically. Now I''m working on CentOS and what
I''m hearing
is I don''t need to set up a sysconfig file (which I already have).

On Fri, Nov 19, 2010 at 8:47 AM, jcbollinger
<John.Bollinger@stjude.org>wrote:
>
> On Nov 18, 6:32 pm, James Louis <jgloui...@gmail.com> wrote:
> > Don''t know what to tell you. Commenting out the line in that
file fixed
> the
> > problem. And it''s been working great since.
>
> I''m glad your problem is fixed.
>
> Folks around here have previously informed me that the whole /etc/
> sysconfig interface dates from a time before Puppet had its own
> configuration files.  There is nothing you can configure that way that
> you cannot also configure via the main config file, but the reverse is
> not true, so you might consider consolidating your Puppet
> configuration into /etc/puppet/puppet.conf.
>
>
> Cheers,
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
“Twenty years from now you will be more disappointed by the things that you
didn’t do than by the ones you did do. So throw off the bowlines. Sail away
from the safe harbor. Catch the trade winds in your sails. Explore. Dream.
Discover.”
– Mark Twain

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 11/19/2010 03:47 PM, jcbollinger wrote:
> 
> On Nov 18, 6:32 pm, James Louis <jgloui...@gmail.com> wrote:
>> Don''t know what to tell you. Commenting out the line in that
file fixed the
>> problem. And it''s been working great since.
> 
> I''m glad your problem is fixed.
> 
> Folks around here have previously informed me that the whole /etc/
> sysconfig interface dates from a time before Puppet had its own
> configuration files.  There is nothing you can configure that way that
Ah, so this was about the *sysconfig* file. Sorry for the noise then.

Felix

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Nov 19, 11:33 am, James Louis <jgloui...@gmail.com>
wrote:
> That''s good to know. I originally installed on OpenSuse and it set
up the
> sysconfig file automagically. Now I''m working on CentOS and what
I''m hearing
> is I don''t need to set up a sysconfig file (which I already have).
Some RHEL/CentOS packages also set up a sysconfig file, but you do not
need one as far as Puppet is concerned.  The interface is not really a
feature of Puppet itself, anyway; rather, it''s a feature of (some of)
the initscripts that are packaged with Puppet.

An advantage of putting everything needed into puppet.conf is that
Puppet reads it when you start it manually.  If you start
puppet[master]d by hand (e.g. for testing purposes) then the sysconfig
is ignored.


Cheers,

John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.