As a companion to my series on managing Windows Server with Puppet 5, this short two-part article will guide you through installing your own Puppet 5 server on Red Hat Linux in Hyper-V.
In the final part of this two-part article, I’m going to show you how to install Puppet 5 on Red Hat Linux. In the first part, I installed Red Hat Enterprise Linux (RHEL) in a Hyper-V virtual machine running on Windows 10. I also registered and subscribed RHEL using my Red Hat Developer Program account.
If you missed my series of articles on managing Windows Server using Puppet, here are the links to the pieces published so far.
Managing Windows Server with Puppet Part 1: Configure Puppet Master and Bootstrap the Puppet Agent in Windows Server
Managing Windows Server with Puppet Part 2: Log in to Puppet Master, Accept Node Certificate, and Test Connectivity
Managing Windows Server with Puppet Part 3: Install Modules and Edit the Site Manifest
Managing Windows Server with Puppet Part 4: Working with Files and ACLs
Managing Windows Server with Puppet Part 5: Managing Local Users and Groups
Managing Windows Server with Puppet Part 6: Installing, Updating, and Removing Software
Managing Windows Server with Puppet Part 7: Installing Active Directory
Let’s get started and install Puppet. The VM will need Internet connectivity to complete the steps below.
rpm -Uvh https://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpm
yum install -y puppetserver
The next step is optional. I want to configure Puppet to use a maximum of 512MB of RAM because I want to assign the VM just 1GB of RAM. If you have enough available memory, you can skip this step and leave the default RAM assignment.
certname = petripuppetmaster
server = petripuppetmaster
firewall-cmd --permanent --zone=public --add-port=8140/tcp firewall-cmd –reload
systemctl start puppetserver systemctl enable puppetserver
That’s it! The Puppet Master is now ready to receive incoming requests from agents. You can check the status of your server using the following commands. Use puppet status to check the version number and whether the server is active. Netstat can be used to check that Puppet is listening on port 8140. Puppet is a Java application, so you’ll see Java and not Puppet listed in the command’s output.
systemctl status puppetserver puppet status netstat -anpl | grep 8140
Puppet relies on DNS, so make sure that you can access agents and servers by domain name. You can add entries to the hosts file on Linux using vi if necessary:
Additionally, the Puppet Master time and date must be in-sync with your Puppet agents. You can check the time, date, and time zone using the date command.
Don’t forget to follow my series on managing Windows Server using Puppet for more information on how to work with Puppet 5.