12 Installing Mid-scale and Entry-scale KVM #

Review the Chapter 2, Pre-Installation Checklist about recommended pre-installation tasks.

Prepare the Cloud Lifecycle Manager node. The Cloud Lifecycle Manager must be accessible either directly or via ssh, and have SUSE Linux Enterprise Server 12 SP3 installed. All nodes must be accessible to the Cloud Lifecycle Manager. If the nodes do not have direct access to online Cloud subscription channels, the Cloud Lifecycle Manager node will need to host the Cloud repositories.

1. If you followed the installation instructions for Cloud Lifecycle Manager server (see Chapter 3, Installing the Cloud Lifecycle Manager server), SUSE OpenStack Cloud software should already be installed. Double-check whether SUSE Linux Enterprise and SUSE OpenStack Cloud are properly registered at the SUSE Customer Center by starting YaST and running Software › Product Registration.

   If you have not yet installed SUSE OpenStack Cloud, do so by starting YaST and running Software › Product Registration › Select Extensions. Choose SUSE OpenStack Cloud and follow the on-screen instructions. Make sure to register SUSE OpenStack Cloud during the installation process and to install the software pattern patterns-cloud-ardana.

   tux > sudo zypper -n in patterns-cloud-ardana

2. Ensure the SUSE OpenStack Cloud media repositories and updates repositories are made available to all nodes in your deployment. This can be accomplished either by configuring the Cloud Lifecycle Manager server as an SMT mirror as described in Chapter 4, Installing and Setting Up an SMT Server on the Cloud Lifecycle Manager server (Optional) or by syncing or mounting the Cloud and updates repositories to the Cloud Lifecycle Manager server as described in Chapter 5, Software Repository Setup.

3. Configure passwordless sudo for the user created when setting up the node (as described in Section 3.4, “Creating a User”). Note that this is not the user ardana that will be used later in this procedure. In the following we assume you named the user cloud. Run the command visudo as user root and add the following line to the end of the file:

   CLOUD ALL = (root) NOPASSWD:ALL

   Make sure to replace CLOUD with your user name choice.

4. Set the password for the user ardana:

   tux > sudo passwd ardana

5. Become the user ardana:

   tux > su - ardana

6. Place a copy of the SUSE Linux Enterprise Server 12 SP3 .iso in the ardana home directory, var/lib/ardana, and rename it to sles12sp3.iso.

7. Install the templates, examples, and working model directories:

   ardana > /usr/bin/ardana-init

Set up your configuration files, as follows:

1. Copy the example configuration files into the required setup directory and edit them to contain the details of your environment.

   For example, if you want to use the SUSE OpenStack Cloud Mid-scale KVM model, you can use this command to copy the files to your cloud definition directory:

   ardana > cp -r ~/openstack/examples/mid-scale-kvm/* \
   ~/openstack/my_cloud/definition/

   If you want to use the SUSE OpenStack Cloud Entry-scale KVM model, you can use this command to copy the files to your cloud definition directory:

   ardana > cp -r ~/openstack/examples/entry-scale-kvm/* \
   ~/openstack/my_cloud/definition/

2. Begin inputting your environment information into the configuration files in the ~/openstack/my_cloud/definition directory.

(Optional) You can use the ardanaencrypt.py script to encrypt your IPMI passwords. This script uses OpenSSL.

1. Change to the Ansible directory:

   ardana > cd ~/openstack/ardana/ansible

2. Put the encryption key into the following environment variable:

   export ARDANA_USER_PASSWORD_ENCRYPT_KEY=<encryption key>

3. Run the python script below and follow the instructions. Enter a password that you want to encrypt.

   ardana > ./ardanaencrypt.py

4. Take the string generated and place it in the ilo-password field in your ~/openstack/my_cloud/definition/data/servers.yml file, remembering to enclose it in quotes.

5. Repeat the above for each server.

   

   Note

   Before you run any playbooks, remember that you need to export the encryption key in the following environment variable: export ARDANA_USER_PASSWORD_ENCRYPT_KEY=<encryption key>

Commit your configuration to the local git repo (Chapter 10, Using Git for Configuration Management), as follows:

ardana > cd ~/openstack/ardana/ansible
ardana > git add -A
ardana > git commit -m "My config or other commit message"

Important

This step needs to be repeated any time you make changes to your configuration files before you move on to the following steps. See Chapter 10, Using Git for Configuration Management for more information.

Use the playbook below to create a deployment directory:

cd ~/openstack/ardana/ansible
ansible-playbook -i hosts/localhost ready-deployment.yml

[OPTIONAL] - Run the wipe_disks.yml playbook to ensure all of your non-OS partitions on your nodes are completely wiped before continuing with the installation. The wipe_disks.yml playbook is only meant to be run on systems immediately after running bm-reimage.yml. If used for any other case, it may not wipe all of the expected partitions.

If you are using fresh machines this step may not be necessary.

ardana > cd ~/scratch/ansible/next/ardana/ansible
ardana > ansible-playbook -i hosts/verb_hosts wipe_disks.yml

If you have used an encryption password when running the configuration processor use the command below and enter the encryption password when prompted:

ardana > ansible-playbook -i hosts/verb_hosts wipe_disks.yml --ask-vault-pass

Run the site.yml playbook below:

ardana > cd ~/scratch/ansible/next/ardana/ansible
ardana > ansible-playbook -i hosts/verb_hosts site.yml

If you have used an encryption password when running the configuration processor use the command below and enter the encryption password when prompted:

ardana > ansible-playbook -i hosts/verb_hosts site.yml --ask-vault-pass

Note

The step above runs osconfig to configure the cloud and ardana-deploy to deploy the cloud. Therefore, this step may run for a while, perhaps 45 minutes or more, depending on the number of nodes in your environment.

Verify that the network is working correctly. Ping each IP in the /etc/hosts file from one of the controller nodes.