Every module contains one or more classes. Classes are named chunks of Puppet code and are the primary means by which Puppet Enterprise configures nodes. The Puppet wsus_client module you installed in the Module Installation QSG contains a class called
wsus_client. In this example, you’ll use the
wsus_client class to supply the types and providers necessary to schedule updates using a WSUS server with Puppet.
In this example, you create a group called windows_example and add the
wsus_client class to it.
Note: The process for adding classes to agent nodes in the console is the same on both Windows and *nix operating systems.
Create the windows_example group
- In the PE console, click Nodes > Classification, and then click Add group.
- In the Group name field, name your group, for example, windows_example, and then click Add.
- Click the link to add membership rules, classes and variables.
On the Rules tab, in the Certname field, enter the name of the PE-managed node you want to add to this group, and then click Pin node.
Repeat this step for any additional nodes you want to add.
Note: Pinning a node adds the node to the group regardless of any rules specified for a node group. A pinned node remains in the node group until you manually remove it. Adding nodes dynamically describes how to use rules to add nodes to a node group.
wsus_client class to the example group
In the console, click Nodes > Classification, and select the windows_example group.
On the Classes tab, in the Add new class field, select
wsus_clientdoesn’t appear in the list, you might have to click Refresh.
Click Add class, and then commit changes.
wsus_clientclass now appears in the list of classes for your agent node.
Puppet runs, which configures the windows_ example group using the newly-assigned class. Wait one or two minutes.