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 contains a class called
wsus_client. In this exercise, you use the
wsus_client class to supply the types and providers necessary to schedule updates using a WSUS server with Puppet.
To prepare the class, you create a group called
windows_example and add the
wsus_client class to it.
Create the windows_example group
To classify a node is to add classification data (classes, parameters, and variables) for the node group to the node.
These instructions assume you have installed a monolithic PE deployment, installed at least one Windows agent node, and installed the
- In the PE console, click Nodes> Classification, and click Add group.
- In the Group name field, name your group, for example, windows_example, and click Add.
- Click Add membership rules, classes, and variables.
- On the Rules tab, in the Certname field, enter the name of the managed node you want to add to this group, and 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.
- Commit your changes.
Add the wsus_client class to the example group
Adding the class to the group and then running Puppet configures the group to use that class.
- In the console, click Classification, and find and select the
- On the Configuration 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 commit changes.
wsus_clientclass now appears in the list of classes for your agent node.
- Puppet runs, which configures the
windows_ examplegroup using the newly-assigned class. Wait one or two minutes.