Procedure

1. In an environment file, set the value of the GlanceCacheEnabled parameter to true, which automatically sets the flavor value to keystone+cachemanagement in the glance-api.conf heat template:

   parameter_defaults:
       GlanceCacheEnabled: true

2. Include the environment file in the openstack overcloud deploy command when you redeploy the overcloud.

3. Optional: Tune the glance_cache_pruner to an alternative frequency when you redeploy the overcloud. The following example shows a frequency of 5 minutes:

   parameter_defaults:
     ControllerExtraConfig:
       glance::cache::pruner::minute: '*/5'

   Adjust the frequency according to your needs to avoid file system full scenarios. Include the following elements when you choose an alternative frequency:

   • The size of the files that you want to cache in your environment.
   • The amount of available file system space.
   • The frequency at which the environment caches images.

1. In the dashboard, select Project > Compute > Images.
2. Click Create Image.
3. Fill out the values, and click Create Image.

1. In the dashboard, select Project > Compute > Images.

2. Click Edit Image from the list.

   Note

   The Edit Image option is available only when you log in as an admin user. When you log in as a demo user, you have the option to Launch an instance or Create Volume.

3. Update the fields and click Update Image . You can update the following values - name, description, kernel ID, ramdisk ID, architecture, format, minimum disk, minimum RAM, public, protected.
4. Click the drop-down menu and select Update Metadata option.
5. Specify metadata by adding items from the left column to the right one. In the left column, there are metadata definitions from the Image Service Metadata Catalog. Select Other to add metadata with the key of your choice and click Save when finished.

1. In the dashboard, select Project > Compute > Images.
2. Select the image you want to delete and click Delete Images.

Procedure

1. Import image data to multiple, specified stores:

   $ glance image-create-via-import \
   --container-format bare \
   --name IMAGE-NAME \
   --import-method web-download \
   --uri URI \
   --stores STORE1,STORE2,STORE3

   • Replace IMAGE-NAME with the name of the image you want to import.
   • Replace URI with the URI of the image.
   • Replace STORE1, STORE2, and STORE3 with the names of the stores to which you want to import the image data.
   • Alternatively, replace --stores with --all-stores true to upload the image to all the stores.

Procedure

1. Import image data to multiple, specified stores:

   $ glance image-create-via-import \
   --container-format bare \
   --name IMAGE-NAME \
   --import-method web-download \
   --uri URI \
   --stores STORE1,STORE2

   • Replace IMAGE-NAME with the name of the image you want to import.
   • Replace URI with the URI of the image.
   • Replace STORE1, STORE2, and STORE3 with the names of stores to which you want to copy the image data.

   • Alternatively, replace --stores with --all-stores true to upload the image to all the stores.

     Note

     With the --allow-failure parameter set to false, the Image service does not ignore stores that fail to import the image data. You can view the list of failed stores with the image property os_glance_failed_import. For more information see Checking the progress of image import operation.

2. Verify that the image data was added to specific stores:

   $ glance image-show IMAGE-ID | grep stores

   Replace IMAGE-ID with the ID of the original existing image.

   The output displays a comma-delimited list of stores.

Procedure

1. Import image data to a single store:

   $ glance image-create-via-import \
   --container-format bare \
   --name IMAGE-NAME \
   --import-method web-download \
   --uri URI \
   --store STORE

   • Replace IMAGE-NAME with the name of the image you want to import.
   • Replace URI with the URI of the image.

   • Replace STORE with the name of the store to which you want to copy the image data.

     Note

     If you do not include the options of --stores, --all-stores, or --store in the command, the Image service creates the image in the central store.

2. Verify that the image data was added to specific store:

   $ glance image-show IMAGE-ID | grep stores

   Replace IMAGE-ID with the ID of the original existing image.

   The output displays a comma-delimited list of stores.

Procedure

1. Verify that the image data was added to specific stores:

   $ glance image-show IMAGE-ID

   Replace IMAGE-ID with the ID of the original existing image.

   The output displays a comma-delimited list of stores similar to the following example snippet:

   | os_glance_failed_import       |
   | os_glance_importing_to_stores | central,dcn0,dcn1
   | status                        | importing

2. Monitor the status of the image import operation. When you precede a command with watch, the command output refreshes every two seconds.

   $ watch glance image-show IMAGE-ID

   Replace IMAGE-ID with the ID of the original existing image.

   The status of the operation changes as the image import operation progresses:

   | os_glance_failed_import       |
   | os_glance_importing_to_stores | dcn0,dcn1
   | status                        | importing

   Output that shows that an image failed to import resembles the following example:

   | os_glance_failed_import       | dcn0
   | os_glance_importing_to_stores | dcn1
   | status                        | importing

   After the operation completes, the status changes to active:

   | os_glance_failed_import       | dcn0
   | os_glance_importing_to_stores |
   | status                        | active

Procedure

1. Copy image data to all available stores:

   $ glance image-import IMAGE-ID \
   --all-stores true \
   --import-method copy-image

   Replace IMAGE-ID with the name of the image you want to copy.

2. Confirm that the image data successfully replicated to all available stores:

   $ glance image-list --include-stores

   For information about how to check the status of the image import operation, see Checking the progress of the image import operation.

Procedure

1. Copy image data to specific stores:

   $ glance image-import IMAGE-ID \
   --stores STORE1,STORE2 \
   --import-method copy-image

   • Replace IMAGE-ID with the name of the image you want to copy.
   • Replace STORE1 and STORE2 with the names of the stores to which you want to copy the image data.

2. Confirm that the image data successfully replicated to the specified stores:

   $ glance image-list --include-stores

   For information about how to check the status of the image import operation, see Checking the progress of the image import operation.

1. In the dashboard, select Project.
2. Select Network > Networks, and ensure there is a private network to which you can attach the new instance (to create a network, see Create a Network section in the Networking Guide).
3. Select Compute > Access & Security > Key Pairs, and ensure there is a key pair (to create a key pair, see Section 4.2.1.1, “Create a Key Pair”).

4. Ensure that you have either an image or a volume that can be used as a boot source:

   • To view boot-source images, select the Images tab (to create an image, see Section 1.2.1, “Creating an image”).
   • To view boot-source volumes, select the Volumes tab (to create a volume, see Create a Volume in the Storage Guide).
5. Select Compute > Access & Security > Security Groups, and ensure you have created a security group rule (to create a security group, see Project Security Management in the Users and Identity Management Guide).

1. In the dashboard, select Project > Compute > Instances.
2. Click Launch Instance.
3. Fill out the fields (those marked with '* ' are required), and click Launch.

1. Ensure communication between hosts by setting up each host with SSH key authentication so that Compute can use SSH to move disks to other hosts (for example, compute nodes can share the same SSH key).

2. Enable resizing on the original host by setting the allow_resize_to_same_host parameter to "True" in your Compute environment file.

   Note

   The allow_resize_to_same_host parameter does not resize the instance on the same host. Even if the parameter equals "True" on all Compute nodes, the scheduler does not force the instance to resize on the same host. This is the expected behavior.

3. In the dashboard, select Project > Compute > Instances.
4. Click the instance’s Actions arrow, and select Resize Instance.
5. Select a new flavor in the New Flavor field.

6. If you want to manually partition the instance when it launches (results in a faster build time):

   1. Select Advanced Options.
   2. In the Disk Partition field, select Manual.
7. Click Resize.

1. In the dashboard, select Project > Compute > Instances, and select your instance.
2. Click Terminate Instance.

1. Click the check boxes in the first column for the instances that you want to start. If you want to select all of the instances, click the check box in the first row in the table.
2. Click More Actions above the table and select Start Instances.

Procedure

1. List the available QoS policies:

   (overcloud)$ openstack network qos policy list

   ----------------------------------------------------------------+
   | ID                                   | Name    | Shared | Default | Project                          |
   ----------------------------------------------------------------+
   | 6d771447-3cf4-4ef1-b613-945e990fa59f | policy2 | True   | False   | ba4de51bf7694228a350dd22b7a3dc24 |
   | 78a24462-e3c1-4e66-a042-71131a7daed5 | policy1 | True   | False   | ba4de51bf7694228a350dd22b7a3dc24 |
   | b80acc64-4fc2-41f2-a346-520d7cfe0e2b | policy0 | True   | False   | ba4de51bf7694228a350dd22b7a3dc24 |
   ----------------------------------------------------------------+

2. Check the rules of each of the available policies to determine which has the required minimum bandwidth:

   (overcloud)$ openstack network qos policy show policy0

   ----------------------------------------------------------------------------------------------------+
   | Field       | Value                                                                                 |
   ----------------------------------------------------------------------------------------------------+
   | description |                                                                                                                                                                                                                                                                                                                                                                     |
   | id          | b80acc64-4fc2-41f2-a346-520d7cfe0e2b                                                                                                                                                                                                                                                                                                                                |
   | is_default  | False                                                                                                                                                                                                                                                                                                                                                               |
   | location    | cloud=', project.domain_id=, project.domain_name='Default, project.id=ba4de51bf7694228a350dd22b7a3dc24, project.name=admin, region_name=regionOne, zone=                                                                                                                                                                                                    |
   | name        | policy0                                                                                                                                                                                                                                                                                                                                                             |
   | project_id  | ba4de51bf7694228a350dd22b7a3dc24                                                                                                                                                                                                                                                                                                                                    |
   | rules       | [{min_kbps: 100000, direction: egress, id: d46218fe-9218-4e96-952b-9f45a5cb3b3c, qos_policy_id: b80acc64-4fc2-41f2-a346-520d7cfe0e2b, type: minimum_bandwidth}, {min_kbps: 100000, direction: ingress, id: 1202c4e3-a03a-464c-80d5-0bf90bb74c9d, qos_policy_id: b80acc64-4fc2-41f2-a346-520d7cfe0e2b, type: minimum_bandwidth}] |
   | shared      | True                                                                                                                                                                                                                                                                                                                                                                |
   | tags        | []                                                                                                                                                                                                                                                                                                                                                                  |
   ----------------------------------------------------------------------------------------------------+

3. Create a port from the appropriate policy:

   (overcloud)$ openstack port create port-normal-qos --network net0 --qos-policy policy0

4. Create an instance, specifying the NIC port to use:

   $ openstack server create --flavor cirros256 --image cirros-0.3.5-x86_64-disk --nic port-id=port-normal-qos --wait qos_instance

   An "ACTIVE" status in the output indicates that you have successfully created the instance on a host that can provide the requested guaranteed minimum bandwidth.

1. In the dashboard, select the Project tab, and click Compute > Access & Security.
2. On the Security Groups tab, click + Create Security Group.
3. Provide a name and description for the group, and click Create Security Group.

1. Change the permissions of the generated key-pair certificate.

   $ chmod 600 os-key.pem

2. Check whether ssh-agent is already running:

   # ps -ef | grep ssh-agent

3. If not already running, start it up with:

   # eval `ssh-agent`

4. On your local machine, load the key-pair certificate into SSH. For example:

   $ ssh-add ~/.ssh/os-key.pem

5. You can now SSH into the file with the user supplied by the image.

1. In the /etc/openstack-dashboard/local_settings file, set the change_set_password parameter value to True.

   can_set_password: True

2. Set the inject_password parameter to "True" in your Compute environment file.

   inject_password=true

3. Restart the Compute service.

   # service nova-compute restart

1. In the dashboard, select Project > Compute > Instances.
2. Select the instance from which you want to create a snapshot.
3. In the Actions column, click Create Snapshot.

4. In the Create Snapshot dialog, enter a name for the snapshot and click Create Snapshot.

   The Images category now shows the instance snapshot.

1. In the dashboard, select Project > Images.
2. All snapshots you created, appear under the Project option.

3. For every snapshot you create, you can perform the following functions, using the dropdown list:

   1. Use the Create Volume option to create a volume and entering the values for volume name, description, image source, volume type, size and availability zone. For more information, see Create a Volume in the Storage Guide.
   2. Use the Edit Image option to update the snapshot image by updating the values for name, description, Kernel ID, Ramdisk ID, Architecture, Format, Minimum Disk (GB), Minimum RAM (MB), public or private. For more information, see Section 1.2.3, “Update an image”.
   3. Use the Delete Image option to delete the snapshot.

1. In the dashboard, select Project > Compute > Images.
2. Select the snapshot from which you want to restore the instance.
3. In the Actions column, click Launch Instance.
4. In the Launch Instance dialog, enter a name and the other details for the instance and click Launch.

1. Add the rescue image to the Image service:

   # glance image-create --name IMAGE_NAME --disk-format qcow2 \
     --container-format bare --is-public True --file IMAGE_PATH

   Here IMAGE_NAME is the name of the image, IMAGE_PATH is the location of the image.

2. Use the image-list command to obtain the IMAGE_ID required for launching an instace in the rescue mode.

   # glance image-list

1. Since you need to rescue an instance with a specific image, rather than the default one, use the --image parameter:

   # nova rescue --image IMAGE_ID VIRTUAL_MACHINE_ID

   Here IMAGE_ID is the ID of the image you want to use and VIRTUAL_MACHINE_ID is ID of a virtual machine that you want to rescue.

   Note

   The nova rescue command allows an instance to perform a soft shut down. This allows the guest operating system to perform a controlled shutdown before the instance is powered off. The shut down behavior is configured using shutdown_timeout in your Compute configuration file. The value stands for the overall period (in seconds) a guest operation system is allowed to complete the shutdown. The default timeout is 60 seconds.

   The timeout value can be overridden on a per image basis by means of os_shutdown_timeout that is an image metadata setting allowing different types of operating systems to specify how much time they need to shut down cleanly.

2. Reboot the virtual machine.
3. Confirm the status of the virtual machine is RESCUE on the controller node by using nova list command or by using dashboard.
4. Log in to the new virtual machine dashboard by using the password for rescue mode.

1. Execute the following commands on the controller node.

   # nova unrescue VIRTUAL_MACHINE_ID

   Here VIRTUAL_MACHINE_ID is ID of a virtual machine that you want to unrescue.

Procedure

1. Create a file with instructions for cloud-init. For example, create a bash script that installs and enables a web server on the instance:

   $ vim /home/scripts/install_httpd
   #!/bin/bash
   
   yum -y install httpd python-psycopg2
   systemctl enable httpd --now

2. Launch an instance with the --user-data option to pass the bash script:

   $ openstack server create \
   --image rhel8 \
   --flavor default \
   --nic net-id=web-server-network \
   --security-group default \
   --key-name web-server-keypair \
   --user-data /home/scripts/install_httpd \
   --wait web-server-instance

3. When the instance state is active, attach a floating IP address:

   $ openstack floating ip create web-server-network
   $ openstack server add floating ip web-server-instance 172.25.250.123

4. Log in to the instance with SSH:

   $ ssh -i ~/.ssh/web-server-keypair cloud-user@172.25.250.123

5. Check that the customization was successfully performed. For example, to check that the web server has been installed and enabled, enter the following command:

   $ curl http://localhost | grep Test
   <title>Test Page for the Apache HTTP Server on Red Hat Enterprise Linux</title>
   <h1>Red Hat Enterprise Linux <strong>Test Page</strong></h1>

6. Review the /var/log/cloud-init.log file for relevant messages, such as whether or not the cloud-init executed:

   $ sudo less /var/log/cloud-init.log
   ...output omitted...
   ...util.py[DEBUG]: Cloud-init v. 0.7.9 finished at Sat, 23 Jun 2018 02:26:02 +0000. Datasource DataSourceOpenStack [net,ver=2].  Up 21.25 seconds

Procedure

1. Launch an instance with the --property <key=value> option. For example, to mark the instance as a webserver, set the following property:

   $ openstack server create \
   --image rhel8 \
   --flavor default \
   --property role=webservers \
   --wait web-server-instance

2. Optional: Add an additional property to the instance after it is created, for example:

   $ openstack server set \
   --property region=emea \
   --wait web-server-instance

Procedure

1. Enable the config drive, and specify a file that contains content that you want to make available in the config drive. For example, the following command creates a new instance named config-drive-instance and attaches a config drive that contains the contents of the file my-user-data.txt:

   (overcloud)$ openstack server create --flavor m1.tiny \
     --config-drive true \
     --user-data ./my-user-data.txt \
     --image cirros config-drive-instance

   This command creates the config drive with the volume label of config-2, which is attached to the instance when it boots, and adds the contents of my-user-data.txt to the user_data file in the openstack/{version}/ directory of the config drive.

2. Log in to the instance.

3. Mount the config drive:

   • If the instance OS uses udev:

     # mkdir -p /mnt/config
     # mount /dev/disk/by-label/config-2 /mnt/config

   • If the instance OS does not use udev, you need to first identify the block device that corresponds to the config drive:

     # blkid -t LABEL="config-2" -odevice
     /dev/vdb
     # mkdir -p /mnt/config
     # mount /dev/vdb /mnt/config