On 05/04/2013 02:25 PM, Luke Bigum wrote:
On Saturday, May 4, 2013 12:43:57 PM UTC+1, Martin Langhoff wrote:
On Fri, May 3, 2013 at 4:43 PM, Schofield > wrote:
> Everything else is managed by puppet.
Do you manage complex network setups (bonding, routing) via puppet?
There is a
On 05/04/2013 01:43 PM, Martin Langhoff wrote:
On Fri, May 3, 2013 at 4:43 PM, Schofield wrote:
Everything else is managed by puppet.
Do you manage complex network setups (bonding, routing) via puppet?
There is a certain degree of chicken-and-egg in that; how do you
handle managing configurat
Yes, that's what I meant, if it were available I would use it. But I don't
think useradd knows how to deal with it because AFAIK it only creates local
users. The same about /etc/passwd could be said about
/etc/sysconfig/network. You might want to control it partially only, not
the whole content
On Mon, May 6, 2013 at 8:49 AM, Bernardo Costa wrote:
> Well, I'll tell you that for now some kind of configuration is difficult to
> be done with puppet. At least I couldn't find a way to do it. Ex:
> controlling a /etc/passwd file but partially with a libnss compat syntax.
> This means entries o
On Sun, May 5, 2013 at 2:11 PM, Larry Fast wrote:
> What about the larger processes involved in incremental updates? Eg.
> sequencing your updates so that the service keeps running. I'm considering
> using Jenkins to orchestrate sequencial activity.
Coming from an ISConf background, I'd do it
Well, I'll tell you that for now some kind of configuration is difficult to
be done with puppet. At least I couldn't find a way to do it. Ex:
controlling a /etc/passwd file but partially with a libnss compat syntax.
This means entries of local users are no controlled but entries beginning
with
What about the larger processes involved in incremental updates? Eg.
sequencing your updates so that the service keeps running. I'm
considering using Jenkins to orchestrate sequencial activity.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" grou
On Saturday, May 4, 2013 12:43:57 PM UTC+1, Martin Langhoff wrote:
> On Fri, May 3, 2013 at 4:43 PM, Schofield >
> wrote:
> > Everything else is managed by puppet.
>
> Do you manage complex network setups (bonding, routing) via puppet?
> There is a certain degree of chicken-and-egg in that; ho
On Fri, May 3, 2013 at 4:43 PM, Schofield wrote:
> Everything else is managed by puppet.
Do you manage complex network setups (bonding, routing) via puppet?
There is a certain degree of chicken-and-egg in that; how do you
handle managing configuration without breaking the network that
delivers th
I want everything managed by puppet because if it is not it only adds
operational complexity into the environment. I have found that using
kickstart to bootstrap puppet works well. Kickstart does the minimum to
get puppet running (root volume group, temporary network, puppet rpms) and
the la
10 matches
Mail list logo
