Gi Giorgio (and others), Quoting Giorgio Pioda (2013-01-19 12:59:40) > > >In my wishlist I would also like to see Cfengine3 deeper boundled; > > >im currently using it since November to keep the client in sync and > > >is really great to automatize additional packages and configs. > > > > Yes, I have also had several deployed setups (not any more) that > > were fully maintained by Cfengine3. However, if a switch over to > > Debian LAN will be in the discussion, one should see what can be > > handled by FAI and if then is anything left that has to be handled > > by cfengine. > > But FAI itself is a mix of Cfengine2 with other tools. Cfengine3 > should support Cf2 legacy scripts. Isn't it?
CFEngine is both a scripting engine and a site-wide OS customizing framework. FAI is an OS install and customizing framework. FAI can make use _some_ CFEngine _scripts_ (and many other scripts), but the core of the FAI framework is different from CFEngine the framework. I agree with Mike that a move to FAI is a different path than tying CFEngine scripts to the CFEngine framework. I believe that a move to FAI will make Debian Edu easier to reuse for similar but not identical Debian usecases. I believe that use of CFEngine the framework has a higher risk of drifting further away from Debian than FAI. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
