Satellite 6 and config file management

Latest response

Hi

I have Satellite 6.1.3 up and running and have a challengs right now that I need to tackle. Basically I want to be able to update and distribute /etc/sudoers and /etc/auto.master files across all my servers. A typical scenario is when you need to add/remove sudo rules and update them on all or large number of servers. Or need to add new NFS auto mount point to /etc/auto.master file. I do it usually 2-3 times a week.

In the old (Satellite 5 ) I used to have Configuration Channel (In the GUI Configuration->Configuration Channels) with for example sudoers file and I could then update the file and apply config channel to all or selected servers.

What is the best way to do it in Satellite 6?

Responses

Configuration file management in Sat 6+ is done using Puppet. Its can do much more than Configuration Channels in Satellite 5.6.

This guide can help you do that.

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Puppet_Guide/index.html

You will have to write a puppet module for that or you may some on forge.puppetlabs.com

- Swapnil

Boris, Satellite 5 and 6 architecture are totally different. You need to configure your host group and put your hosts under that. The 2nd task is to configure puppet-agent: https://access.redhat.com/solutions/1228973. You can have n number of config file on your list, that puppet will take care to ensure they have been persistent...Manoj

In Sat 5, I currently have a config channel for each host plus a config channel fo the release (rhel5, rhel6, rhel7) plus additional channels if required. In the host specific channel I put the SSH keys for example, /etc/ssh/key. I do this so when I need to rebuild machines, they get their same key back. How do I replicate this in Sat 6?

Puppet seems like a very large hammer...

Hi Colin,

In Sat 6 almost I is using puppet modules that either I wrote myself och picked them from the puppet website. There is some mental activation threshold to get started with puppet but once you have done than then it pretty simple to write modules. Although some things are really hard to achieve, but only some.

For ssh keys I wrote a module that just creates a file with the content which is a ssh public key and puts all my keys under for example /etc/ssh/myuserseks. Then my sshd is configured to find the keys there.

Here is the snippet from the puppet module (of course modified slightly) that places a key file in place. The forum reformats my code and it end up on one line, I dont know hut to keep the newlines here :) Try copy pasting into notepad++ alike and see if it looks better

file { "${ssh_keys_path}/alice_keys" : ensure => file, mode => '0440', owner => 'alice', group => 'root', content => 'Here comes a key data for example QWERTYUIOASFGDHLKAALKJHksdAAB3NzaC1yc2EAAAAB', require => File[$ssh_keys_path], }

Hope this helps.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.