Part 1: RHEL 7.2 Installation and Configuration

The following topics describes how to download, install, and configure the RHEL 7.2 operating system on the Blue Planet server.

Note
 RHEL 7.2 installation procedures use the Dell PowerEdge R630 rack server as an example.

Download RHEL 7.2

  1. Download the Red Hat Enterprise Linux Server version 7.2 x86_64bit server ISO image.

  2. Create a USB stick to place the downloaded RHEL 7.2 ISO image. For Unix, enter the correct device (for example, /dev/sdb or /dev/sdc). For Mac OSX, select the correct USB device /dev/disk{2-4}. For more information, see the Red Hat Customer Portal.

    Unix machine:

    sudo dd if=rhel-server-7.2-x86_64-dvd.iso of=/dev/sdb bs=8M
sudo fdisk -l

    Mac OSX:

    diskutil list
sudo dd if=rhel-server-7.2-x86_64-dvd.iso of=/dev/disk4 bs=4096

  3. Set up the BIOS to boot from the USB stick, then restart your computer.

Install and configure RHEL 7.2

Follow these steps to install and configure the RHEL 7.2 server software. This method uses the RHEL Anaconda installer. For more information, see the Red Hat Customer Portal.

Important
 You must have an RHEL 7.2 license to complete this procedure.

  1. After the host machine boots, the Welcome to Red Hat screen displays. Select the language, English (United States), for example, then click Continue.

    The Installation Summary window, shown below, displays.

    rhel install summary 1.png
    Figure 1. Installation Summary window

  2. On the Installation Summary window, click DATE & TIME then, on the DATE & TIME window (shown below), select the region to use for the server timezone. Ciena recommends that you set the timezone to GMT.

    rhel date time.png
    Figure 2. Date & Time window

  3. Click Done

  4. On the Installation Summary window, click Software Selection, then select the Infrastructure server installation. Do not select any options in the Add-ons for the selected Environment panel.

  5. Click Done.

    The system automatically detects the live network interface for Network & Host Name.

  6. On the Installation Summary window, click Installation Destination. The Installation Destination window, shown below, displays.

    rhel install dest 1.png
    Figure 3. Installation Destination window

  7. On the Installation Destination window, select the following:

    1. Local Standard Disks--The available disks display. If two disks are displayed, select only the primary disk. The primary disk is typically displayed on the left and labeled as sda, as shown in the figure above. If more than one is selected (indicated by a checkmark), select to uncheck.

      Note
      		 If you select both disks, they will be included in the volume group and will not be accessible as a second disk for Docker storage. You will need to reinstall RHEL 7.2 to remove the second disk from the volume group.

      Verify that the second disk has 150 GB available to serve as an LVM partition for Docker container images. This disk is partitioned when you run the docker-storage-setup script. If only one disk is displayed, verify that it has an additional 150 GB for Docker images.

    2. Other Storage Options--Select I will configure partitioning.

  8. Click Done. The Manual Partitioning window, shown below, displays.

    rhel man partition 1.png
    Figure 4. Manual Partitioning window 1

  9. For the partitioning scheme, select LVM.

  10. Select Click here to create them automatically to specify LVM mount points. The Manual Partitioning window displays the information shown below.

    rhel man partition 2.png
    Figure 5. Manual Partitioning window 2

    On the Manual Partitioning window, complete the following steps:

    1. Record the amount of home storage space.

    2. Select the /home partition, then click "-"" to delete.

    3. Select the / (root) partition and add the space that was assigned to the /home partition in step a. For a single-host deployment, leave 150 GB of disk space for Docker storage.

    4. Select the /boot partition and increase the partition to 1024 MB.

      Note
      		 You do not need to change the swap partition because it is created automatically.

  11. Click the / (root) partition.

  12. Next to Volume Group (rhel), click Modify. The Configure Volume Group window displays.

    1. From the Size Policy list, select As large as possible.

    2. Click Save. The Partitioning window displays.

  13. Click Done. The Summary of Changes window displays.

  14. Click Accept Changes.

  15. On the Installation Summary window, select Network & Host Name.

    1. Verify that the network interface device correctly identifies the default, KDUMP (kernal crash dumping mechanism).

    2. Enable the Ethernet port.

    3. Click Done.

  16. In the Installation Summary window, click Begin Installation. The Configuration window, shown below, displays.

    rhel configuration.png
    Figure 6. Configuration Set Root Password window

  17. During the installation, set the root password (you will create a non-root bpadmin user later):

    1. Click Root Password.

    2. Enter a password in Root Password, then enter the password again to confirm.

    3. Click Done. If the password is weak, click Done twice to accept the weak password.

      Note
      		 A weak password is acceptable because you will restrict the server to sshkeys access and the Red Hat user will not have remote SSH access. You can change the password later.

    4. Click Done again.

Register RHEL 7.2 and update RHEL 7.2 package and dependencies

Complete the following steps to register the RHEL 7.2 installation and update the RHEL package and dependencies.

  1. Register your RHEL installation using the subscription-manager register command.

    subscription-manager register --username bpuser@ciena --password <password> --auto-attach --release=7.2 --force

  2. Download and install the RHEL 7.2 Infrastructure Server base on each server.

    Note
    		 The Blue Planet server requires the infrastructure server package. 
    yum --setopt=group_package_types=mandatory,default,optional groupinstall 'Infrastructure Server'
    Important

    This Blue Planet release can only run on RHEL 7.2. Enable only the following RPM packages. Do not enable others because they might interfere with Blue Planet processes.

    • rhel-7-server-rh-common-rpms

    • rhel-7-server-rpms

    • rhel-7-server-optional-rpms

  3. Update any RHEL packages and dependencies (assume yes if prompted).

yum update -y

Configure the host names

Complete the following steps to give Blue Planet host(s) a unique name.

  1. Log in as root.

    $ sudo -s

  2. Set a unique name using the hostnamectl set-hostname command. This example sets the name, cluster1.mycompany.com.

    # hostnamectl set-hostname cluster1.mycompany.com

  3. For multi-host clusters, complete steps 1-2 at each host.

Remove and recreate the SSH host files

  1. Remove the SSH host files, create new SSH host files, and restart the sshd.service.

    rm -rf /etc/ssh/ssh_host_*
ssh-keygen -A
systemctl restart sshd.service

  2. For a multi-host cluster, repeat step 1 at each host.

Create the bpadmin user

Complete the following steps to create a non-root user named bpadmin. The bpadmin user is required to perform the remaining Blue Planet installation tasks.

  1. As root, add a Docker group.

    # groupadd docker

  2. Create the user, bpadmin.

    # useradd -d /home/bpadmin -m -s /bin/bash -g docker bpadmin

  3. Set the password for bpadmin; in this example the password is bpadminpw.

    # passwd bpadmin
Changing password for user bpadmin.
New password: xxxxxxxxx

Retype new password: xxxxxxxxx

password set

  4. Create an /etc/bp2 directory and set the owner as bpadmin.

    # mkdir /etc/bp2
# chown bpadmin:`id --group bpadmin` /etc/bp2

  5. Repeat steps 1 through 4 on each host.

Create the bpadmin user sudo privileges

Complete the following steps to create sudo privileges for the bpadmin user. Adding the permissions accurately is important. Should you encounter permission failures later in the Blue Planet installation, verify that all privileges below were entered accurately.

  1. As the root user, create the /etc/sudoers.d/bpadmin file on each host and enter the following permissions.

    # cat <<EOF > /etc/sudoers.d/bpadmin
bpadmin ALL=(ALL) NOPASSWD: /bin/apply-ilan-config
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/bp2-site*
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/rm /etc/docker/key.json
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart docker.service
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/systemctl stop docker.service
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/systemctl start docker.service
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/set-site-ip
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/brctl delif dockerbr ilanbr
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/ifconfig ilanbr down
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/ovs-vsctl add-br ilanbr
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/ovs-vsctl del-br ilanbr
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/yum remove
bpadmin ALL=(ALL) NOPASSWD: /usr/bin/yum clean
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/wipefs
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/lvremove --force direct-lvm
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/lvremove -y rhel/docker-pool
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/lvremove -y direct-lvm/docker-pool
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/vgdisplay
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/vgremove -y direct-lvm
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/lvs
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /etc/yum.repos.d/bp2.repo
bpadmin ALL=(ALL) NOPASSWD: /usr/sbin/service docker restart
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /tmp/bp-docker-installer/
bpadmin ALL=(ALL) NOPASSWD: /tmp/bp-docker-installer/configure-sshd.sh
bpadmin ALL=(ALL) NOPASSWD: /tmp/bp-docker-installer/single-host-install.sh
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /var/lib/docker
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /etc/sysconfig/docker-storage
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /etc/sysconfig/docker-storage-setup
bpadmin ALL=(ALL) NOPASSWD: /bin/rm -rf /etc/bp2/*
bpadmin ALL=(ALL) NOPASSWD: /bin/find /bp2 -type d -exec chmod go+rX {} +
bpadmin ALL=(ALL) NOPASSWD: /bin/find /bp2 -type f -exec chmod go+r {} +
EOF

  2. Disable tty for sudo ssh sessions.

    sed -i 's/^Defaults    requiretty/#Defaults    requiretty/g' /etc/sudoers

  3. Complete steps 1 and 2 on each host.

Configure the SSH keys

Complete the following steps to configure the SSH keys for the root and bpadmin users.

  1. Generate an SSH RSA key pair. Repeat at each host.

    # ssh-keygen -t rsa
    Note
    		 Accept the default file location of ~/.ssh/id_rsa, leave the pass phrase empty, and confirm. This writes the public key to ~/.ssh/id_rsa.pub and the private key to ~/.ssh/id_rsa.

  2. Copy the root SSH key to the host. When prompted, enter the root password and proceed. Repeat for each host.

    # ssh-copy-id -i ~/.ssh/id_rsa.pub root@<server-ip host-A>
# ssh-copy-id -i ~/.ssh/id_rsa.pub root@<server-ip host-B>
# ssh-copy-id -i ~/.ssh/id_rsa.pub root@<server-ip host-C>

  3. Switch user to bpadmin and create the SSH key.

    Note
    		 Accept the default ~/.ssh/id_rsa file location, leave the pass phrase empty, and confirm. The public key will be written to ~/.ssh/id_rsa.pub and the private key to ~/.ssh/id_rsa. 
    su bpadmin
ssh-keygen -t rsa

  4. Copy the bpadmin SSH key to itself. When prompted, enter the bpadmin password and proceed.

    ssh-copy-id -i ~/.ssh/id_rsa.pub bpadmin@<server-ip host-A>
ssh-copy-id -i ~/.ssh/id_rsa.pub bpadmin@<server-ip host-B>
ssh-copy-id -i ~/.ssh/id_rsa.pub bpadmin@<server-ip host-C>

  5. Repeat steps 3 and 4 at each host.

results matching ""

    No results matching ""