How would you define it?
by Mike McGrath
So I'm working on a language.xml document. I'm referencing rfc2119 for
some def's but I'm not sure what to do about others.
How would the people on this list define the following?
client:
server:
host:
end user:
admin:
Its been surprisingly difficult to come up with some so I thought I'd just
drop by the list and see what others thought.
-Mike
15 years, 10 months
Re: First Pitch: PuppetB
by Mike McGrath
> Hi there,
>
> here's a first standard I'd like to pitch and get you guys involved
> with. I've been using puppet in a number of environments including my
> "servers" at home, ranging from just a couple of servers to a thousand
> desktop/laptop/server organization.
>
> The things I've figured out over time, I'm going to try and use at the
> Fedora Infrastructure as well, and make up a standard or best practice
> for configuration management. Some of you might use other configuration
> management tools as well; I'd also like you to kick in and tell me what
> I'm doing wrong.
>
> So, I guess the title of the standard would be "Configuration
> Management" or something like that.
>
> I'll give you something to ponder right-away. I've been packaging or
> actually rebuilding the stack that is needed for the puppetmaster to run
> the mongrel server type instead of the default webrick, since webrick
> inherent to the Ruby stack (?) can only do one thread at a time. So, for
> starters, I'd recommend using mongrel straight-away as the initial
> server type.
>
> Let me know what you think ;-)
>
I agree with this. We'd talked in our FUDCon session briefly about puppet
modules and unless there's a technical reason not to, I think that every
endorsed application should have one of these puppet modules associated
with it.
There's also an FAS group called 'gitcsi' that will give you access to our
git repo:
http://git.fedorahosted.org/git/csi.git/
At the end of the day, configuration management is at the CORE of what
will make this work. Configuration management like puppet and cfengine
are basically sysadming for adults :)
-Mike
15 years, 10 months
First Pitch: Puppet
by Jeroen van Meeuwen
Hi there,
here's a first standard I'd like to pitch and get you guys involved
with. I've been using puppet in a number of environments including my
"servers" at home, ranging from just a couple of servers to a thousand
desktop/laptop/server organization.
The things I've figured out over time, I'm going to try and use at the
Fedora Infrastructure as well, and make up a standard or best practice
for configuration management. Some of you might use other configuration
management tools as well; I'd also like you to kick in and tell me what
I'm doing wrong.
So, I guess the title of the standard would be "Configuration
Management" or something like that.
I'll give you something to ponder right-away. I've been packaging or
actually rebuilding the stack that is needed for the puppetmaster to run
the mongrel server type instead of the default webrick, since webrick
inherent to the Ruby stack (?) can only do one thread at a time. So, for
starters, I'd recommend using mongrel straight-away as the initial
server type.
Let me know what you think ;-)
Kind regards,
Jeroen van Meeuwen
-kanarip
P.S. Also working on puppetmanaged.org; which will have HUGE benefit
from what you guys bring in here.
15 years, 10 months