As far as I can tell, both approach are very similar. I usually combine both, with top level bundles in the bundlesequence hiding the complexity and showing the intention, and these bundles using methods with all the complex stuff
I'm don't know why cf-know doesn't work, your code looks correct Regards Nicolas On 29/09/2010 22:08, no-re...@cfengine.com wrote: > Forum: Cfengine Help > Subject: Re: Understanding how to use methods / bundles > Author: msvob...@linkedin.com > Link to topic: https://cfengine.com/forum/read.php?3,18460,18555#msg-18555 > > Bump... Anyone? > > http://www.youtube.com/watch?v=L21fgU336KM > > > > On 9/23/10 12:41 PM, "Mike Svoboda" wrote: > > Hey fellow cfengineers! > > Have a question and hope that this helps some other folks out as well. In my > promises.cf, I define my inputs and bundlesequence as such: > > $ more promises.cf > ... > ... > body common control > { > bundlesequence => { @(global.agent_sequence) }; > > > inputs => { > # Separate config files for each CFEngine process and the standard library. > "cfengine_stdlib.cf", > "cf-execd.cf", > "cf-monitord.cf", > > "kill_switch.cf", > "garbage_collection.cf", > "cfengine_automated_execution.cf", > "verify_root.cf", > ... > ...... > > > So, I’m planning on inputting every file on every client, but wont actually > execute upon them. I define the bundlesequence by using classes. > > > bundle common global > { > "common_sequence" slist => { > # Phase 1 configurations > "kill_switch", > "garbage_collection", > "cfengine_automated_execution", > "verify_root", > }; > > # If we dont fall in a special class, then just execute the common policies > above. > any:: > "agent_sequence" slist => { @(common_sequence) }; > > # If we do fall under a specific class, and we want to execute something > additional to the global policies, then > # add them here. > #HADOOP_SERVER:: > #"agent_sequence" slist => { @(common_sequence), "hadoop_specific_actions" }; > #DB_SERVER:: > #"agent_sequence" slist => { @(common_sequence), > "check_SAN_attached_storage_policy" }; > > > > So, this actually works.... Kinda... I can run cf-agent and I don’t have any > issues. > > $ /var/cfengine/bin/cf-agent -I -K > $ > > If I try to run cf-know, it bombs out. > > $ /var/cfengine/bin/cf-know > Bundle "kill_switch" listed in the bundlesequence is not a defined bundle > Bundle "garbage_collection" listed in the bundlesequence is not a defined > bundle > Bundle "cfengine_automated_execution" listed in the bundlesequence is not a > defined bundle > Bundle "verify_root" listed in the bundlesequence is not a defined bundle > > > Looking online, I saw this post from Mark > > > > Anyways, what I’m trying to ask — is how is using > > bundlesequence => { "main" }; .... > > > method: > any:: > “default” usebundle => generic_bundle; > > > A different approach from what I am currently doing? And what is incorrect > about my current use of an slist to define bundlesequence instead of using > method / bundles? > > Thanks! > Mike > > _______________________________________________ > 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
