...
For every device type within the Device Manager that you would like to specify Puppet classes and parameters for, you will need to configure the 'Puppet Node Control' device module. This module is configured like any other device module within the system. Configuration of device modules is done from the 'Device Types' section of 'setup & admin' Settings. Select the device type group or individual device type(s) that you'd like to configure the module for, and click the 'modules' link. From this page, click the 'add module' link. This will load a popup. The 'Details' tab should be configured with 'Enabled' to 'Yes', 'Module' to 'Puppet Node Control', and 'Client Access' to 'No Access'. The Config tab is a bit more complicated.
The 'Available Classes/Modules' section allows you to define the classes and modules known to your puppetmaster, and available for application to a puppet client. The format for an entry is as follows:
...
The naming convention here is the same as above for modules. To the left of the colon is the actual environment name as you would use in a node definition. To the right of the colon is a 'friendly name'.
Once this module is configured, you can then set up devices in the Device Manager to take advantage of it. By default, Ubersmith will provide an empty YAML node definition with no classes, and the custom data fields and values as parameters. If you edit the configuration for the Puppet Node Control module, you'll be able to select the applicable classes for that device, as well as the appropriate environment.
NOTE: The puppetmaster uses the host's fully qualified domain name (FQDN) -- in most cases, the output of the 'hostname' on the system to query Ubersmith. You will want to ensure that the Device Manager entry has that hostname configured as the device label in order for the configuration to be pulled properly from Ubersmith.
...