Satellite 6 offers the possibility to provision a host with multiple network cards, however an issue is faced when using VMWare in conjuction with Satellite 6 and you want to provision multiple network interfaces with static IP addresses.
What happens is that after the provisioning of a virtual machine is complete, multiple network cards are added, but only the primary interface (which is used for PXE / DHCP during installation) is configured correctly.
I created a workaround to get this working. I described this solution in an official Red Hat KCS article which is now verified by Red Hat Engineering and published to the public. You can find this article here.
If you are interested in learning more about Docker and Linux Container in general and especially its terminology then please visit this Red Hat website.
If you plan to deploy RHEL guests with Satellite 6 and your DNS server of choice is Microsoft DNS than Satellite 6 is also able to create / delete appropriate DNS entries for newly created hosts automatically via foremen-proxy on Microsoft DNS. This article describes on how to configure both Satellite 6 and Microsoft DNS.
You will find a good overview of common administrative commands in RHEL 5, 6 and 7 on the following link.
NailGun provides an easy to us Python library that facilitates easy usage of the Satellite 6 API. This is an Upstream project and is not officially supported by Red Hat.
Official project website: visit Github
Documentation: visit Red the Docs
Examples: click here or here
I have created a Python script which automatically registers your existing RHEL clients to a Satellite 6 / Katello 2 server or Capsule. It also configures your Puppet agent, creates a “Host” entry in Satellite 6 / Katello 2 Web-UI and starts an initial Puppet run. All you need to do is to sign the Puppet agent cert request on your Satellite or Capsule server (if autosign is not configured which is default).
You can run the script either interactively (The script searches all needed values on your Satellite and shows the findings as options. Currently you have to copy/paste the values.) or unattended (where you have to pass by ALL needed values like organization, location, hostgroup etc.).
You can find the script on Github: https://github.com/hambuergaer/sat6_client_configuration
The Satellite “katello-installer” currently does not offer options to configure foreman proxy settings during installation. This leads to the problem that if you manually configured settings in /etc/foreman-proxy/settings.d/ these settings will be set back to default after each “katello-installer –upgrade”.
I already filed an RFE to extend the katello-installer options in the future (see here).
If you want to learn interesting stuff about journalctl please visit this page: link.
Satellite 6.1 provides a possibility to integrate OpenSCAP into Satellite. OpenSCAP is a security and vulnerability scanner which creates compliance reports for your hosts.
- More information about OpenSCAP: klick here
- More information on how to integrate OpenSCAP into Satellite: klick here
There is currently a bug (see BZ 1259188, should be fixed with Satellite 6.1.6) with ‘Hosts’ and ‘Content Hosts’ mappings which should be done manually. How this works is described in this Red Hat KB article. The bug leads to the problem that even if the upload of SCAP scan results from your client to Satellite 6 / Capsule was successfully performed no reports are visible in Satellite 6 web-ui for your host.