just in case some of you missed it ;=)<br>please take some time and answer this little survey<br><br>thanks<br>Rachid<br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">
Zarouali Rachid</b> <<a href="mailto:rzarouali@gmail.com">rzarouali@gmail.com</a>><br>Date: Jan 8, 2007 12:35 PM<br>Subject: [config management] kind of survey<br>To: <a href="mailto:fedora-infrastructure-list@redhat.com">
fedora-infrastructure-list@redhat.com</a><br><br></span>Hy all,<br><br>i have recently join the fedora infrastructure list, so maybe this survey would appear to you a bit odd.
<br>i have taken a deeper look at what have been discussed regarding the config management task,<br>many of you have strong experience in different kind of tools like glump, puppet, cfengine ...
<br>but i haven't seen any checkup list on :<br>- what's the aim of a new config management system.<br>- how far we want this tool to manage servers config (system,services, both of them, anything else maybe ....).
<br>- system limitations (for example : no ruby tools because it has been sealed that ruby should be installed on servers ).<br><br>i've
seen jeff ollie has made a little wiki page listing all config
management tools suggested, with pros and cons,
<br><br>here's my little suggestion:<br>first : <br>we should list : <br>- what the new config tool should do for us<br>- perhaps how we want this tool to work, (agent/server or something else)<br>- system things for example : no ruby, if there an agent so it should communicate securely with his server .....
<br>second :<br>looking at jeff wiki's page and other solutions discussed on the list, and see if there is any tool listed there which answer all our requirements,<br>if not then 2 choice :<br>- take a look around and find the "right" tool
<br>- lower a little bit our requirements, so one of the tools listed would answer them (definitely the worst solution ).
<br>third:<br>-build a test environment with the chosen tool, so
everyone can play with it (the more people become familiar with it, the
best it would be ;) )<br>fourth:<br>- make a deployment schedule.<br>fifth:<br>- deploy and enjoy the work done by all people involved in ;=)
<br><br>here my personal view:<br>1) <br>what the new config tool should do for us:<br>this tool should help us managing system and services configurations of all fp.o servers.<br>by managing, i mean :<br>- building new config to deploy.
<br>- easily and smoothly updating several config<br>- versioning all config created and/or updated<br><br>how we want this tool to work:<br>- all tasks should be done securely, agent/server tool or not.<br>- the tool should give us some report on how tasks goes.
<br><br>system things:<br>well as I'm not used on how servers are deployed , i can't really answer this point but, <br>IMHO, whatever tool is chosen, it should not require something that may change how our systems works, this tool should be nearly invisible system view.
<br><br>2)<br>about the right tool, after looking at threads in the list archive and looking at jeff page, glump seems to be a good start<br><br>3) and 4) would come along the way after all question for 1) and 2) are settled.
<br><br><br>who's next to answer this little survey ? :)<br>hoping this would help<br><span class="sg"><br>Rachid<br>
</span>