On Tue, Jul 2, 2013 at 8:58 AM, Lawrence K. Chen, P.Eng. <[email protected]> wrote: > > If only there was an invisible way to drop CF3 on to policy server and all the existing CF2 just continued to work.... we try managing up into CF3 (something our new director says is part of his job...he's managing up our CIO.)
CF3 is designed such that it can be dropped in alongside CF2. You just replace the CF2 executor (cfexecd) with the CF3 executor (cf-execd), and the CF3 executor can run the CF2 agent (cfagent) and the CF3 agent (cf-agent). That's why the CF3 binaries have dashes in the name. So you can drop them into the CF2 working directory. CF3 is expressly designed for "overlay" onto CF2 installation, it's to make migration from CF2 to CF3 easier. The trick is editing exec_command in the executor configuration, that's the command for running the agent; modify it to run both agents (v2 and v3). May I recommend blog post by Diego Zamboni (author of "Learning CFEngine 3"): Migrating From CFEngine 2 to CFEngine 3, http://zzamboni.org/blog.cf-learn.info/migrating-from-cfengine-2-to-cfengine-3/ Let me know if you'd like any help. Yours, -at -- CFEngine Training: Irvine, California, October 14 - 17. http://cf3irvine.eventbrite.com/
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
