Unfortunately Puppet is not able to handle the installation of Yum package groups like “Base” or “compat-libraries” and so forth. This is due to the fact that Puppet is currently not able to verify if all packages in a package group are installed after a Puppet run. Continue reading
This is something I will test out during the next days. Read this Red Hat article to know how to realize this scenario.
If you are interested in DevOps then read Red Hat`s DevOps blog.
Please find the Red Hat Satellite 6 product page here with release notes and more relevant informations.
This article describes very well above mentioned topic. Afterwards you should be able to manage sudo rules centrally in LDAP or Active Directory and access them through sssd for example. Have fun while reading.
If you configure multiple network cards in your RHEL machine with more than one gateway then you can use “policy based routing” to configure the network traffic in a way where the traffic will leave the same interface where the traffic came from.
This procedure is described in this Red Hat KCS article.
I also created a Puppet module to configure policy based routing on RHEL 6 / 7. Currently this module does not handle Bond or VLAN tagged interfaces. You can find my module here.
Puppet Lint is a nice tool to check the syntax of your Puppet code. Common errors can be fixed directly with Puppet Lint. It can also be included to CI tools like Jenkins if you want to check your Puppet code during a Jenkins build job for example.
Find out more about Puppet Lint here.