I seem to be missing something here. The OP's problem is that part of what
he wants to test is his code's environment-dependent behavior. I maintain
that no solution requiring a different environment to be declared than the
one he wants to test can in fact test such behavior adequately. I do
On 9/19/12 10:43 PM, Gonzalo Servat wrote:
> On Thu, Sep 20, 2012 at 3:37 PM, Garrett Honeycutt
> mailto:garr...@puppetlabs.com>> wrote:
>
> No need at all to use a different puppet master, you could just use
> environments[1]. When you want to test a system again a different
> environ
On Thu, Sep 20, 2012 at 3:37 PM, Garrett Honeycutt
wrote:
> Hiera[2] is meant to solve this. You might have staging.yaml and
> production.yaml that specify values for mysql_innodb_buffer_pool_size.
>
Another scenario I've found is that we also add certain users if
$::environment is production, an
On Thu, Sep 20, 2012 at 3:37 PM, Garrett Honeycutt
wrote:
> No need at all to use a different puppet master, you could just use
> environments[1]. When you want to test a system again a different
> environment, staging in this example, you can run `puppet agent -t
> --environment=staging`.
>
Yep,
On 9/19/12 4:53 PM, Gonzalo Servat wrote:
> Hi All,
>
> Thanks for your feedback. While writing the original email, the subject
> sounded familiar and that's because I had written about it in the past:
>
> https://groups.google.com/d/topic/puppet-users/twLhIwsCRu4/discussion
>
> Apologies to
Hi All,
Thanks for your feedback. While writing the original email, the subject
sounded familiar and that's because I had written about it in the past:
https://groups.google.com/d/topic/puppet-users/twLhIwsCRu4/discussion
Apologies to those involved in the other thread for not replying, but
Use heira. Heira can load a config file based on the environment. Setting
this up is as simple as creating a hiera definition such as...
(environment).yaml
... And then creating the following files: production.yaml and staging.yaml
that contain your environment specific configs.
Install the
On 19/09/12 06:11, Gonzalo Servat wrote:
Hi All,
In our environment, we use the $::environment variable extensively to
determine if the host should have one set of mounts (e.g. production)
or a different set of mounts (e.g. qa). This is just one example, but
there are many others where the $:
Hi All,
In our environment, we use the $::environment variable extensively to
determine if the host should have one set of mounts (e.g. production) or a
different set of mounts (e.g. qa). This is just one example, but there are
many others where the $::environment variable comes into play.
The pr
Hello,
one of my clients has a server infrastructure with 20+ servers that
are all unique. Currently it runs without a puppet staging environment
which makes me sleep badly at night :)
The problem is: the client doesn't have the resources to run 20
staging servers as well, and the overhead of sett
10 matches
Mail list logo
