What some people have done is to limit the number of bundles in the
bundlesequence to the common stuff, but have one of the bundles call a bunch of
modules:
body common control
{
bundlesequence => {"update", "classes", "security", "host_specific", "tidy",
"backup" };
}
bundle agent host_specific
{
modules:
webhost::
"any" usebundle => perl();
"any" usebundle => apache();
"any" usebundle => php();
dnshost::
"any" usebundle => bind();
mailhost::
"any" usebundle => postfix();
"any" usebundle => spamassassin();
}
On Sep 15, 2010, at 8:36 AM, no-re...@cfengine.com wrote:
> Forum: Cfengine Help
> Subject: Re: Looking for ideas on people's config
> Author: neilhwatson
> Link to topic: https://cfengine.com/forum/read.php?3,18245,18249#msg-18249
>
> In promises.cf I define classes in a common bundle at the top of the file.
> Then I can use this classes in common control.
> bundle common gclasses {
> classes:
> webhosts or => {
> "perl",
> "diamond",
> "ruby",
> "topaz"
> };
>
> dnshosts or => {
> "granite",
> "sand",
> "lime"
> };
> }
>
> bundle common control {
>
> webhosts::
> bundlesequence => {
> "update",
> "classes",
> "cfengine",
> "security",
> "apache",
> "php",
> "tidy",
> "backup"
> };
>
> dnshosts::
> bundlesequence => {
> "update",
> "classes",
> "cfengine",
> "security",
> "bind",
> "tidy",
> "backup"
> };
> }
>
>
> You can alter this to suit your needs. You can add variables in the top
> common bundle if you like.
>
> _______________________________________________
> 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
