1. Log in to the dashboard.

2. From the PROJECT on the Project tab, select the appropriate project.

3. On the Project tab, click Images.

4. Click Create Image.

   The Create An Image dialog box appears.

5. Enter the following values:

   Name	Enter a name for the image.
   Description	Optionally, enter a brief description of the image.
   Image Source	Choose the image source from the list. Your choices are Image Location and Image File.
   Image File or Image Location	Based on your selection for Image Source, you either enter the location URL of the image in the Image Location field or browse to the image file on your system and add it.
   Format	Select the correct format (for example, QCOW2) for the image.
   Architecture	Specify the architecture. For example, i386 for a 32-bit architecture or x86-64 for a 64-bit architecture.
   Minimum Disk (GB) and Minimum RAM (MB)	Leave these optional fields empty.
   Public	Select this check box to make the image public to all users with access to the current project.
   Protected	Select this check box to ensure that only users with permissions can delete the image.

6. Click Create Image.

   The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

1. Log in to the dashboard.

2. From the PROJECT on the Project tab, select the appropriate project.

3. On the Project tab, click Images.

4. Select the image that you want to edit.

5. In the Actions column, click More and then select Edit from the list.

6. In the Update Image dialog box, you can perform the following actions:

   • Change the name of the image.

   • Select the Public check box to make the image public.

   • Clear the Public check box to make the image private.

7. Click Update Image.

1. Log in to the dashboard.

2. From the PROJECT on the Project tab, select the appropriate project.

3. On the Project tab, click Images.

4. Select the images that you want to delete.

5. Click Delete Images.

6. In the Confirm Delete Image dialog box, click Delete Images to confirm the deletion.

1. Log in to the dashboard, choose a project, and click Access & Security. The Security Groups tab shows the security groups that are available for this project.

2. Select the default security group and click Edit Rules.

3. To allow SSH access, click Add Rule.

4. In the Add Rule dialog box, enter the following values:

   Rule	SSH
   Remote	CIDR
   CIDR	0.0.0.0/0

   Note

   To accept requests from a particular range of IP addresses, specify the IP address block in the CIDR box.

5. Click Add.

   Instances will now have SSH port 22 open for requests from any IP address.

6. To add an ICMP rule, click Add Rule.

7. In the Add Rule dialog box, enter the following values:

   Rule	All ICMP
   Direction	Ingress
   Remote	CIDR
   CIDR	0.0.0.0/0

8. Click Add.

   Instances will now accept all incoming ICMP packets.

1. Log in to the dashboard, choose a project, and click Access & Security.

2. Click the Keypairs tab, which shows the key pairs that are available for this project.

3. Click Create Keypair.

4. In the Create Keypair dialog box, enter a name for your key pair, and click Create Keypair.

5. Respond to the prompt to download the key pair.

1. Log in to the dashboard, choose a project, and click Access & Security.

2. Click the Keypairs tab, which shows the key pairs that are available for this project.

3. Click Import Keypair.

4. In the Import Keypair dialog box, enter the name of your key pair, copy the public key into the Public Key box, and then click Import Keypair.

5. Save the *.pem file locally.

6. To change its permissions so that only you can read and write to the file, run the following command:

   $ chmod 0600 yourPrivateKey.pem

   Note

   If you are using the dashboard from a Windows computer, use PuTTYgen to load the *.pem file and convert and save it as *.ppk. For more information see the WinSCP web page for PuTTYgen.

7. To make the key pair known to SSH, run the ssh-add command.

   $ ssh-add yourPrivateKey.pem

1. Log in to the dashboard, choose a project, and click Access & Security.

2. Click the Floating IPs tab, which shows the floating IP addresses allocated to instances.

3. Click Allocate IP to Project.

4. Choose the pool from which to pick the IP address.

5. Click Allocate IP.

6. In the Floating IPs list, click Associate.

7. In the Manage Floating IP Associations dialog box, choose the following options:

   • The IP Address field is filled automatically, but you can add a new IP address by clicking the + button.

   • In the Ports to be associated field, select a port from the list.

     The list shows all the instances with their fixed IP addresses.

8. Click Associate.

1. Log in to the dashboard, choose a project, and click Images.

   The dashboard shows the images that have been uploaded to OpenStack Image Service and are available for this project.

   For details on creating images, see Creating images manually in the OpenStack Virtual Machine Image Guide.

2. Select an image and click Launch.

3. In the Launch Instance dialog box, specify the following values:

   Details tab
   Availability Zone	By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
   Instance Name	Assign a name to the virtual machine. Note The name you assign here becomes the initial host name of the server. After the server is built, if you change the server name in the API or change the host name directly, the names are not updated in the dashboard. Server names are not guaranteed to be unique when created so you could have two instances with the same host name.
   Flavor	Specify the size of the instance to launch. Note The flavor is selected based on the size of the image selected for launching an instance. For example, while creating an image, if you have entered the value in the Minimun RAM (MB) field as 2048, then on selecting the image, the default flavor is m1.small.
   Instance Count	To launch multiple instances, enter a value greater than 1. The default is 1.
   Instance Boot Source	Your options are: Boot from image If you choose this option, a new field for Image Name displays. You can select the image from the list. Boot from snapshot If you choose this option, a new field for Instance Snapshot displays. You can select the snapshot from the list. Boot from volume If you choose this option, a new field for Volume displays. You can select the volume from the list. Boot from image (creates a new volume) With this option, you can boot from an image and create a volume by entering the Device Size and Device Name for your volume. Click the Delete on Terminate option to delete the volume on terminating the instance. Boot from volume snapshot (creates a new volume) Using this option, you can boot from a volume snapshot and create a new volume by choosing Volume Snapshot from a list and adding a Device Name for your volume. Click the Delete on Terminate option to delete the volume on terminating the instance. Since you are launching an instance from an image, Boot from image is chosen by default.
   Image Name	This field changes based on your previous selection. Since you have chosen to launch an instance using an image, the Image Name field displays. Select the image name from the dropdown list.
   Access & Security tab
   Keypair	Specify a key pair. If the image uses a static root password or a static key set (neither is recommended), you do not need to provide a key pair to launch the instance.
   Security Groups	Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. For details, see Section 3.1, “Add a rule to the default security group”. If you have not created any security groups, you can assign only the default security group to the instance.
   Networking tab
   Selected Networks	To add a network to the instance, click the + in the Available Networks field.
   Post-Creation tab
   Customization Script	Specify a customization script that runs after your instance launches.
   Advanced Options tab
   Disk Partition	Select the type of disk partition from the dropdown list. Automatic Entire disk is single partition and automatically resizes. Manual Faster build times but requires manual partitioning.

4. Click Launch.

   The instance starts on a compute node in the cloud.

1. Copy the IP address for your instance.

2. Use the ssh command to make a secure connection to the instance. For example:

   $ ssh -i MyKey.pem demo@10.0.0.2

3. At the prompt, type yes.

1. Log in to the dashboard, choose a project, and click Overview.

2. To query the instance usage for a month, select a month and click Submit.

3. To download a summary, click Download CSV Summary.

1. Log in to the dashboard, choose a project, and click Instances.

2. Select the instance from which to create a snapshot.

3. In the Actions column, click Create Snapshot.

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

   The Images category shows the instance snapshot.

1. Log in to the dashboard, choose a project, and click Instances.

2. Select an instance.

3. In the More list in the Actions column, select the state.

   You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it.

1. Log in to the dashboard, choose a project, and click Networks.

2. Click Create Network.

3. In the Create Network dialog box, specify the following values.

   Network tab
   Network Name	Specify a name to identify the network.
   Subnet tab
   Create Subnet	Select this check box to create a subnet You do not have to specify a subnet when you create a network, but if you do not, any attached instance receives an Error status.
   Subnet Name	Specify a name for the subnet.
   Network Address	Specify the IP address for the subnet.
   IP Version	Select IPv4 or IPv6.
   Gateway IP	Specify an IP address for a specific gateway. This parameter is optional.
   Disable Gateway	Select this check box to disable a gateway IP address.
   Subnet Detail tab
   Enable DHCP	Select this check box to enable DHCP.
   Allocation Pools	Specify IP address pools.
   DNS Name Servers	Specify a name for the DNS server.
   Host Routes	Specify the IP address of host routes.

4. Click Create.

   The dashboard shows the network on the Networks tab.

1. Log in to the dashboard, choose a project, and click Routers.

2. Click Create Router.

3. In the Create Router dialog box, specify a name for the router and click Create Router.

   The new router is now displayed in the Routers tab.

4. Click the new router's Set Gateway button.

5. In the External Network field, specify the network to which the router will connect, and then click Set Gateway.

6. To connect a private network to the newly created router, perform the following steps:

   1. On the Routers tab, click the name of the router.

   2. On the Router Details page, click Add Interface.

   3. In the Add Interface dialog box, specify the following information:

      Subnet	Select a subnet.
      IP Address (optional)	Enter the router interface IP address for the selected subnet. Note: If this value is not set, then by default, the first host IP address in the subnet is used by OpenStack Networking.

      The Router Name and Router ID fields are automatically updated.

7. Click Add Interface.

1. Log in to the dashboard, choose a project, and click Containers.

2. Click Create Container.

3. In the Create Container dialog box, enter a name for the container.

4. Make the container Public or Private by choosing the option from the dropdown menu for Container Access.

5. Click Create Container.

1. Log in to the dashboard, choose a project, and click Containers.

2. Select the container in which you want to store your object.

3. Click Upload Object.

   The Upload Object To Container: <name> dialog box is displayed. <name> is the name of the container to which you are uploading the object.

4. Enter a name for the object.

5. Browse to and select the file that you want to upload.

6. Click Upload Object.

Procedure 1.1. To edit an object

1. Log in to the dashboard, choose a project, and click Containers.

2. Select the container in which you want to store your object.

3. Click More and choose Edit from the dropdown list.

   The Edit Object dialog box is displayed.

4. Browse to and select the file that you want to upload.

5. Click Update Object.

Procedure 1.2. To copy an object from one container to another

1. Log in to the dashboard, choose a project, and click Containers.

2. Select the container in which you want to store your object.

3. Click More and choose Copy from the dropdown list.

4. In the Copy Object: launch dialog box, enter the following values:

   • Destination Container: Choose the destination container from the list.

   • Path: Specify a path in which the new copy should be stored inside of the selected container.

   • Destination object name: Enter a name for the object in the new container.

5. Click Copy Object.

Procedure 1.3. To create a metadata-only object without a file

You can create a new object in a container without a file and can upload the file later when it is ready. This temporary object acts a place-holder for a new object, and enables the user to share object metadata and URL info in advance.

1. Log in to the dashboard, choose a project, and click Containers.

2. Select the container in which you want to store your object.

3. Click Upload Object.

   The Upload Object To Container: <name> dialog box is displayed. <name> is the name of the container to which you are uploading the object.

4. Enter a name for the object.

5. Click Update Object.

Procedure 1.4. To create a pseudo-folder

Pseudo-folders are similar to folders in your desktop operating system. They are virtual collections defined by a common prefix on the object's name.

1. Log in to the dashboard, choose a project, and click Containers.

2. Select the container in which you want to store your object.

3. Click Create Pseudo-folder.

   The Create Pseudo-Folder in Container <name> dialog box is displayed. <name> is the name of the container to which you are uploading the object.

4. Enter a name for the pseudo-folder.

   A slash (/) character is used as the delimiter for pseudo-folders in the Object Store.

5. Click Create.

1. Log in to the dashboard, choose a project, and click Volumes.

2. Click Create Volume.

   In the dialog box that opens, enter or select the following values.

   Volume Name	Specify a name for the volume.
   Description	Optionally, provide a brief description for the volume.
   Type	Leave this field blank.
   Size (GB)	The size of the volume in gigabytes.
   Volume Source	Select one of the following options: No source, empty volume Creates an empty volume. Note An empty volume does not contain a file system or a partition table. Snapshot If you choose this option, a new field for Use snapshot as a source displays. You can select the snapshot from the list. Image If you choose this option, a new field for Use image as a source displays. You can select the image from the list. Select the Availability Zone from the list. By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova. Volume If you choose this option, a new field for Use volume as a source displays. You can select the volume from the list. Note Options to use a snapshot or a volume as the source for a volume are displayed only if there are existing snapshots or volumes.

3. Click Create Volume.

1. Log in to the dashboard, choose a project, and click Volumes.

2. Select the volume to add to an instance and click Edit Attachments.

3. In the Manage Volume Attachments dialog box, select an instance.

4. Enter the name of the device from which the volume is accessible by the instance.

   Note

   The actual device name might differ from the volume name because of hypervisor settings.

5. Click Attach Volume.

   The dashboard shows the instance to which the volume is now attached and the device name.

1. Log in to the dashboard, choose a project, and click Volumes.

2. Select the volume and click Edit Attachments.

3. Click Detach Volume and confirm your changes.

1. Log in to the dashboard, choose a project, and click Volumes.

2. Select a volume from which to create a snapshot.

3. From the More list, select Create Snapshot.

4. In the dialog box that opens, enter a snapshot name and a brief description.

5. Confirm your changes.

   The dashboard shows the new volume snapshot in Volume Snapshots tab.

1. Log in to the dashboard, choose a project, and click Volumes.

2. From the PROJECT on the Project tab, select the appropriate project.

3. On the Project tab, click Volumes.

4. Select the image that you want to edit.

5. In the Actions column, click Edit Volume.

6. In the Edit Volume dialog box, update the name and description of the image.

7. Click Edit Volume.

1. Log in to the dashboard, choose a project, and click Volumes.

2. Select the check boxes for the volumes that you want to delete.

3. Click Delete Volumes and confirm your choice.

   A message indicates whether the action was successful.

1. Log in to the dashboard, choose a project, and click Stacks in the Orchestration category on the Projects tab.

2. Click Launch Stack.

3. In the Select Template dialog box, specify the following values.

   Template Source	Choose the source of the template from the list.
   Template URL/File/Data	Depending on the source that you selected, enter the URL, browse to the file location, or directly include the template.
   Environment Source	Choose the source of the environment from the list. The environment files contain additional settings for the stack.
   Environment URL/File/Data	Depending on the source that you selected, enter the URL, browse to the file location, or directly include the environment.

4. Click Next.

5. In the Launch Stack dialog box, specify the following values.

   Stack Name	Enter a name to identify the stack.
   Creation Timeout (minutes)	Specify the number of minutes that can elapse before the launch of the stack times out.
   Rollback On Failure	Select this check box if you want the service to roll back changes if the stack fails to launch.
   Password for user "demo"	Specify the password that the default user uses when the stack is created.
   DBUsername	Specify the name of the database user.
   LinuxDistribution	Specify the Linux distribution that is used in the stack.
   DBRootPassword	Specify the root password for the database.
   KeyName	Specify the name of the key pair to use to log in to the stack.
   DBName	Specify the name of the database.
   DBPassword	Specify the password for the database.
   InstanceType	Specify the flavor for the instance.

6. Click Launch to create a stack.

7. The Stacks tab shows the stack.

1. Log in to the dashboard, choose a project, and click Stacks.

2. Select the stack that you want to update.

3. Click Change Stack Template.

4. In the Select Template dialog box, select the new template source or environment source.

5. Click Next.

   The Update Stack Parameters window appears.

6. Enter new values for any parameters that you want to update.

7. Click Update.

1. Log in to the dashboard, choose a project, and click Stacks.

2. Select the stack that you want to delete.

3. Click Delete Stack.

4. In the confirmation dialog box, click Delete Stack to confirm the deletion.

1. Log in to the OpenStack dashboard, choose the project for which you want to download the OpenStack RC file, and click Access & Security.

2. On the API Access tab, click Download OpenStack RC File and save the file. The filename will be of the form PROJECT-openrc.sh where PROJECT is the name of the project for which you downloaded the file.

3. Copy the PROJECT-openrc.sh file to the computer from which you want to run OpenStack commands.

   For example, copy the file to the computer from which you want to upload an image with a glance client command.

4. On any shell from which you want to run OpenStack commands, source the PROJECT-openrc.sh file for the respective project.

   In the following example, the demo-openrc.sh file is sourced for the demo project:

   $ source demo-openrc.sh

5. When you are prompted for an OpenStack password, enter the password for the user who downloaded the PROJECT-openrc.sh file.

1. In a text editor, create a file named PROJECT-openrc.sh file and add the following authentication information:

   ​
   ​export OS_USERNAME=username
   ​export OS_PASSWORD=password
   ​export OS_TENANT_NAME=projectName
   ​export OS_AUTH_URL=https://identityHost:portNumber/v2.0
   ​# The following lines can be omitted
   ​export OS_TENANT_ID=tenantIDString
   ​export OS_REGION_NAME=regionName

   The following example shows the information for a project called admin, where the OpenStack username is also admin, and the identity host is located at controller.

   ​
   ​export OS_USERNAME=admin
   ​export OS_PASSWORD=ADMIN_PASS
   ​export OS_TENANT_NAME=admin
   ​export OS_AUTH_URL=http://controller:35357/v2.0

2. On any shell from which you want to run OpenStack commands, source the PROJECT-openrc.sh file for the respective project. In this example, you source the admin-openrc.sh file for the admin project:

   $ source admin-openrc.sh

1. Write any buffered data to disk.

   For more information on taking snapshots, see the End User Guide at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/.

2. List instances to get the server name:

   $ nova list
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | ID                                   | Name                 | Status | Task State | Power State | Networks         |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer       | ACTIVE | None       | Running     | private=10.0.0.3 |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+

   In this example, the server is named myCirrosServer.

3. Use this server to create a snapshot:

   $ nova image-create myCirrosServer myCirrosImg

   The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it.

4. Get details for your image to check its status:

   $ nova image-show myCirrosImg
   
   +----------------------+--------------------------------------+
   | Property             | Value                                |
   +----------------------+--------------------------------------+
   | OS-EXT-IMG-SIZE:size | 13147648                             |
   | created              | 2014-10-22T01:47:45Z                 |
   | id                   | 901d3823-2be1-4ce3-b9b4-56330d56fd45 |
   | minDisk              | 0                                    |
   | minRam               | 0                                    |
   | name                 | myCirrosImg                          |
   | progress             | 100                                  |
   | status               | ACTIVE                               |
   | updated              | 2014-10-22T01:49:25Z                 |
   +----------------------+--------------------------------------+

   The image status changes from SAVING to ACTIVE. Only the tenant who creates the image has access to it.

You can generate a key pair or upload an existing public key.

1. To generate a key pair, run the following command:

   $ nova keypair-add KEY_NAME > MY_KEY.pem

   The command generates a key pair with the name that you specify for KEY_NAME, writes the private key to the .pem file that you specify, and registers the public key at the Nova database.

2. To set the permissions of the .pem file so that only you can read and write to it, run the following command:

   $ chmod 600 MY_KEY.pem

1. If you have already generated a key pair and the public key is located at ~/.ssh/id_rsa.pub, run the following command to upload the public key:

   $ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME

   The command registers the public key at the Nova database and names the key pair the name that you specify for KEY_NAME.

2. To ensure that the key pair has been successfully imported, list key pairs as follows:

   $ nova keypair-list

1. To list the security groups for the current project, including descriptions, enter the following command:

   $ nova secgroup-list

2. To create a security group with a specified name and description, enter the following command:

   $ nova secgroup-create SECURITY_GROUP_NAME GROUP_DESCRIPTION

3. To delete a specified group, enter the following command:

   $ nova secgroup-delete SECURITY_GROUP_NAME 

   Note

   You cannot delete the default security group for a project. Also, you cannot delete a security group that is assigned to a running instance.

Modify security group rules with the nova secgroup-*-rule commands. Before you begin, source the OpenStack RC file. For details, see Section 4, “Set environment variables using the OpenStack RC file”.

1. To list the rules for a security group, run the following command:

   $ nova secgroup-list-rules SECURITY_GROUP_NAME

2. To allow SSH access to the instances, choose one of the following options:

   • Allow access from all IP addresses, specified as IP subnet 0.0.0.0/0 in CIDR notation:

     $ nova secgroup-add-rule SECURITY_GROUP_NAME tcp 22 22 0.0.0.0/0

   • Allow access only from IP addresses from other security groups (source groups) to access the specified port:

     $ nova secgroup-add-group-rule --ip_proto tcp --from_port 22 \
      --to_port 22 SECURITY_GROUP_NAME SOURCE_GROUP_NAME

3. To allow pinging of the instances, choose one of the following options:

   • Allow pinging from all IP addresses, specified as IP subnet 0.0.0.0/0 in CIDR notation:

     $ nova secgroup-add-rule SECURITY_GROUP_NAME icmp -1 -1 0.0.0.0/0

     This allows access to all codes and all types of ICMP traffic.

   • Allow only members of other security groups (source groups) to ping instances:

     $ nova secgroup-add-group-rule --ip_proto icmp --from_port -1 \
      --to_port -1 SECURITY_GROUP_NAME SOURCE_GROUP_NAME

4. To allow access through a UDP port, such as allowing access to a DNS server that runs on a VM, choose one of the following options:

   • Allow UDP access from IP addresses, specified as IP subnet 0.0.0.0/0 in CIDR notation:

     $ nova secgroup-add-rule SECURITY_GROUP_NAME udp 53 53 0.0.0.0/0

   • Allow only IP addresses from other security groups (source groups) to access the specified port:

     $ nova secgroup-add-group-rule --ip_proto udp --from_port 53 \
      --to_port 53 SECURITY_GROUP_NAME SOURCE_GROUP_NAME

1. List the available flavors:

   $ nova flavor-list

   Note the ID of the flavor that you want to use for your instance:

   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
   | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
   | 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      |
   | 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      |
   | 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      |
   | 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      |
   | 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      |
   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+

2. List the available images:

   $ nova image-list

   Note the ID of the image from which you want to boot your instance:

   +--------------------------------------+---------------------------------+--------+--------+
   | ID                                   | Name                            | Status | Server |
   +--------------------------------------+---------------------------------+--------+--------+
   | 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.2-x86_64-uec         | ACTIVE |        |
   | df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.2-x86_64-uec-kernel  | ACTIVE |        |
   | 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE |        |
   +--------------------------------------+---------------------------------+--------+--------+

   You can also filter the image list by using grep to find a specific image, as follows:

   $ nova image-list | grep 'kernel'

   | df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.2-x86_64-uec-kernel  | ACTIVE |        |

3. List the available security groups:

   Note

   If you are an admin user, specify the --all-tenants parameter to list groups for all tenants.

   $ nova secgroup-list --all-tenants

   Note the ID of the security group that you want to use for your instance:

   +----+---------+-------------+----------------------------------+
   | Id | Name    | Description | Tenant_ID                        |
   +----+---------+-------------+----------------------------------+
   | 2  | default | default     | 66265572db174a7aa66eba661f58eb9e |
   | 1  | default | default     | b70d90d65e464582b6b2161cf3603ced |
   +----+---------+-------------+----------------------------------+

   If you have not created any security groups, you can assign the instance to only the default security group.

   You can view rules for a specified security group:

   $ nova secgroup-list-rules default

4. List the available key pairs and note the name of the key pair that you use for SSH access.

   $ nova keypair-list

1. After you gather required parameters, run the following command to launch an instance. Specify the server name, flavor ID, and image ID. Additionally:

   • If more than one network is deployed, you must specify the network ID using --nic net-id=networkID.

   • Optionally, you can provide a key name for access control and a security group for security. You can also include metadata key and value pairs. For example, you can add a description for your server by providing the --meta description="My Server" parameter.

   • You can pass user data in a local file at instance launch by using the --user-data USER-DATA-FILE parameter.

   $ nova boot --flavor FLAVOR_ID --image IMAGE_ID \
   --nic net-id=NETWORK_ID --key-name KEY_NAME \
   --user-data USER_DATA_FILE --security-groups SEC_GROUP --meta KEY=VALUE \
   INSTANCE_NAME

   For example:

   $ nova boot --flavor 1 --image 397e713c-b95b-4186-ad46-6126863ea0a9 \
   --nic net-id=3d706957-7696-4aa8-973f-b80892ff9a95 \
    --key-name KeyPair01 --user-data cloudinit.file --security-groups default\
   myCirrosServer

   Depending on the parameters that you provide, the command returns a list of server properties.

   • A status of BUILD indicates that the instance has started, but is not yet online.

   • A status of ACTIVE indicates that the instance is active.

   +-------------------------------------+--------------------------------------+
   | Property                            | Value                                |
   +-------------------------------------+--------------------------------------+
   | OS-EXT-STS:task_state               | scheduling                           |
   | image                               | cirros-0.3.2-x86_64-uec              |
   | OS-EXT-STS:vm_state                 | building                             |
   | OS-EXT-SRV-ATTR:instance_name       | instance-00000002                    |
   | flavor                              | m1.small                             |
   | id                                  | b3cdc6c0-85a7-4904-ae85-71918f734048 |
   | security_groups                     | [{u'name': u'default'}]              |
   | user_id                             | 376744b5910b4b4da7d8e6cb483b06a8     |
   | OS-DCF:diskConfig                   | MANUAL                               |
   | accessIPv4                          |                                      |
   | accessIPv6                          |                                      |
   | progress                            | 0                                    |
   | OS-EXT-STS:power_state              | 0                                    |
   | OS-EXT-AZ:availability_zone         | nova                                 |
   | config_drive                        |                                      |
   | status                              | BUILD                                |
   | updated                             | 2013-07-16T16:25:34Z                 |
   | hostId                              |                                      |
   | OS-EXT-SRV-ATTR:host                | None                                 |
   | key_name                            | None                                 |
   | OS-EXT-SRV-ATTR:hypervisor_hostname | None                                 |
   | name                                | myCirrosServer                       |
   | adminPass                           | tVs5pL8HcPGw                         |
   | tenant_id                           | 66265572db174a7aa66eba661f58eb9e     |
   | created                             | 2013-07-16T16:25:34Z                 |
   | metadata                            | {u'KEY': u'VALUE'}                   |
   +-------------------------------------+--------------------------------------+

   Copy the server ID value from the id field in the output. You use this ID to get details for or delete your server.

   Copy the administrative password value from the adminPass field. You use this value to log in to your server.

   Note

   You can also place arbitrary local files into the instance file system at creation time by using the --file <dst-path=src-path> option. You can store up to five files. For example, if you have a special authorized keys file named special_authorized_keysfile that you want to put on the instance rather than using the regular SSH key injection, you can use the --file option as shown in the following example:

   $ nova boot --image rhel-cloudimage --flavor 1 \
   --nic net-id=3d706957-7696-4aa8-973f-b80892ff9a95 \
   --file /root/.ssh/authorized_keys=special_authorized_keysfile VM-name

2. Check if the instance is online:

   $ nova list

   The list shows the ID, name, status, and private (and if assigned, public) IP addresses for all instances in the project to which you belong:

   +------------------------------------+--------------------+------+----------+-----------+----------------+
   |ID                                  |Name                |Status|Task State|Power State|Networks        |
   +------------------------------------+--------------------+------+----------+-----------+----------------+
   |84c6e57d-a6b1-44b6-81eb-fcb36afd31b5|myCirrosServer      |ACTIVE|None      |Running    |private=10.0.0.3|
   |8a99547e-7385-4ad1-ae50-4ecfaaad5f42|myInstanceFromVolume|ACTIVE|None      |Running    |private=10.0.0.4|
   +------------------------------------+--------------------+------+----------+-----------+----------------+

   If the status for the instance is ACTIVE, the instance is online.

   To view the available options for the nova list command, run the following command:

   $ nova help list

Procedure 2.1. Resize a server

1. Show information about your server, including its size, which is shown as the value of the flavor property.

   $ nova show myCirrosServer
   +--------------------------------------+----------------------------------------------------------+
   | Property                             | Value                                                    |
   +--------------------------------------+----------------------------------------------------------+
   | OS-DCF:diskConfig                    | AUTO                                                     |
   | OS-EXT-AZ:availability_zone          | nova                                                     |
   | OS-EXT-SRV-ATTR:host                 | devstack                                                 |
   | OS-EXT-SRV-ATTR:hypervisor_hostname  | devstack                                                 |
   | OS-EXT-SRV-ATTR:instance_name        | instance-00000005                                        |
   | OS-EXT-STS:power_state               | 1                                                        |
   | OS-EXT-STS:task_state                | -                                                        |
   | OS-EXT-STS:vm_state                  | active                                                   |
   | OS-SRV-USG:launched_at               | 2014-08-14T06:10:21.000000                               |
   | OS-SRV-USG:terminated_at             | -                                                        |
   | accessIPv4                           |                                                          |
   | accessIPv6                           |                                                          |
   | config_drive                         |                                                          |
   | created                              | 2014-08-14T06:09:47Z                                     |
   | flavor                               | m1.small (2)                                             |
   | hostId                               | 6e1e69b71ac9b1e6871f91e2dfc9a9b9ceca0f052a81d45385       |
   | id                                   | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5                     |
   | image                                | cirros-uec (397e713c-b95b-4186-ad46-6126863ea0a9)        |
   | key_name                             | None                                                     |
   | metadata                             | {}                                                       |
   | name                                 | myCirrosServer                                           |
   | os-extended-volumes:volumes_attached | []                                                       |
   | progress                             | 0                                                        |
   | private network                      | 10.0.0.3                                                 |
   | security_groups                      | default                                                  |
   | status                               | ACTIVE                                                   |
   | tenant_id                            | 66265572db174a7aa66eba661f58eb9e                         |
   | updated                              | 2014-08-14T22:54:56Z                                     |
   | user_id                              | 376744b5910b4b4da7d8e6cb483b06a8                         |
   +--------------------------------------+----------------------------------------------------------+

   The size (flavor) of the server is m1.small (2).

2. List the available flavors with the following command:

   $ nova flavor-list
   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
   | ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
   | 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      |
   | 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      |
   | 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      |
   | 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      |
   | 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      |
   +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+

3. To resize the server, pass the server ID or name and the new flavor to the nova resize command. Include the --poll parameter to report the resize progress.

   $ nova resize myCirrosServer 4 --poll

   Instance resizing... 100% complete
   Finished

4. Show the status for your server:

   $ nova list
   +--------------------------------------+---------------+--------+------------+-------------+-----------------------------------------+
   | ID                                   | Name          | Status | Task State | Power State | Networks                                |
   +--------------------------------------+---------------+--------+------------+-------------+-----------------------------------------+
   | 3503e70a-8ede-444c-b779-fcb36afd31b5 | CirrosServer  | RESIZE | -          | Running     | private=172.16.101.6, public=10.4.113.6 |
   +--------------------------------------+---------------+--------+------------+-------------+-----------------------------------------+

   When the resize completes, the status becomes VERIFY_RESIZE.

5. Confirm the resize:

   $ nova resize-confirm 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5

   The server status becomes ACTIVE.

• By default, when you reboot a server, it is a soft reboot.

  $ nova reboot SERVER

1. List all instances:

   $ nova list
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | ID                                   | Name                 | Status | Task State | Power State | Networks         |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer       | ACTIVE | None       | Running     | private=10.0.0.3 |
   | 8a99547e-7385-4ad1-ae50-4ecfaaad5f42 | myInstanceFromVolume | ACTIVE | None       | Running     | private=10.0.0.4 |
   | d7efd3e4-d375-46d1-9d57-372b6e4bdb7f | newServer            | ERROR  | None       | NOSTATE     |                  |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+

2. Run the nova delete command to delete the instance. The following example shows deletion of the newServer instance, which is in ERROR state:

   $ nova delete newServer

   The command does not notify that your server was deleted.

3. To verify that the server was deleted, run the nova list command:

   $ nova list
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | ID                                   | Name                 | Status | Task State | Power State | Networks         |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer       | ACTIVE | None       | Running     | private=10.0.0.3 |
   | 8a99547e-7385-4ad1-ae50-4ecfaaad5f42 | myInstanceFromVolume | ACTIVE | None       | Running     | private=10.0.0.4 |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+

   The deleted instance does not appear in the list.

1. Shut down the source VM before you take the snapshot to ensure that all data is flushed to disk. If necessary, list the instances to view get the instance name.

   $ nova list
   +--------------------------------------+------------+--------+------------------------------+
   | ID                                   | Name       | Status | Networks                     |
   +--------------------------------------+------------+--------+------------------------------+
   | c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | ACTIVE | private=10.0.0.3             |
   +--------------------------------------+------------+--------+------------------------------+

   $ nova stop example

2. Use the nova list command to confirm that the instance shows a SHUTOFF status.

   $ nova list
   +--------------------------------------+------------+---------+------------------------------+
   | ID                                   | Name       | Status  | Networks                     |
   +--------------------------------------+------------+---------+------------------------------+
   | c41f3074-c82a-4837-8673-fa7e9fea7e11 | myInstance | SHUTOFF | private=10.0.0.3             |
   +--------------------------------------+------------+---------+------------------------------+

3. Use the nova image-create command to take a snapshot. Use the nova image-list command to check the status until the status is ACTIVE:

   $ nova image-create --poll myInstance myInstanceSnapshot
   Instance snapshotting... 50% complete

   $ nova image-list
   +--------------------------------------+---------------------------------+--------+--------+
   | ID                                   | Name                            | Status | Server |
   +--------------------------------------+---------------------------------+--------+--------+
   | 657ebb01-6fae-47dc-986a-e49c4dd8c433 | cirros-0.3.2-x86_64-uec         | ACTIVE |        |
   | 72074c6d-bf52-4a56-a61c-02a17bf3819b | cirros-0.3.2-x86_64-uec-kernel  | ACTIVE |        |
   | 3c5e5f06-637b-413e-90f6-ca7ed015ec9e | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE |        |
   | f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | myInstanceSnapshot              | ACTIVE |        |
   +--------------------------------------+---------------------------------+--------+--------+

1. Get the image ID:

   $ nova image-list
   +--------------------------------------+-------------------+--------+--------------------------------------+
   | ID                                   | Name              | Status | Server                               |
   +--------------------------------------+-------------------+--------+--------------------------------------+
   | f30b204e-1ce6-40e7-b8d9-b353d4d84e7d | myInstanceSnapshot| ACTIVE | c41f3074-c82a-4837-8673-fa7e9fea7e11 |
   +--------------------------------------+-------------------+--------+--------------------------------------+

2. Download the snapshot by using the image ID that was returned in the previous step:

   $ glance image-download --file snapshot.raw f30b204e-1ce6-40e7-b8d9-b353d4d84e7d

   Note

   The glance image-download command requires the image ID and cannot use the image name.

   Ensure there is sufficient space on the destination file system for the image file.

3. Make the image available to the new environment, either through HTTP or with direct upload to a machine (scp).

1. To enable the configuration drive, pass the --config-drive=true parameter to the nova boot command.

   The following example enables the configuration drive and passes user data, two files, and two key/value metadata pairs, all of which are accessible from the configuration drive:

   $ nova boot --config-drive=true --image my-image-name \
   --nic net-id=3d706957-7696-4aa8-973f-b80892ff9a95 --key-name mykey --flavor 1 \
   --user-data ./my-user-data.txt myinstance \
   --file /etc/network/interfaces=/home/myuser/instance-interfaces \
   --file known_hosts=/home/myuser/.ssh/known_hosts \
   --meta role=webservers --meta essential=false

   You can also configure the Compute service to always create a configuration drive by setting the following option in the /etc/nova/nova.conf file:

   ​force_config_drive=true

   Note

   If a user passes the --config-drive=true flag to the nova boot command, an administrator cannot disable the configuration drive.

2. If your guest operating system supports accessing disk by label, you can mount the configuration drive as the /dev/disk/by-label/configurationDriveVolumeLabel device. In the following example, the configuration drive has the config-2 volume label.

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

   Note

   Ensure that you use at least version 0.3.1 of CirrOS for configuration drive support.

   If your guest operating system does not use udev, the /dev/disk/by-label directory is not present.

   You can use the blkid command to identify the block device that corresponds to the configuration drive. For example, when you boot the CirrOS image with the m1.tiny flavor, the device is /dev/vdb:

   # blkid -t LABEL="config-2" -odevice

   /dev/vdb

   Once identified, you can mount the device:

   # mkdir -p /mnt/config
   # mount /dev/vdb /mnt/config

1. List the extensions of the system:

   $ neutron ext-list -c alias -c name

   +-----------------+--------------------------+
   | alias           | name                     |
   +-----------------+--------------------------+
   | agent_scheduler | Agent Schedulers         |
   | binding         | Port Binding             |
   | quotas          | Quota management support |
   | agent           | agent                    |
   | provider        | Provider Network         |
   | router          | Neutron L3 Router        |
   | lbaas           | LoadBalancing service    |
   | extraroute      | Neutron Extra Route      |
   +-----------------+--------------------------+

2. Create a network:

   $ neutron net-create net1

   Created a new network:
   +---------------------------+--------------------------------------+
   | Field                     | Value                                |
   +---------------------------+--------------------------------------+
   | admin_state_up            | True                                 |
   | id                        | 2d627131-c841-4e3a-ace6-f2dd75773b6d |
   | name                      | net1                                 |
   | provider:network_type     | vlan                                 |
   | provider:physical_network | physnet1                             |
   | provider:segmentation_id  | 1001                                 |
   | router:external           | False                                |
   | shared                    | False                                |
   | status                    | ACTIVE                               |
   | subnets                   |                                      |
   | tenant_id                 | 3671f46ec35e4bbca6ef92ab7975e463     |
   +---------------------------+--------------------------------------+

   Note

   Some fields of the created network are invisible to non-admin users.

3. Create a network with specified provider network type:

   $ neutron net-create net2 --provider:network-type local

   Created a new network:
   +---------------------------+--------------------------------------+
   | Field                     | Value                                |
   +---------------------------+--------------------------------------+
   | admin_state_up            | True                                 |
   | id                        | 524e26ea-fad4-4bb0-b504-1ad0dc770e7a |
   | name                      | net2                                 |
   | provider:network_type     | local                                |
   | provider:physical_network |                                      |
   | provider:segmentation_id  |                                      |
   | router:external           | False                                |
   | shared                    | False                                |
   | status                    | ACTIVE                               |
   | subnets                   |                                      |
   | tenant_id                 | 3671f46ec35e4bbca6ef92ab7975e463     |
   +---------------------------+--------------------------------------+

   Just as shown previously, the unknown option --provider:network-type is used to create a local provider network.

• Create a subnet:

  $ neutron subnet-create net1 192.168.2.0/24 --name subnet1

  Created a new subnet:
  +------------------+--------------------------------------------------+
  | Field            | Value                                            |
  +------------------+--------------------------------------------------+
  | allocation_pools | {"start": "192.168.2.2", "end": "192.168.2.254"} |
  | cidr             | 192.168.2.0/24                                   |
  | dns_nameservers  |                                                  |
  | enable_dhcp      | True                                             |
  | gateway_ip       | 192.168.2.1                                      |
  | host_routes      |                                                  |
  | id               | 15a09f6c-87a5-4d14-b2cf-03d97cd4b456             |
  | ip_version       | 4                                                |
  | name             | subnet1                                          |
  | network_id       | 2d627131-c841-4e3a-ace6-f2dd75773b6d             |
  | tenant_id        | 3671f46ec35e4bbca6ef92ab7975e463                 |
  +------------------+--------------------------------------------------+

  The subnet-create command has the following positional and optional parameters:

  • The name or ID of the network to which the subnet belongs.

    In this example, net1 is a positional argument that specifies the network name.

  • The CIDR of the subnet.

    In this example, 192.168.2.0/24 is a positional argument that specifies the CIDR.

  • The subnet name, which is optional.

    In this example, --name subnet1 specifies the name of the subnet.

1. Create a router:

   $ neutron router-create router1

   Created a new router:
   +-----------------------+--------------------------------------+
   | Field                 | Value                                |
   +-----------------------+--------------------------------------+
   | admin_state_up        | True                                 |
   | external_gateway_info |                                      |
   | id                    | 6e1f11ed-014b-4c16-8664-f4f615a3137a |
   | name                  | router1                              |
   | status                | ACTIVE                               |
   | tenant_id             | 7b5970fbe7724bf9b74c245e66b92abf     |
   +-----------------------+--------------------------------------+

   Take note of the unique router identifier returned, this will be required in subsequent steps.

2. Link the router to the external provider network:

   $ neutron router-gateway-set ROUTER NETWORK

   Replace ROUTER with the unique identifier of the router, replace NETWORK with the unique identifier of the external provider network.

3. Link the router to the subnet:

   $ neutron router-interface-add ROUTER SUBNET

   Replace ROUTER with the unique identifier of the router, replace SUBNET with the unique identifier of the subnet.

1. Create a port with specified IP address:

   $ neutron port-create net1 --fixed-ip ip_address=192.168.2.40

   Created a new port:
   +--------------------+----------------------------------------------------------------------+
   |Field               |Value                                                                 |
   +--------------------+----------------------------------------------------------------------+
   |admin_state_up      |True                                                                  |
   |binding:capabilities|{"port_filter": false}                                                |
   |binding:vif_type    |ovs                                                                   |
   |device_id           |                                                                      |
   |device_owner        |                                                                      |
   |fixed_ips           |{"subnet_id": "15a09f6c-87a5-4d14-b2cf-03d97cd4b456", "ip_address": "192.168.2.40"}|
   |id                  |f7a08fe4-e79e-4b67-bbb8-a5002455a493                                  |
   |mac_address         |fa:16:3e:97:e0:fc                                                     |
   |name                |                                                                      |
   |network_id          |2d627131-c841-4e3a-ace6-f2dd75773b6d                                  |
   |status              |DOWN                                                                  |
   |tenant_id           |3671f46ec35e4bbca6ef92ab7975e463                                      |
   +--------------------+----------------------------------------------------------------------+

   In the previous command, net1 is the network name, which is a positional argument. --fixed-ip ip_address=192.168.2.40 is an option, which specifies the port's fixed IP address we wanted.

   Note

   When creating a port, you can specify any unallocated IP in the subnet even if the address is not in a pre-defined pool of allocated IP addresses (set by your cloud provider).

2. Create a port without specified IP address:

   $ neutron port-create net1

   Created a new port:
   +--------------------+-----------------------------------------------------------------+
   |Field               |Value                                                            |
   +--------------------+-----------------------------------------------------------------+
   |admin_state_up      |True                                                             |
   |binding:capabilities|{"port_filter": false}                                           |
   |binding:vif_type    |ovs                                                              |
   |device_id           |                                                                 |
   |device_owner        |                                                                 |
   |fixed_ips           |{"subnet_id": "15a09f6c-87a5-4d14-b2cf-03d97cd4b456", "ip_address": "192.168.2.2"} |
   |id                  |baf13412-2641-4183-9533-de8f5b91444c                             |
   |mac_address         |fa:16:3e:f6:ec:c7                                                |
   |name                |                                                                 |
   |network_id          |2d627131-c841-4e3a-ace6-f2dd75d                                  |
   |status              |DOWN                                                             |
   |tenant_id           |3671f46ec35e4bbca6ef92ab7975e463                                 |
   +--------------------+-----------------------------------------------------------------+

   Note

   Note that the system allocates one IP address if you do not specify an IP address in the neutron port-create command.

3. Query ports with specified fixed IP addresses:

   $ neutron port-list --fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40

   +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
   | id                                   | name | mac_address       | fixed_ips                                                                           |
   +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
   | baf13412-2641-4183-9533-de8f5b91444c |      | fa:16:3e:f6:ec:c7 | {"subnet_id": "15a09f6c-87a5-4d14-b2cf-03d97cd4b456", "ip_address": "192.168.2.2"}  |
   | f7a08fe4-e79e-4b67-bbb8-a5002455a493 |      | fa:16:3e:97:e0:fc | {"subnet_id": "15a09f6c-87a5-4d14-b2cf-03d97cd4b456", "ip_address": "192.168.2.40"} |
   +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+

   --fixed-ips ip_address=192.168.2.2 ip_address=192.168.2.40 is one unknown option.

   How to find unknown options? The unknown options can be easily found by watching the output of create_xxx or show_xxx command. For example, in the port creation command, we see the fixed_ips fields, which can be used as an unknown option.

1. List images, and note the ID of the image that you want to use for your volume:

   $ nova image-list

   +--------------------------------------+---------------------------------+--------+--------------------------------------+
   | ID                                   | Name                            | Status | Server                               |
   +--------------------------------------+---------------------------------+--------+--------------------------------------+
   | 397e713c-b95b-4186-ad46-6126863ea0a9 | cirros-0.3.2-x86_64-uec         | ACTIVE |                                      |
   | df430cc2-3406-4061-b635-a51c16e488ac | cirros-0.3.2-x86_64-uec-kernel  | ACTIVE |                                      |
   | 3cf852bd-2332-48f4-9ae4-7d926d50945e | cirros-0.3.2-x86_64-uec-ramdisk | ACTIVE |                                      |
   | 7e5142af-1253-4634-bcc6-89482c5f2e8a | myCirrosImage                   | ACTIVE | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 |
   | 89bcd424-9d15-4723-95ec-61540e8a1979 | mysnapshot                      | ACTIVE | f51ebd07-c33d-4951-8722-1df6aa8afaa4 |
   +--------------------------------------+---------------------------------+--------+--------------------------------------+

2. List the availability zones, and note the ID of the availability zone in which you want to create your volume:

   $ nova availability-zone-list

   +-----------------------+----------------------------------------+
   | Name                  | Status                                 |
   +-----------------------+----------------------------------------+
   | internal              | available                              |
   | |- devstack           |                                        |
   | | |- nova-conductor   | enabled :-) 2013-07-25T16:50:44.000000 |
   | | |- nova-consoleauth | enabled :-) 2013-07-25T16:50:44.000000 |
   | | |- nova-scheduler   | enabled :-) 2013-07-25T16:50:44.000000 |
   | | |- nova-cert        | enabled :-) 2013-07-25T16:50:44.000000 |
   | | |- nova-network     | enabled :-) 2013-07-25T16:50:44.000000 |
   | nova                  | available                              |
   | |- devstack           |                                        |
   | | |- nova-compute     | enabled :-) 2013-07-25T16:50:39.000000 |
   +-----------------------+----------------------------------------+

3. Create a volume with 8 GB of space, and specify the availability zone and image:

   $ cinder create 8 --display-name my-new-volume --image-id 397e713c-b95b-4186-ad46-6126863ea0a9 --availability-zone nova

   +---------------------+--------------------------------------+
   |       Property      |                Value                 |
   +---------------------+--------------------------------------+
   |     attachments     |                  []                  |
   |  availability_zone  |                 nova                 |
   |       bootable      |                false                 |
   |      created_at     |      2013-07-25T17:02:12.472269      |
   | display_description |                 None                 |
   |     display_name    |            my-new-volume             |
   |          id         | 573e024d-5235-49ce-8332-be1576d323f8 |
   |       image_id      | 397e713c-b95b-4186-ad46-6126863ea0a9 |
   |       metadata      |                  {}                  |
   |         size        |                  8                   |
   |     snapshot_id     |                 None                 |
   |     source_volid    |                 None                 |
   |        status       |               creating               |
   |     volume_type     |                 None                 |
   +---------------------+--------------------------------------+

4. To verify that your volume was created successfully, list the available volumes:

   $ cinder list

   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   |                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   | 573e024d-5235-49ce-8332-be1576d323f8 | available |  my-new-volume  |  8   |     None    |   true   |             |
   | bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol |  8   |     None    |   true   |             |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

   If your volume was created successfully, its status is available. If its status is error, you might have exceeded your quota.

1. Attach your volume to a server, specifying the server ID and the volume ID:

   $ nova volume-attach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8 /dev/vdb

   +----------+--------------------------------------+
   | Property | Value                                |
   +----------+--------------------------------------+
   | device   | /dev/vdb                             |
   | serverId | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 |
   | id       | 573e024d-5235-49ce-8332-be1576d323f8 |
   | volumeId | 573e024d-5235-49ce-8332-be1576d323f8 |
   +----------+--------------------------------------+

   Note the ID of your volume.

2. Show information for your volume:

   $ cinder show 573e024d-5235-49ce-8332-be1576d323f8

   The output shows that the volume is attached to the server with ID 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5, is in the nova availability zone, and is bootable.

   +----------------------------+-----------------------------------------------------------+
   | Property                   | Value                                                     |
   +----------------------------+-----------------------------------------------------------+
   |attachments                 |[{u'device': u'/dev/vdb', u'server_id': u'84c6e57d-a6b1-44b6-81eb-fcb36afd31b5', u'id': u'573e024d-5235-49ce-8332-be1576d323f8', u'volume_id': u'573e024d-5235-49ce-8332-be1576d323f8'}] |
   |availability_zone           | nova                                                      |
   |created_at                  | 2013-07-25T17:02:12.0000                                  |
   |display_description         | None                                                      |
   |display_name                | my-newvolume                                              |
   |id                          | 573e024d-5235-49ce-8332-be1576d323f8                      |
   |metadata                    | {}                                                        |
   |os-vol-host-attr:host       | devstack                                                  |
   |os-vol-tenant-attr:tenant_id| 66265572db174a7aa66eba661f58eb9e                          |
   |size                        | 8                                                         |
   |snapshot_id                 | None                                                      |
   |source_volid                | None                                                      |
   |status                      | in-use                                                    |
   |volume_image_metadata       | {u'kernel_id': u'df430cc2-3406-4061-b635-a51c16e488ac', u'image_id': u'397e713c-b95b-4186-ad46-6126863ea0a9', u'ramdisk_id': u'3cf852bd-2332-48f4-9ae4-7d926d50945e', u'image_name': u'cirros-0.3.2-x86_64-uec'} |
   |volume_type                 | None                                                      |
   +----------------------------+-----------------------------------------------------------+

1. To resize your volume, you must first detach it from the server.

   To detach the volume from your server, pass the server ID and volume ID to the following command:

   $ nova volume-detach 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8

   The volume-detach command does not return any output.

2. List volumes:

   $ cinder list

   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   |                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   | 573e024d-5235-49ce-8332-be1576d323f8 | available |  my-new-volume  |  8   |     None    |   true   |             |
   | bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol |  8   |     None    |   true   |             |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

   Note that the volume is now available.

3. Resize the volume by passing the volume ID and the new size (a value greater than the old one) as parameters:

   $ cinder extend 573e024d-5235-49ce-8332-be1576d323f8 10

   The extend command does not return any output.

1. To delete your volume, you must first detach it from the server.

   To detach the volume from your server and check for the list of existing volumes, see steps 1 and 2 in Section 16.4, “Resize a volume”.

2. Delete the volume using either the volume name or ID:

   $ cinder delete my-new-volume

   The delete command does not return any output.

3. List the volumes again, and note that the status of your volume is deleting:

   $ cinder list

   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   |                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   | 573e024d-5235-49ce-8332-be1576d323f8 |  deleting |  my-new-volume  |  8   |     None    |   true   |             |
   | bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol |  8   |     None    |   true   |             |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

   When the volume is fully deleted, it disappears from the list of volumes:

   $ cinder list

   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   |                  ID                  |   Status  |   Display Name  | Size | Volume Type | Bootable | Attached to |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+
   | bd7cf584-45de-44e3-bf7f-f7b50bf235e3 | available | my-bootable-vol |  8   |     None    |   true   |             |
   +--------------------------------------+-----------+-----------------+------+-------------+----------+-------------+

Procedure 3.1. To create a router and add a port to a subnet

1. Import the following modules:

   from neutronclient.v2_0 import client
   import novaclient.v1_1.client as nvclient
   from credentials import get_credentials
   from credentials import get_nova_credentials
   from utils import print_values_server

2. Get Nova Credentials. See Section 5.3, “Get Nova credentials”.

3. Instantiate the nova_client client object by using the credentials dictionary object:

   nova_client = nvclient.Client(**credentials)

4. Create a router and add a port to the subnet:

   # Replace with server_id and network_id from your environment
   
   router_id = '72cf1682-60a8-4890-b0ed-6bad7d9f5466'
   network_id = '81bf592a-9e3f-4f84-a839-ae87df188dc1'
   
   credentials = get_credentials()
   neutron = client.Client(**credentials)
   router = neutron.show_router(router_id)
   print(router)
   body_value = {'port': {
       'admin_state_up': True,
       'device_id': router_id,
       'name': 'port1',
       'network_id': network_id,
       }}
   
   response = neutron.create_port(body=body_value)
   print(response)
   print("Execution Completed")

Procedure 3.2. To delete a network

1. Import the following modules:

   from neutronclient.v2_0 import client
   from credentials import get_credentials

2. Get credentials. See Section 5.2, “Get credentials”.

3. Instantiate the neutron client object by using the credentials dictionary object:

   neutron = client.Client(**credentials)

4. Delete the network:

   body_sample = {'network': {'name': network_name,
                  'admin_state_up': True}}
   
   netw = neutron.create_network(body=body_sample)
   net_dict = netw['network']
   network_id = net_dict['id']
   print('Network %s created' % network_id)
   
   body_create_subnet = {'subnets': [{'cidr': '192.168.199.0/24',
                         'ip_version': 4, 'network_id': network_id}]}
   
   subnet = neutron.create_subnet(body=body_create_subnet)
   print('Created subnet %s' % subnet)
   
   neutron.delete_network(network_id)
   print('Deleted Network %s' % network_id)
   
   print("Execution completed")

Procedure 3.3. To list routers

1. Import the following modules:

   from neutronclient.v2_0 import client
   from credentials import get_credentials
   from utils import print_values

2. Get credentials. See Section 5.2, “Get credentials”.

3. Instantiate the neutron client object by using the credentials dictionary object:

   neutron = client.Client(**credentials)

4. List the routers

   routers_list = neutron.list_routers(retrieve_all=True)
   print_values(routers_list, 'routers')
   print("Execution completed")

   For print_values see Section 5.4, “Print values”.

Procedure 3.4. To list security groups

1. Import the following modules:

   from neutronclient.v2_0 import client
   from credentials import get_credentials
   from utils import print_values

2. Get credentials. See Section 5.2, “Get credentials”.

3. Instantiate the neutron client object by using the credentials dictionary object:

   neutron = client.Client(**credentials)

4. List Security groups

   sg = neutron.list_security_groups()
   print(sg)

Procedure 3.5. To list subnets

1. Import the following modules:

   from neutronclient.v2_0 import client
   from credentials import get_credentials
   from utils import print_values

2. Get credentials. See Section 5.2, “Get credentials”.

3. Instantiate the neutron client object by using the credentials dictionary object:

   neutron = client.Client(**credentials)

4. List subnets:

   subnets = neutron.list_subnets()
   print(subnets)

Procedure 3.6. To list the servers

1. Import the following modules:

   from credentials import get_nova_credentials_v2
   from novaclient.client import Client

2. Get Nova Credentials. See Section 6.2, “Get nova credentials v2”.

3. Instantiate the nova_client client object by using the credentials dictionary object:

   nova_client = Client(**credentials)

4. Get the list of servers by calling servers.list on nova_client object:

   print(nova_client.servers.list())

Procedure 3.7. To create a server

1. Import the following modules:

   import time
   from credentials import get_nova_credentials_v2
   from novaclient.client import Client

2. Get Nova Credentials. See Section 6.2, “Get nova credentials v2”.

3. Instantiate the nova_client client object by using the credentials dictionary object:

   nova_client = Client(**credentials)

4. In this step, search for the flavor and image to be used for creating a server. The following code assumes cirros image and m1.tiny are being used.

   image = nova_client.images.find(name="cirros")
   flavor = nova_client.flavors.find(name="m1.tiny")

5. image = nova_client.images.find(name="cirros")
   flavor = nova_client.flavors.find(name="m1.tiny")

6. In this step determine the network with which the server is going to be attached. Use this along with flavor and image to create the server.

   net_id = 'd05a7729-4bcf-4149-9d8f-6a4764520a04'
   nic_d = [{'net-id': net_id}]
   instance = nova_client.servers.create(name="vm2", image=image,
                                         flavor=flavor, key_name="keypair-1", nics=nic_d)

7. Check if the server/VM was created by calling nova_client.servers.list() after waiting for five seconds.

   print("Sleeping for 5s after create command")
   time.sleep(5)
   print("List of VMs")
   print(nova_client.servers.list)

Procedure 3.8. To Delete a Server

1. Import the following modules:

   import time
   from credentials import get_nova_credentials_v2
   from novaclient.client import Client

2. Get Nova Credentials. See Section 6.2, “Get nova credentials v2”.

3. Instantiate the nova_client client object by using the credentials dictionary object:

   nova_client = Client(**credentials)

4. Check if the server "vm1" exists using the following steps

   1. Get the list of servers: servers_list

   2. Iterate over the servers_list and compare name with "vm1"

   3. If true set the variable name server_exists as True and break from the for loop

   servers_list = nova_client.servers.list()
   server_del = "vm1"
   server_exists = False
   
   for s in servers_list:
       if s.name == server_del:
           print("This server %s exists" % server_del)
           server_exists = True
           break

5. If the server exists execute delete method of nova_client.servers object.

   nova_client.servers.delete(s)