Skip to main content

Puppet Role Management System

Overview​

This document describes the role-based configuration management system that controls how hosts are managed and what settings are applied.

Role Behavior​

No Role Selected​

When no role is selected:

  • 0 changes are performed on the node
  • The system operates in a passive state
  • No configuration management occurs

Available Roles​

Host Management​

Subscription-Based Activation​

  • Monitoring infrastructure is only deployed when an active subscription exists
  • The system will not set up monitoring components without a valid subscription (Open Source is enabled

Subscription Expiration​

When a subscription expires or becomes inactive:

What Happens:

  • Monitoring setup is NOT removed from the host
  • The monitoring infrastructure remains in place

What Changes:

  • Prometheus is disabled automatically
  • This prevents Obmondo from receiving metrics from the host

Result: The monitoring stack remains functional on the host but stops sending data to the central monitoring system.

Usage Examples​

Monitoring-Only Host​

# Deploys only monitoring, always in noop mode
role: monitoring

Basic Managed Host​

# Basic management with monitoring
role: basic
full_host_management: true

Custom Role with Full Management​

# Custom role + basic + full management
role: webserver
full_host_management: true

Mode of Operation​

RoleDefault Modefull_host_managementCan Force No-Noop?
NoneN/AN/AN/A
role::monitoringnoopDisabled (hardcoded)No
role::basicnoopEnabledYes (with --no-noop)
Custom rolesnoopConfigurableYes (with --no-noop)

Best Practices​

  1. Start with noop mode - Always test configurations in noop mode before applying changes
  2. Enable full_host_management carefully - Understand the scope of changes before enabling
  3. Monitor subscription status - Keep track of subscription expiration to avoid unexpected monitoring disruptions
  4. Role composition - Remember that custom roles inherit role::basic settings
  5. SSSD requirements - Enable full_host_management if SSSD integration is needed

Troubleshooting​

No changes being applied​

  • Check if a role is assigned to the node
  • Verify whether you're running in noop mode
  • Confirm full_host_management settings if applicable

Monitoring data not appearing​

  • Check subscription status (active/expired)
  • Verify pushprox is not disabled due to inactive subscription
  • Confirm monitoring role or monitoring component is properly configured

Support​

For issues or questions regarding role management and configuration, please contact your system administrator or refer to the internal documentation portal.