Chapter 10. Performing basic overcloud administration tasks

Procedure

1. On the existing OpenStack environment, create a new image by taking a snapshot of a running server and download the image:

   $ openstack server image create instance_name --name image_name
   $ openstack image save image_name --file exported_vm.qcow2

   Copy to Clipboard Toggle word wrap

2. Copy the exported image to the undercloud node:

   $ scp exported_vm.qcow2 stack@192.168.0.2:~/.

   Copy to Clipboard Toggle word wrap
3. Log into the undercloud as the stack user.

4. Source the overcloudrc file:

   $ source ~/overcloudrc

   Copy to Clipboard Toggle word wrap

5. Upload the exported image into the overcloud:

   (overcloud) $ openstack image create imported_image --file exported_vm.qcow2 --disk-format qcow2 --container-format bare

   Copy to Clipboard Toggle word wrap

6. Launch a new instance:

   (overcloud) $ openstack server create  imported_instance --key-name default --flavor m1.demo --image imported_image --nic net-id=net_id

   Copy to Clipboard Toggle word wrap

Procedure

1. To view a dynamic inventory of nodes, run the tripleo-ansible-inventory command after sourcing stackrc:

   $ source ~/stackrc
   (undercloud) $ tripleo-ansible-inventory --list

   Copy to Clipboard Toggle word wrap

   The --list option returns details about all hosts. This command outputs the dynamic inventory in a JSON format:

   {"overcloud": {"children": ["controller", "compute"], "vars": {"ansible_ssh_user": "heat-admin"}}, "controller": ["192.168.24.2"], "undercloud": {"hosts": ["localhost"], "vars": {"overcloud_horizon_url": "http://192.168.24.4:80/dashboard", "overcloud_admin_password": "abcdefghijklm12345678", "ansible_connection": "local"}}, "compute": ["192.168.24.3"]}

   Copy to Clipboard Toggle word wrap

2. To execute Ansible playbooks on your environment, run the ansible command and include the full path of the dynamic inventory tool using the -i option. For example:

   (undercloud) $ ansible [HOSTS] -i /bin/tripleo-ansible-inventory [OTHER OPTIONS]

   Copy to Clipboard Toggle word wrap

   • Replace [HOSTS] with the type of hosts to use. For example:

     • controller for all Controller nodes
     • compute for all Compute nodes
     • overcloud for all overcloud child nodes i.e. controller and compute
     • undercloud for the undercloud
     • "*" for all nodes

   • Replace [OTHER OPTIONS] with additional Ansible options. Some useful options include:

     • --ssh-extra-args='-o StrictHostKeyChecking=no' to bypasses confirmation on host key checking.
     • -u [USER] to change the SSH user that executes the Ansible automation. The default SSH user for the overcloud is automatically defined using the ansible_ssh_user parameter in the dynamic inventory. The -u option overrides this parameter.
     • -m [MODULE] to use a specific Ansible module. The default is command, which executes Linux commands.
     • -a [MODULE_ARGS] to define arguments for the chosen module.