Node group property reference

Node group property reference

Properties hold the configuration that Puppet applies to your nodes. You can set a property on a node group, and depending on the property, also on a node, server, or site.

Platform Manager has more than 2,000 properties, but most of them were created for a single customer and are rarely used. This page covers the properties that are most commonly added to node groups:

To see every property, including its scope, type, and the nodes and node groups that use it, go to Administration > Properties in SC//Reliant™ Platform Manager. To see the keys of a hash property, open the property.

Note: A property only takes effect when the Puppet profile that reads it is also added to the node group. Where it is known, the Puppet profile is listed in the tables.

Platform configuration properties

All of the following properties are of type Hash. The Applies to column lists the resources the property can be set on.

Networking

PropertyTemplate nameApplies toPuppet profileDescription
Network Configurationsnetwork_configurationsNode, Server, Node group-Manages network interfaces and routes. Supported since Profiles 7.12.0, and replaces the Network interfaces and Static Routes properties.
Top-level keys: network_interfaces, network_routes
Host Name Overrideshost_namesNode, Node groupprofiles::hostsHost name entries to add to /etc/hosts.
Top-level keys: one key per host name
DNSdnsNode, Server, Node group-Configures a DNS server on the node, including ACLs, forwarders, DNSSEC validation, and zones.
Top-level keys: acl, allow_query, allow_recursion, listen_on, domain_forwarders, dnssec_validation, zone, zonefile
Connection FailoverfailoverNode, Node groupprofiles::failoverConfigures failover between network connections.
Top-level keys: network
Network interfaces (deprecated)network_interfacesNode, Node group-Configures the network interfaces of the edge appliance. Deprecated since Profiles 7.12.0. Use Network Configurations instead.
Top-level keys: one key per interface
Static Routes (deprecated)network_routeNode, Node group-Routes to add to the edge appliance. Deprecated since Profiles 7.12.0. Use Network Configurations instead.
Top-level keys: one key per interface

Clustering

PropertyTemplate nameApplies toPuppet profileDescription
Cluster Virtual IPscluster_vipsNode, Node groupprofiles::clusterVirtual IP addresses to assign to the cluster.
Top-level keys: vip
Cluster Interfacescluster_interfacesNode, Node groupprofiles::clusterNetwork interfaces to monitor as part of the cluster.
Top-level keys: one key per interface
Cluster Mount Pointscluster_mount_pointsNode, Server, Node groupprofiles::clusterAdditional volumes to mount and synchronize across the nodes in the cluster that are not tied to a virtual machine or container.
Top-level keys: one key per mount
Cluster Docker Resourcescluster_docker_resourcesNode, Node groupprofiles::clusterDocker configuration for clustered containers, with DRBD volume sharing. Requires Profiles 6.5.0 or later. For containers that are not clustered, use Docker.
Top-level keys: registries, networks, shared_mounts, containers, proxy, image_management
Cluster KVM Resourcescluster_kvm_resourcesNode, Node groupprofiles::clusterKVM virtual machines that are managed by the cluster.
Top-level keys: one key per virtual machine
Cluster LXCcluster_lxcNode, Node group-LXC containers that are shared between the nodes in the cluster.
Top-level keys: one key per container

Virtualization and containers

PropertyTemplate nameApplies toPuppet profileDescription
DockerdockerNode, Server, Node group, Siteprofiles::dockerDocker service configuration for containers on a single node. For clustered containers, use Cluster Docker Resources.
Top-level keys: registries, networks, volumes, containers, proxy, version
KVM Resourcesvirt_kvmNode, Node groupprofiles::kvmKVM virtual machines that are not managed by the cluster.
Top-level keys: one key per virtual machine
LXC Containersvirt_lxcNode, Node groupprofiles::lxcLXC containers that are not shared with a cluster.
Top-level keys: one key per container
Logical Volume Groupslogical_volume_groupsNode, Server, Node group-LVM volume group configuration.
Top-level keys: one key per volume group

Monitoring and logging

PropertyTemplate nameApplies toPuppet profileDescription
Sensu Go Agent Configurationssensugo_agentNode, Server, Node group, Siteprofiles::sensugo::agentConfigures the Sensu Go agent. These options can also override the Sensu Go Check Configurations.
Top-level keys: config_hash
Sensu Go Common Configurationssensu_go_common_configurationsNode, Server, Node group, Site-Settings shared by Sensu Go agents and servers, such as the version and backends.
Top-level keys: version, backends, ssl_enabled, password
Sensu Go Check Configurationssensu_go_checks_configurationsNode, Server, Node group-Sensu Go checks and handlers.
Top-level keys: checks, handlers, custom_checks
Sensu Go Server Configurationssensu_go_server_configurationsNode, Server, Node groupprofiles::sensugo::serverConfigures a Sensu Go server. For a standalone server, disable the cluster configuration.
Top-level keys: general_configurations, cluster_configurations

SC//Reliant services

PropertyTemplate nameApplies toPuppet profileDescription
Reliant Virtual Controller Configurationsrvc_configurationsNode, Server, Node groupprofiles::rvcConfigures the SC//Reliant™ Virtual Controller (RVC) on the node.
Top-level keys: version, port, backup_location, scheduling, ssl_enabled, command_timeout, maintained_snapshots
Reliant Local Status Interface Configurationsrlsi_configurationsNode, Node groupprofiles::rlsiOptions and controls for the SC//Reliant Local Status Interface (RLSI). Changes are applied during the next Puppet run.
Top-level keys: backups, cluster, vms, music_player_options
Edge Install Monitor Configurationsedge_install_monitorNode, Node groupprofiles::edge_install_monitorConfigures the edge install monitor, including the Platform Manager address, connection test, and NTP server.
Top-level keys: rpm_address, conn_test, backoff_min_wait, backoff_max_wait, ntp_server
Reliant Web Displayrwd_dataNode, Node groupprofiles::rwdSettings for the Reliant Web Display module.
Top-level keys: site_url, chrome_flags, service_enabled, package_list
EVDI Configurationsevdi_configurationsNode, Server, Node groupprofiles::evdi_serverEdge Virtual Desktop Infrastructure (EVDI) configuration.
Top-level keys: version, server_options, remmina

Configuration management

PropertyTemplate nameApplies toPuppet profileDescription
ChoriachoriaNode, Server, Node groupprofiles::choriaDeploys and configures Choria as a server, client, or broker.
Top-level keys: server, client, broker_settings, version, server_config
Puppetserver Configurationspuppetserver_configurationsServer, Node groupprofiles::puppetserverConfigures a Puppet server.
Top-level keys: version, instances, java_args, certificates, autosign_conf, log_level
Managed Files Utilitymanaged_filesNode, Server, Node group-Creates files on the node that are enforced by the automation framework, such as scripts that combine Platform Manager and system data or JSON files built from Platform Manager hashes. The files are created but not run.
Top-level keys: directories

System settings

PropertyTemplate nameApplies toPuppet profileDescription
ChronychronyNode, Server, Node groupprofiles::chronyConfigures Chrony, which manages the system clock.
Top-level keys: package_ensure, servers, server
APT ConfigurationsaptNode, Server, Node groupprofiles::aptConfigures APT, including the proxy, package sources, and pins.
Top-level keys: proxy, sources, pins
Sudo ConfigurationsudoNode, Server, Node group, Siteprofiles::sudoConfigures sudo access.
Top-level keys: admin
GRUB settingsgrub_settingsNode, Server, Node group-Manages the kernel command line, so that the node boots with consistent settings for hardware, power management, and resource control.
Top-level keys: boot_delay, kernel_parameters
SystemdsystemdNode, Server, Node group-Custom systemd settings, such as udev rules, drop-ins, and journald settings.
Top-level keys: udev_rules, manage_dropins, journald_settings
Unattended upgradesunattended_upgradesNode, Server, Node group-Configures automatic security upgrades on Debian nodes, run by cron: the archives to upgrade from, packages that must never be upgraded automatically, and the schedule.
Top-level keys: enabled, origin_archives, blacklist, cron_entry, jitter

VPN, proxy, and web services

PropertyTemplate nameApplies toPuppet profileDescription
OpenVPN Clients Configurationsopenvpn_clients_configurationsNode, Server, Node groupprofiles::openvpn_clientConfigures OpenVPN clients.
Top-level keys: version, ovpn_dco, clients, log_size, log_maxage
OpenVPN Servers Configurationsopenvpn_servers_configurationsServer, Node groupprofiles::openvpn_serverConfigures OpenVPN servers.
Top-level keys: version, ovpn_dco, servers, log_size, log_maxage
OpenVPN Clientopenvpn_clientNode, Server, Node group-Older single-client OpenVPN configuration.
Top-level keys: mgmt
OpenVPN Serversopenvpn_serversServer, Node group-Older OpenVPN server configuration.
Top-level keys: mgmt
squidsquidNode, Server, Node groupprofile::squidConfigures the Squid proxy.
Top-level keys: acl, http_access, http_ports, https_ports, cache_mem, version
Nginx Serversnginx_serversNode, Server, Node groupprofiles::nginxCreates and manages Nginx web servers.
Top-level keys: server
Redis ConfigurationsredisNode, Server, Node group, Siteprofiles::redisConfigures Redis masters and replicas.
Top-level keys: package_ensure, redis_servers
Redis master serversredis_masterServer, Node groupprofiles::redis_masterDefines one or more Redis master services.
Top-level keys: one key per service

Common standard properties

The following single-value properties are each used by many node groups. Related properties are grouped into one row.

Hardening

PropertyTemplate nameTypeDescription
Hardening Controlsmy_hardeningHashOptions for the hardening profile, including passwords, wanted and unwanted packages, disabled services, mount options, kernel options, and SSH daemon settings.
Hardening Password Rootmy_hardening_password_rootPasswordThe root password set by the hardening profile.
Hardening Password Installmy_hardening_password_installPasswordThe password of the install user set by the hardening profile.

Puppet and orchestration

PropertyTemplate nameTypeDescription
Hostname Puppetmy_hostname_puppetHostnameThe host name of the Puppet server.
Hostname PuppetCAmy_hostname_puppetcaHostnameThe host name of the Puppet certificate authority.
Hostip Puppet, Hostip Puppet Netmaskmy_hostip_puppet, my_hostip_puppet_netmaskIP, NetmaskThe IP address and netmask of the Puppet server.
Puppet Client Versionmy_puppet_client_versionTextThe Puppet agent version to install.
Cron Puppet Client Hours, Cron Puppet Client Minutesmy_cron_puppet_client_hours, my_cron_puppet_client_minutesNumberWhen the Puppet agent runs from cron. See Configuring automated Puppet runs.
Puppet Maxwaitmy_puppet_maxwaitNumberThe maximum random delay, in seconds, before a scheduled Puppet run. A value of 0 doesn't mean no delay. See Configuring automated Puppet runs.
DNS Alt Namesmy_dns_alt_namesTextAlternative DNS names for the node.
mcollective clients, mCollective Agents, mcollective rabbitmq hostmy_mcollective_clients, my_mcollective_agents, my_mcollective_rabbitmq_hostText, HostnameMCollective clients, agents, and RabbitMQ host.

Versions

PropertyTemplate nameTypeDescription
RVC Versionmy_rvc_versionTextThe SC//Reliant Virtual Controller (RVC) version to install.
Rlsi Versionmy_rlsi_versionTextThe SC//Reliant Local Status Interface (RLSI) version to install.

Network interfaces

PropertyTemplate nameTypeDescription
Lan1 to Lan6, Bridge0 to Bridge2, Vlan10, Interface External, Ddns Interfacemy_lan1 … my_lan6, my_bridge0 … my_bridge2, my_vlan10, my_interface_external, my_ddns_interfaceNetwork interfaceThe configuration of a network interface. For nodes on Profiles 7.12.0 or later, network interfaces are managed with Network Configurations.
<Interface> Ip, <Interface> Netmask, <Interface> Gatewayfor example my_lan1_ip, my_lan1_netmask, my_lan1_gateway, my_bridge0_ipIP, NetmaskThe static IP address, netmask, and gateway of an interface.
<Interface> Vip, <Interface> Vip Netmaskfor example my_bridge0_vip, my_lan1_vipIP, NetmaskA virtual IP address and netmask on an interface.
Bridge0 Interfaces, Bridge1 Interfacesmy_bridge0_interfaces, my_bridge1_interfacesTextThe physical interfaces that make up a bridge.

Domain and DNS

PropertyTemplate nameTypeDescription
Domainmy_domainTextThe domain of the node.
Domain Reversemy_domain_reverseTextThe reverse DNS zone.
Hostips Dns, Hostips Dns Netmaskmy_hostips_dns, my_hostips_dns_netmaskIP, NetmaskThe IP addresses and netmask of the DNS servers. Puppet writes these servers to /etc/resolv.conf on each node, followed by the Puppet server's IP address, and the node queries them in that order. If a public DNS server such as 8.8.8.8 is listed first, the node can't resolve internal SC//Reliant host names, such as the Sensu servers. See Troubleshooting a node that shows as offline.

Logging

PropertyTemplate nameTypeDescription
Rsyslog Clientmy_rsyslog_clientHashRsyslog client settings, including log forwarders and Elasticsearch, Datadog, and New Relic destinations.
Rsyslog Retentionmy_rsyslog_retentionNumberThe maximum number of days to keep logs.
Hostip Logmy_hostip_logIPThe IP address of the log server.
logserversmy_logserversTextThe log servers to send logs to.
logserver store logsmy_logserver_store_logsBooleanWhether an rsyslog server stores all logs.
logserver relaymy_logserver_relayBooleanWhether an rsyslog server relays logs.

Monitoring

PropertyTemplate nameTypeDescription
hostip sensu, hostip sensu Netmaskmy_hostip_sensu, my_hostip_sensu_netmaskIP, NetmaskThe IP address and netmask of the Sensu server.
Sensu Subscriptionsmy_sensu_subscriptionsTextThe Sensu subscriptions for the node.
Arpwatch Interfacesmy_arpwatch_interfacesTextThe interfaces that arpwatch monitors.
interface monitor interval, interface monitor timeoutmy_interface_monitor_interval, my_interface_monitor_timeoutNumberHow often, and with what timeout, interfaces are monitored.

IPMI

PropertyTemplate nameTypeDescription
IPMImy_ipmiHashThe configuration of the IPMI interface, including users and networks. Does not work properly with Profiles earlier than 6.0.0.
ipmi ip, ipmi gatewaymy_ipmi_ip, my_ipmi_gatewayIPThe IP address and gateway of the IPMI interface.
IPMI Passwordmy_ipmi_passwordPasswordThe password for the IPMI interface.

RLSI

PropertyTemplate nameTypeDescription
Rlsi Enabled Tabs, Rlsi Publicly Available Tabs, Rlsi Enabled Checksmy_rlsi_enabled_tabs, my_rlsi_publicly_available_tabs, my_rlsi_enabled_checksTextThe RLSI tabs and checks that are enabled, and the tabs that can be viewed without signing in.
Rlsi Music Enablemy_rlsi_music_enableBooleanWhether the RLSI music player is enabled.

Other

PropertyTemplate nameTypeDescription
apt client proxymy_apt_client_proxyTextThe proxy that APT uses.
Docker dnsmasq configmy_docker_dnsmasq_configHashThe dnsmasq configuration used with Docker.
Environment File Contentmy_environment_file_contentText areaThe contents of an environment file on the node.
KVM Template Path 1, KVM Template Path 2, Optional VM 1my_kvm_template_path_1, my_kvm_template_path_2, my_optional_vm_1TextKVM virtual machine template paths and optional virtual machines.

Other properties

Properties that are not listed on this page are either rarely used or were created for a specific customer. Their template names usually start with my_. To find one, search the Properties page in Platform Manager by name or template name.