On Thursday, December 22, 2011 at 11:57 AM, David Lee wrote:
Michael DeHaan wrote:Thanks, totally agree.[...]Thanks. Glad to that, as a newbie to cobbler, I'm getting thismore-or-less right.[...]Then there are a few things that probably don't have pages on them,where we could take them off the main page too.* power management* PXE (boot loop prevention, menu generation, etc)* configuration management (section exists already about puppet, butshould merge in the built-in config stuff and make easier to understand)[...]I've always been uneasy about the way cobbler talks about "configurationmanagement".Installed machines can have a life-cycle of several years. It is inthis long-term, ongoing maintenance context that products such ascfengine and puppet use the term "configuration management".But when cobbler documentation uses this same term, it isn't talkingabout long-term maintenance at all. Rather it is talking about"configuration initialisation": getting some sort of initialconfiguration onto the machine that will probably do for the moment,where "for the moment" means "while my mind is on the business ofgetting this machine started; probably less than a day; probably lessthan an hour; probably less than even 15 minutes".So I would suggest that we give care to our use of terminology andintention. I suggest we reserve the term "configuration management" forits generally understood long-term maintenance purpose (cfengine,puppet, etc.), and introduce a term such as "configurationinitialisation" to discuss our activities of doing the initialtailoring. This initial tailoring might include hooks to installcfengine/puppet and just enough to get them started; it might includethe material (hitherto called "config management", such as "managementclasses" etc.).-- David Lee_______________________________________________cobbler mailing list