Hi Traiano, The points you state are all standard operations easily achieved with Cfengine. But I suspect that creating the promises manually would be much more efficient than trying to create scripts that in turn create Cfengine policies. It also allows for much greater flexibility in case you don't want every bit equal on all servers at some point. Cfengine is built around the idea that agents are independent entities, rather than the old-fashioned clone/rebuild/rollback model.
I suggest that instead of spending time on installing packages on and configuring your "master" server, create Cfengine promises. Good luck with the first steps. -- Regards, Eystein On Tue, Mar 9, 2010 at 11:00 AM, Traiano Welcome <traiano.welc...@mtnbusiness.co.za> wrote: > Hi List > > (Newbie Alert!) I’ve got a test installation of cfengine3 running on a few > freebsd servers: What I’d like to do is use cfengine to automate the > creation of a Server Template for package installation and configuration. > > So, for example, I have a server which is an ideal installation template > (right packages installed, right processes running, right configuration > files), and I deploy cfengine on it, and cfengine checks the packages > installed (and possibly the config files in /etc/) and generates for me 3 > .cf files: > > 1. A file containing cefengine code to install all packages on the server > that are listed as installed, > 2. A file containing cfengine code to create and configure all configuration > files in /etc/ and, > 3. A file with cfengine code to check if all the processes running on the > freebsd server are running, and if not to start them up. > > The idea would then be to deploy these 3 files and cf-agent on other bare > freebsd installed servers and cfengine would do the work of ‘cloning’ the > configuration profile of the new systems. > > Is this easily doable with the current tools that come with cfengine3? > > Thanks in advance, > Traiano Welcome > ________________________________ > NOTE: This e-mail message and all attachments thereto contain confidential > information intended for a specific addressee and purpose. If you are not > the addressee (a) you may not disclose, copy, distribute or take any action > based on the contents hereof; (b) kindly inform the sender immediately and > destroy all copies hereof. Any copying, publication or disclosure of this > message, or part hereof, in any form whatsoever, without the sender's > express written consent, is prohibited. No opinion expressed or implied by > the sender necessarily constitutes the opinion of MTN. This message does not > constitute a guarantee or proof of the facts mentioned herein. No Employee > or intermediary is authorised to conclude a binding agreement on behalf of > MTN Group Limited, or any of its subsidiary companies, by e-mail without the > express written confirmation by a duly authorised representative of MTN > Group Limited. > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > > _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
