Skip to content

Latest commit

 

History

History
172 lines (119 loc) · 5 KB

02-Prep-to-Install-Puppet-Master.md

File metadata and controls

172 lines (119 loc) · 5 KB
Raw

<-- Back

Lab #2 - Prepare to Install Puppet Enterprise on the puppet VM

Overview

Time to complete: 10 minutes

In this lab we will complete some pre-installations steps to get our VM ready to take Puppet Enterprise

Startup your Training VMs

If not already up and running...

vagrant up puppet

If you don't know the status of your vagrant-controlled VM's, you can always check with...

$ vagrant global-status
id       name         provider   state    directory
--------------------------------------------------------------------------------
4dd5ed7  puppet       virtualbox running  /Users/Mark/Vagrant/puppet-tutorial-pe
070258c  gitlab       virtualbox poweroff /Users/Mark/Vagrant/puppet-tutorial-pe
682eafe  agent        virtualbox poweroff /Users/Mark/Vagrant/puppet-tutorial-pe

Notice that my puppet VM is running, but my gitlab and agent VM's are powered off.

Login/Connect to your Training VM

$ vagrant ssh puppet

Once you're connected to the puppet VM, notice the bash shell pompt looks something like this:

[vagrant@puppet ~]$

Become root...

[vagrant@puppet ~]$ sudo su -

...and notice your shell prompt changes to:

Last login: Fri Oct 21 15:37:10 UTC 2016 on pts/0
[root@puppet ~]#

Now exit your root shell, and drop back to the vagrant user's shell...

[root@puppet ~]# exit
logout
[vagrant@puppet ~]$

Throughout the labs, you will need to execute many (if not most) commands as root.

Using sudo is a good habbit to develop, but starting a root shell can be more convenient as long as you remember that you can severly damage a running system if typing in the wrong command in the wrong place. (e.g. what if you accidently copy and paste some text into a root shell, and it contains some commands that remove the entire /lib directory?)

I will use sudo to run commands as root while in the vagrant user's shell, as well as starting a root shell with sudo su - to illistrate these two options below...

- Use sudo to edit the /etc/hosts file
- Start a root shell, and configure the host firewall

Pre-installation Steps

There are a couple things we need to do to make our VM ready to take PE:

- Add some entries to the /etc/hosts file ( if not already there )
- Open some ports through the host firewall

Edit /etc/hosts

The /etc/hosts file should already be setup correctly, but if for some reason you find it is not, go ahead and edit it as follows.

Edit /etc/hosts and add entries for localhost, as well as our 3 training VMs, both long (FQDN) and short name.

Note: For the purposes of this training, we will not use DNS.  We will rely
      on the /etc/hosts file for name resolution.  In a production deployment
      you would almost certainly want to use fully-qualified domain names (FQDN's),
      and very likely DNS as well.

sudo vi /etc/hosts

We want our /etc/hosts file to look like this:

127.0.0.1      localhost
192.168.198.10 puppet.example.com puppet
192.168.198.11 agent.example.com  agent
192.168.198.12 gitlab.example.com gitlab

In a later lab, we will configure Puppet to manage these /etc/hosts entries for us.

Configure Firewall

Open the host firewall to allow Puppet to work as per PE Install Guide - Firewall Config

sudo su -
firewall-cmd --permanent --add-service=https   # PE Console (default port 443)
firewall-cmd --permanent --add-port=3000/tcp   # PE web-based installer
firewall-cmd --permanent --add-port=8080/tcp   # PuppetDB
firewall-cmd --permanent --add-port=8081/tcp   # PuppetDB
firewall-cmd --permanent --add-port=8140/tcp   # Puppet Master, Certificate Authority
firewall-cmd --permanent --add-port=8142/tcp   # Orchestration services
firewall-cmd --permanent --add-port=8143/tcp   # The Orchestrator client uses this port to communicate with the orchestration services
firewall-cmd --permanent --add-port=61613/tcp  # MCollective / ActiveMQ
firewall-cmd --permanent --add-port=4432/tcp   # Local connections for node classifier, activity service, and RBAC status checks
firewall-cmd --permanent --add-port=4433/tcp   # Classifier / Console Services API endpoint
firewall-cmd --permanent --add-port=8170/tcp   # Code Manager
firewall-cmd --reload
firewall-cmd --list-all
exit # drop out of root shell

The output of your firewall-cmd --list-all should look like this:

[vagrant@puppet ~]$ firewall-cmd --list-all
public (default, active)
  interfaces: enp0s3 enp0s8
  sources:
  services: dhcpv6-client https ssh
  ports: 3000/tcp 8140/tcp 8170/tcp 8080/tcp 4433/tcp 8081/tcp 4432/tcp 8143/tcp 8142/tcp 61613/tcp
  masquerade: no
  forward-ports:
  icmp-blocks:
  rich rules:

Okay, now we're ready to run the Puppet Enterprise Installer...

Continue to Lab #3 --> Install Puppet Master

<-- Back to Contents

Copyright © 2016 by Mark Bentley