On 2013-07-05 19:02, Brian Hicks wrote:
On Wednesday, July 3, 2013 11:40:15 PM UTC-7, David Schmitt wrote:
On 03.07.2013 00:26, Jakov Sosic wrote:
> On 05/09/2013 03:33 PM, jcbollinger wrote:
>
That exactly is the problem. Ruby does not provide a internal
partitioning for namespaces. So, depending on who hits your
puppetmaster
first, if your ruby code is not the same across environments, one of
those will load and be used for everything.
I'm not sure I get it. We are using multiple environments in our setup
and haven't seen issues yet. Our puppetmaster has this in the config:
modulepath = /u0/puppet/$environment/modules
manifestdir = /u0/puppet/$environment/manifests
and so forth, for all the various bits of config. Everything has to be
duplicated per environment. we store the configs in subversion, then to
create a new environment you can just svn copy production to a new
branch and specify it during agent runs to test new code. for example like:
puppet agent --test --environment=foo --noop
since everything has to be duplicated, it seems like we avoid namespace
issues. There's no cross-environment dependencies. am I missing something?
This only applies to custom types and providers which do not get loaded
by (the) puppet (parser) but are ruby scripts which get loaded by
directly by the ruby process.
Sorry if I was unclear on that point.
Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
