[Puppet Users] Re: puppet port 8139

2009-10-02 Thread Joe McDonagh
lovewadhwa wrote: > Hi > > In some of my servers my puppetd daemon doesnot open the default port > 8139.I have specified explicitly in configuration file but to no > use.Also checked for by executing the puppetd daemon with debug and > verbose option but didnot find any information logged.I tried

[Puppet Users] Re: what is queueing for storeconfigs?

2009-10-02 Thread Allan Marcus
makes sense. The access is only moderate in the e-mail! :-) --- Thanks, Allan Marcus 505-667-5666 On Oct 2, 2009, at 1:29 AM, Andrew Shafer wrote: You can't understand the slides unless you can hear the outrageous accent. On Fri, Oct 2, 2009 at 12:43 AM, Brice Figureau > wrote: On 2/1

[Puppet Users] Re: Puppet 0.25 - passenger + foreman (webfrontend)

2009-10-02 Thread Ohad Levy
On Fri, Oct 2, 2009 at 12:43 AM, philipp Hanselmann < philipp.hanselm...@gmail.com> wrote: > > > I found the answer by myself ... > Great, sorry for the late reply, we were kinda busy here at puppet camp :) > > Next steps will be to use passenger instead of mongrel > That should be really strai

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread R.I.Pienaar
hello, - "Aurelien Degremont" wrote: > How do you deal with a file, like /etc/sysconfig/network which have > content composed from > different aspects (could be network, nfs, nis, ...). So managed by > various modules but all > of them should add its own stuff to the same file. In the ca

[Puppet Users] Puppet way to manage a central file?

2009-10-02 Thread Thomas Bellman
Aurelien Degremont wrote: > I put /etc/sysconfig/network as an example. AFAIK, unfortunately, > Augeas only handles known files (existing lenses). If we trty to > handle /etc/our_local_config_file, it is not so easy. Indeed. Really silly design. There was a reason that I wrote "e.g." in my sug

[Puppet Users] Re: Using variables in virtual resources

2009-10-02 Thread Michael Gliwinski
On Friday 02 October 2009 13:41:44 Michael Gliwinski wrote: > On Friday 02 October 2009 07:35:57 Erling wrote: > > On 28 Sep, 19:44, Eric Gerlach wrote: > > > You might be able to do something like: > > > > > > realize User[kenneth] > > > > > > User[kenneth] { > > >         groups => $server_type

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread Michael Gliwinski
On Friday 02 October 2009 11:06:39 Aurelien Degremont wrote: > Thomas Bellman a écrit : > > Aurelien Degremont wrote: > >> How do you deal with a file, like /etc/sysconfig/network which have > >> content composed from different aspects (could be network, nfs, nis, > >> ...). So managed by various

[Puppet Users] Re: How to structure configuration using Puppet and version control tools

2009-10-02 Thread Matthew Hyclak
On Thu, Oct 1, 2009 at 10:56 AM, Calimero wrote: > > On 30 sep, 17:20, Kenneth Holter wrote: >> Hello all. >> >> We're running Puppet to manage our linux-servers, but as of now we don't >> really have a good setup for dealing with different environments >> (production, qass, and so forth). The p

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread Aurelien Degremont
Nicolas Szalay a écrit : > Le vendredi 02 octobre 2009 à 12:06 +0200, Aurelien Degremont a écrit : >> Thomas Bellman a écrit : >>> Aurelien Degremont wrote: >>> How do you deal with a file, like /etc/sysconfig/network which have content composed from different aspects (could be network,

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread Nicolas Szalay
Le vendredi 02 octobre 2009 à 12:06 +0200, Aurelien Degremont a écrit : > Thomas Bellman a écrit : > > Aurelien Degremont wrote: > > > >> How do you deal with a file, like /etc/sysconfig/network which have > >> content composed from different aspects (could be network, nfs, nis, > >> ...). So mana

[Puppet Users] Re: Using variables in virtual resources

2009-10-02 Thread Michael Gliwinski
On Friday 02 October 2009 07:35:57 Erling wrote: > On 28 Sep, 19:44, Eric Gerlach wrote: > > You might be able to do something like: > > > > realize User[kenneth] > > > > User[kenneth] { > >         groups => $server_type ? { > >                 typeA => "wheel", > >                 default => un

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread Aurelien Degremont
Thomas Bellman a écrit : > Aurelien Degremont wrote: > >> How do you deal with a file, like /etc/sysconfig/network which have >> content composed from different aspects (could be network, nfs, nis, >> ...). So managed by various modules but all > of them should add its >> own stuff to the same fi

[Puppet Users] Re: Puppet way to manage a central file?

2009-10-02 Thread Thomas Bellman
Aurelien Degremont wrote: > How do you deal with a file, like /etc/sysconfig/network which have > content composed from different aspects (could be network, nfs, nis, > ...). So managed by various modules but all > of them should add its > own stuff to the same file. > > What is your elegant way

[Puppet Users] Re: Puppet 0.25 - passenger + foreman (webfrontend)

2009-10-02 Thread philipp Hanselmann
I found the answer by myself ... mongrel network settings can be changend in /opt/foreman/vendor/rails/railties/lib/commands/server.rb I noticed that our company firewall is blocking Port 3000. Now it is working, I can see the webgui ... Next steps will be to use passenger instead of mongre

[Puppet Users] Puppet way to manage a central file?

2009-10-02 Thread Aurelien Degremont
Hello I facing I think a typical problem when using Puppet and I'm wondering what is the Puppet way to deal with this. I'm explaining. How do you deal with a file, like /etc/sysconfig/network which have content composed from different aspects (could be network, nfs, nis, ...). So managed by

[Puppet Users] Re: what is queueing for storeconfigs?

2009-10-02 Thread Andrew Shafer
You can't understand the slides unless you can hear the outrageous accent. On Fri, Oct 2, 2009 at 12:43 AM, Brice Figureau < brice-pup...@daysofwonder.com> wrote: > > On 2/10/09 0:35, Allan Marcus wrote: > > I would have loved to attend, but out budgets are just too tight. > > Would be great if