Este conteúdo não está disponível no idioma selecionado.

Chapter 9. Enforcing Puppet Configuration on Managed Hosts


You can enforce configuration from Satellite either manually on demand (run once) or automatically in configurable intervals.

9.1. Running Puppet Once Using SSH

Assign the proper job template to the Run Puppet Once feature to run Puppet on managed hosts.

Procedure

  1. In the Satellite web UI, navigate to Administer > Remote Execution Features.
  2. Select the puppet_run_host remote execution feature.
  3. Assign the Run Puppet Once - SSH Default job template.

Run Puppet on managed hosts by running a job and selecting category Puppet and template Run Puppet Once - SSH Default. Alternatively, click the Run Puppet Once button in the Schedule Remote Job drop down menu on the host details page.

9.2. Understanding Intervals of Automatic Enforcement

Satellite considers hosts to be out of sync if the last Puppet report is older than the combined values of outofsync_interval and puppet_interval set in minutes. By default, the Puppet agent on managed hosts runs every 30 minutes, the puppet_interval is set to 35 minutes and the global outofsync_interval is set to 30 minutes.

The effective time after which hosts are considered out of sync is the sum of outofsync_interval and puppet_interval. For example, setting the global outofsync_interval to 30 and the puppet_interval to 60 results in a total of 90 minutes after which the host status changes to out of sync.

9.3. Setting the Puppet Agent Run Interval on a Host

Set the interval when the Puppet agent runs and sends reports to Satellite.

Procedure

  1. Connect to your managed host using SSH.
  2. Add the Puppet agent run interval to /etc/puppetlabs/puppet/puppet.conf, for example runinterval = 1h.

9.4. Setting the Global Out-of-Sync Interval

Procedure

  1. In the Satellite web UI, navigate to Administer > Settings.
  2. On the General tab, edit Out of sync interval. Set a duration, in minutes, after which hosts are considered to be out of sync.

    You can also override this interval on host groups or individual hosts by adding the outofsync_interval parameter.

9.5. Setting the Puppet Out-of-Sync Interval

Procedure

  1. In the Satellite web UI, navigate to Administer > Settings, and click the Config Management tab.
  2. In the Puppet interval field, set the value to the duration, in minutes, after which hosts reporting using Puppet are considered to be out of sync.

9.6. Overriding Out-of-Sync Interval for a Host Group

Procedure

  1. In the Satellite web UI, navigate to Configure > Host Groups.
  2. Select a host group.
  3. On the Parameters tab, click Add Parameter.
  4. In the Name field, enter outofsync_interval.
  5. From the Type dropdown menu, select integer.
  6. In the Value field, enter the new interval in minutes.
  7. Click the Submit button.

9.7. Overriding Out-of-Sync Interval for an Individual Host

Procedure

  1. In the Satellite web UI, navigate to Hosts > All Hosts.
  2. Click Edit for a selected host.
  3. On the Parameters tab, click Add Parameter.
  4. In the Name field, enter outofsync_interval.
  5. From the Type dropdown menu, select integer.
  6. In the Value field, enter the new interval in minutes.
  7. Click the Submit button.
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat