Movatterモバイル変換


[0]ホーム

URL:


CFEngine documentation homepage

classes

Suggest changes
Table of contents

Classes promises may be made in any bundle. Classes defined byclasses type promises incommon bundles arenamespace (aka global) scoped bydefault.

code
bundlecommong{classes:"one"expression=>"any";# always defined"two";# always defined"client_network"expression=>iprange("128.39.89.0/24");}

Notes:

  • The promiser is automatically canonified when classes are defined.
  • Classes are not automatically canonified when checked.
code
bundleagentmain{classes:"my-illegal-class";reports:# We search to see what class was defined:"$(with)"with=>join(" ",classesmatching("my.illegal.class"));# We see that the illegal class is explicitly not defined."my-illegal-class is NOT defined (as expected, its invalid)"unless=>"my-illegal-class";# We see the canonified form of the illegal class is defined."my_illegal_class is defined"if=>canonify("my-illegal-class");# Note, if takes expressisons, you couldn't do that if it were# automatically canonified. Here I canonify the string using with, and use# it as part of the expression which contains an invalid classcharacter, but# its desireable for constructing expressions."Slice and dice using `with`"with=>canonify("my-illegal-class"),if=>"linux|$(with)";}

First we promise to definemy-illegal-class. When the promise is actuatedit is automatically canonified and defined. This automatic canonification islogged in verbose logs (verbose: Class identifier 'my-illegal-class' contains illegal characters - canonifying).Next several reports prove which form of the class was defined. The lastreport shows howif takes a class expression, and if you are checking a classthat contains invalid characters you must canonify it.

code
code
R: my_illegal_classR: my-illegal-class is NOT defined (as expected, its invalid)R: my_illegal_class is definedR: Slice and dice using `with`

This policy can be found in/var/cfengine/share/doc/examples/class-automatic-canonificiation.cfand downloaded directly fromgithub.

  • The termclass andcontext are sometimes used interchangeably.
  • The following attributes to make a complete promise.

    • and
    • expression
    • dist
    • or
    • not
    • xor

If you omit all of them, the class is always defined (as if you saidexpression=> "any").

For example, the following promise defines the classweb when a file exists:

code
bundleagentexample{classes:"web"if=>fileexists("/etc/httpd/httpd.conf");}

History: The context attributesexpression,and,or,not,xor,dist were made optional in CFEngine 3.9.0. Before that, one of them wasrequired. So the following examples were the valid equivalents of the exampleabove before 3.9.0:

code
bundle agent example{  classes:      "web"        expression => fileexists("/etc/httpd/httpd.conf");      "webserver"        expression => "any",        if => fileexists("/etc/httpd/httpd.conf");}

Attributes

and

Description: Combine class sources with AND

The class on the left-hand side is set if all of the class expressions listedon the right-hand side are true.

Type:clist

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
classes:"compound_class"and=>{classmatch("host[0-9].*"),"Monday","Hr02"};

Notes:

If an expression contains a mixture of different object types that need to beANDed together, this list form is more convenient than providing anexpression.

dist

Description: Generate a probabilistic class distribution

Always set one generic class and one additional class, randomly weighted on aprobability distribution.

Type:rlist

Allowed input range:-9.99999E100,9.99999E100

Example:

code
classes:"my_dist"dist=>{"10","20","40","50"};

Notes:

In the example above the values sum up to10+20+40+50 = 120. When generatingthe distribution, CFEngine picks a number between1-120, and set the classmy_dist as well as one of the following classes:

code
my_dist_10(10/120ofthetime)my_dist_20(20/120ofthetime)my_dist_40(40/120ofthetime)my_dist_50(50/120ofthetime)

expression

Description: Evaluate string expression of classes in normal form

Set the class on the left-hand side if the expression on the right-hand sideevaluates to true. With classes, the notion of "true" is not a boolean state,because classes can never be false. They are not booleans. They can be definedor undefined, but it's important to understand that a class may be definedduring the execution of the agent, so the result of an expression maychange during execution.

Expressions can be:

  • class names, with or without a namespace

  • the literalstrue (always defined) andfalse (never defined) that allow JSON booleans to be used inside expressions

  • the logicaland operation, expressed asa&b ora.b, which is true if botha andb are true

  • the logicalor operation, expressed asa|b, which is true if eithera orb are true

  • the logicalnot operation, expressed as!a, which is true ifa is nottrue. Note again here thata couldbecome true during the execution. Soif you have"myclass" expression => "!x" andx starts undefined but isdefined later, you could have bothxandmyclass defined!

  • parenthesis(whatever) which operate as expected to prioritize expression evaluation

  • the return value of a function that returns a class, such asfileexists()and()userexists() etc.

Type:class

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
classes:"class_name"expression=>"solaris|(linux.specialclass)";"has_toor"expression=>userexists("toor");# it's unlikely a machine will become Linux during execution# so this is fairly safe"not_linux"expression=>"!linux";"a_or_b"expression=>"a|b";# yes, it's OK to define a class twice, and this is the same outcome# with different syntax"a_and_b"expression=>"a&b";"a_and_b"expression=>"a.b";# yes, it's OK to define a class twice, and this is the same outcome# with different syntax"linux_and_has_toor"expression=>and(userexists("toor"),"linux");"linux_and_has_toor"and=>{userexists("toor"),"linux"};

or

Description: Combine class sources with inclusive OR

The class on the left-hand side will be set if any one (or more) ofthe class expressions on the right-hand side are true.

Type:clist

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
classes:"compound_test"or=>{classmatch("linux_x86_64_2_6_22.*"),"suse_10_3"};

Notes:

This is useful construction for writing expressions that contain functions.

persistence

Description: Make the class persistent to avoid re-evaluation

The value specifies time in minutes.

Type:int

Allowed input range:0,99999999999

Example:

code
bundlecommonsetclasses{classes:"cached_classes"or=>{"any"},persistence=>"1";"cached_class"expression=>"any",persistence=>"1";}

Notes:

This feature can be used to avoid recomputing expensive classes calculationson each invocation. This is useful if a class discovered is essentiallyconstant or only slowly varying, such as a hostname or alias from anon-standard naming facility.Persistent classes are always global and can not be set to localbyscope directive.

For example, to create a conditional inclusion of costly class evaluations,put them into a separate bundle in a fileclasses.cf.

code
# promises.cfbodycommoncontrol{persistent_classes::bundlesequence=>{"test"};!persistent_classes::bundlesequence=>{"setclasses","test"};!persistent_classes::inputs=>{"classes.cf"};}bundleagenttest{reports:!my_persistent_class::"no persistent class";my_persistent_class::"persistent class defined";}

Then createclasses.cf

code
# classes.cfbundlecommonsetclasses{classes:"persistent_classes"# timer flagexpression=>"any",persistence=>"480";"my_persistent_class"or=>{...longlistorheavyfunction...},persistence=>"480";}

History: Was introduced in CFEngine 3.3.0

See also:persistance classes attribute,persist_time in classes body

not

Description: Evaluate the negation of string expression in normal form

The class on the left-hand side will be set if the class expression on theright-hand side evaluates to false.

Type:class

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
classes:"others"not=>"linux|solaris";"no_toor"not=>userexists("toor");

Notes:

Knowing that something is not the case is not the same as not knowing whethersomething is the case. That a class is not set could mean either. See the noteonNegative knowledge.

scope

Description: Scope of the class set by this promise.

Type: (menu option)

Allowed input range:

code
namespacebundle

Default value:bundle in agent bundles,namespace in common bundles

Example:

code
classes:"namespace_context"scope=>"namespace";"bundle_or_namespace_context";# without an explicit scope, depends on bundle type"bundle_context"scope=>"bundle";

See also:scope inbody classes

select_class

Description: Select one of the named list of classes to define based onhost's fully qualified domain name, the primary IP address and the UID thatcf-agent is running under.

This feature is useful for decentralized dynamic grouping. The class is chosendeterministically (not randomly) but it is not possible to say which host willend up in which class in advance. Only that given stable input a host willalways end up in the same class every time while running a given version ofCFEngine.

Type:clist

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
bundlecommong{classes:"selection"select_class=>{"one","two"};reports:one::"One was selected";two::"Two was selected";selection::"A selection was made";}

Notes:

This feature is similar to thesplayclass function. However,instead of selecting a class for a moment in time, it always chooses one classin the list; the same class each time for a given host. This allows hosts tobe distributed across a controlled list of classes (e.g for load balancingpurposes).

If a list is used as the input to select_class the promise will only actuate ifthe list is expandable. If the list has not yet been evaluated, theselect_class will be skipped and wait for a subsequent evaluation pass.

Given stable input, the output of this function will not change between executions of the same version of CFEngine. Its output should not change between versions of CFEngine within the same minor release (3.12.0 -> 3.12.1). Its output may change between minor versions (3.12.0 -> 3.13.0).

xor

Description: Combine class sources with XOR

The class on the left-hand side is set if an odd number of class expressionson the right-hand side matches. This is most commonly used with two classexpressions.

Type:clist

Allowed input range:[a-zA-Z0-9_!@@$|.()\[\]{}:]+

Example:

code
classes:"order_lunch"xor=>{"Friday","Hr11"};# we get pizza every Friday

Still need help?

Chat Ask a question on Github Mailing list
Version 
master3.24 (LTS)3.21 (LTS)view all versions

[8]ページ先頭

©2009-2025 Movatter.jp