The blog post doesn't say much of anything, and the guide link is broken. But, now that you mentioned it, the dash makes sense now....$boss was complaining the other day about the dash for some reason...
All the stuff we had found on upgrading CF2 to CF3 cover promise conversion or vaguely cover only the CF3 side of an inplace migration...or why we should upgrade, no details on how the CF2 side continues to work. This message being the first hint as to how. Though at this point, I'll have to wait until the $boss says ok...because if I have free time at work, he's got something else lined up for me to do already. And, no way to get CF3 into our package management system without everybody knowing about it, and it'll need to be in the system to show up on any systems.... (there have been the occasional one off....but they usually get us in the end....like our RT system was done as one off, done by one of our student admins....to track requests on our student admins....it grew to not only for requests of other units with us, but request to some of those other units....until they finally started working on having our service now system do service requests. Plus CF3 wouldn't be a one off...) ----- Original Message ----- > 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/ -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: [email protected] Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library
_______________________________________________ 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/
