On Fri, Jun 18, 2010 at 11:18 -0700, Nigel Kersten wrote:
> Have you tried --no-report ?
That works! Because other long options work as --key=value,
I never expected --report=false not to work. Thanks!
> This could be a bug, I don't use tagmail reports, but it just hit me
> that it's probably re
On 06/18/2010 02:18 PM, Nigel Kersten wrote:
On Fri, Jun 18, 2010 at 10:34 AM, Robert Scheer wrote:
To facilitate developing, testing and releasing puppet code, we use
different environments. That works very well. The only problem is that
I cannot prevent puppet from mailing a report, nor d
On Fri, Jun 18, 2010 at 10:34 AM, Robert Scheer wrote:
> To facilitate developing, testing and releasing puppet code, we use
> different environments. That works very well. The only problem is that
> I cannot prevent puppet from mailing a report, nor direct it somewhere
> else, when using a differ
Hello James,
Am Friday 12 March 2010 21:49:02 schrieb James Turnbull:
> > the reason for ignoring the different manifests was a setting
> > in /etc/sysconfig/puppetmaster. The settings name is
> > "PUPPETMASTER_MANIFEST" and was set to my "production" site.pp. Because
> > of my switch back to webb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/03/10 2:11 AM, Hubert Krause wrote:
> Hello list,
>
> Am Wednesday 10 March 2010 11:07:14 schrieb Hubert Krause:
>> I was running Puppet server in version 0.24.8 on Srerver and 0.24.4 up to
>> 0.24.8 on client and configured multiple environment
Hello list,
Am Wednesday 10 March 2010 11:07:14 schrieb Hubert Krause:
> I was running Puppet server in version 0.24.8 on Srerver and 0.24.4 up to
> 0.24.8 on client and configured multiple environments. The desired behavior
> is to have different sets of manifests and modules for my two
> environ
On Fri, 8 Jan 2010, Kenneth Holter wrote:
> Do you mean running puppetmaster on different linux servers? It would
> probably be the best solution, but I do think I prefer running multiple
> puppetmasters on one linux server if possible.. How are other people
> testing new puppetmasters?
>
> On
Kenneth Holter wrote:
Do you mean running puppetmaster on different linux servers? It would
probably be the best solution, but I do think I prefer running multiple
puppetmasters on one linux server if possible.. How are other people
testing new puppetmasters?
What?! You mean your puppetmast
Do you mean running puppetmaster on different linux servers? It would
probably be the best solution, but I do think I prefer running multiple
puppetmasters on one linux server if possible.. How are other people testing
new puppetmasters?
On Thu, Dec 31, 2009 at 6:42 PM, Scott Smith wrote:
> Kenn
Kenneth Holter wrote:
>
> We're look into ways to implement change management to our puppet
> configurations, and this approach is very interesting as it seems very
>
Even easier: Maintain multiple Puppet infrastructures. Push your code to each
as it is ready.
Dev puppetmaster, dev puppet cli
We're look into ways to implement change management to our puppet
configurations, and this approach is very interesting as it seems very
straight forward and easy to maintain (btw, it's very similar to the
approach described on http://fnord.no/sysadmin/puppet/staging). As described
on that web site
>>
> Doug, I am not a version control expert but I think you might be
> confusing svn branches with cvs branches.
> As soon as you do:
>
> svn cp production development:
>
> you've not only made a new puppet environment, you've 'branched'
> production into development.
I'd also recommend using a m
Douglas Garstang wrote:
> On Mon, Dec 21, 2009 at 8:32 AM, R.I.Pienaar wrote:
>
>> hello,
>>
>>
>> - "Douglas Garstang" wrote:
>>
>>
>>> http://www.devco.net/archives/2009/10/10/puppet_environments.php
>>>
[staging]
modulepath =
>>> /e
On Dec 19, 2009, at 11:54 PM, Douglas Garstang wrote:
> I'd like to be able to split out my puppet production and test
> environments so that I can continue to develop puppet
> modules/manifests without breaking production. How are people doing
> this?
My setup is pretty simple and doesn't requir
Douglas Garstang wrote:
> But... how do you serve up those multiple puppet environments? Are you
> running multiple versions of the puppetmaster? I'm using passenger so
> it would seem like it would be fairly easy to run additional
> puppetmasters on different ports, except that I can't find where
hello,
> >>> puppet.conf contains (in addition to the standard stuff):
> >>>
> >>> [staging]
> >>> modulepath =
> /etc/puppet-staging/modules:/etc/puppet-staging/services
> >>> manifest = /etc/puppet-staging/manifests/site.pp
> >>>
> >>> [development]
> >>> modulepath =
> >>> /etc/puppet-
On Mon, Dec 21, 2009 at 11:45 AM, Douglas Garstang
wrote:
> On Mon, Dec 21, 2009 at 8:36 AM, Matthew Hyclak wrote:
>> On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
>> wrote:
>>> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>>
hello,
'lo,
> I did read the reductive labs documentation (which is unclear as
> usual), and the devco site before posting here, and again after
> someone referenced it. I understand the concept of multiple
> environments quite well, and that's not the issue. The issue is how I
> integrate this fu
On Mon, Dec 21, 2009 at 8:36 AM, Matthew Hyclak wrote:
> On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
> wrote:
>> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
>>> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>>> wrote:
On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
On Mon, Dec 21, 2009 at 8:32 AM, R.I.Pienaar wrote:
> hello,
>
>
> - "Douglas Garstang" wrote:
>
>> http://www.devco.net/archives/2009/10/10/puppet_environments.php
>
>> > [staging]
>> > modulepath =
>> /etc/puppet-staging/modules:/etc/puppet-staging/services
>> > manifest = /etc/p
On Mon, Dec 21, 2009 at 11:27 AM, Douglas Garstang
wrote:
> On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
>> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
>> wrote:
>>> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
>>> wrote:
On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar w
hello,
- "Douglas Garstang" wrote:
> http://www.devco.net/archives/2009/10/10/puppet_environments.php
> > [staging]
> > modulepath =
> /etc/puppet-staging/modules:/etc/puppet-staging/services
> > manifest = /etc/puppet-staging/manifests/site.pp
> >
> > [development]
> > modul
On Mon, Dec 21, 2009 at 7:44 AM, Matthew Hyclak wrote:
> On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
> wrote:
>> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
>> wrote:
>>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
hello,
- "Douglas Garstang" wrote:
On Sun, Dec 20, 2009 at 7:17 PM, Douglas Garstang
wrote:
> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
> wrote:
>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
>>> hello,
>>>
>>> - "Douglas Garstang" wrote:
>>>
I'd like to be able to split out my puppet production and test
Douglas Garstang wrote:
> On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
> wrote:
>
>> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
>>
>>> hello,
>>>
>>> - "Douglas Garstang" wrote:
>>>
>>>
I'd like to be able to split out my puppet production and test
envi
On Sun, Dec 20, 2009 at 1:58 PM, Douglas Garstang
wrote:
> On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
>> hello,
>>
>> - "Douglas Garstang" wrote:
>>
>>> I'd like to be able to split out my puppet production and test
>>> environments so that I can continue to develop puppet
>>> modul
On Sun, Dec 20, 2009 at 4:57 AM, R.I.Pienaar wrote:
> hello,
>
> - "Douglas Garstang" wrote:
>
>> I'd like to be able to split out my puppet production and test
>> environments so that I can continue to develop puppet
>> modules/manifests without breaking production. How are people doing
>> t
hello,
- "Douglas Garstang" wrote:
> I'd like to be able to split out my puppet production and test
> environments so that I can continue to develop puppet
> modules/manifests without breaking production. How are people doing
> this? Puppet environments may be one way. I guess I'd have a
> m
2009/12/20 Russ Allbery :
> The advantage of Git branches is that we can much more easily merge or
> cherry-pick changes between the environments. For example, changes that
> must be made in production can be made there and then merged into test, so
> that test stays in sync easily but can maintai
Douglas Garstang writes:
> I'd like to be able to split out my puppet production and test
> environments so that I can continue to develop puppet modules/manifests
> without breaking production. How are people doing this? Puppet
> environments may be one way. I guess I'd have a main(prod) environ
30 matches
Mail list logo
