Chapter 5. Creating an instance

Procedure

1. Retrieve the name or ID of the flavor that has the hardware profile that your instance requires:

   $ openstack flavor list

   Note

   Choose a flavor with sufficient size for the image to successfully boot, otherwise the instance will fail to launch.

2. Retrieve the name or ID of the image that has the software profile that your instance requires:

   $ openstack image list

   If the image that you require is not available, you can download or create a new image. For information about how to create or download cloud images, see Creating operating system images in Performing storage operations.

   Note

   If you need to attach more than 26 volumes to your instance, then the image you use to create your instance must have the following properties:

   • hw_scsi_model=virtio-scsi
   • hw_disk_bus=scsi

3. Retrieve the name or ID of the network that you want to connect your instance to:

   $ openstack network list

4. Create your instance:

   $ openstack server create --flavor <flavor> \
     --image <image> --network <network> \
     --wait myInstanceFromImage

   • Replace <flavor> with the name or ID of the flavor that you retrieved in step 1.
   • Replace <image> with the name or ID of the image that you retrieved in step 2.
   • Replace <network> with the name or ID of the network that you retrieved in step 3. You can use the --network option more than once to connect your instance to several networks, as required.

Procedure

1. Retrieve the name or ID of the image that has the software profile that your instance requires:

   $ openstack image list

   If the image that you require is not available, you can download or create a new image. For information about how to create or download cloud images, see Using Red Hat Enterprise Linux KVM instance images in Performing storage operations.

   Note

   If you need to attach more than 26 volumes to your instance, then the image you use to create your instance must have the following properties:

   • hw_scsi_model=virtio-scsi
   • hw_disk_bus=scsi

2. Create a bootable volume from the image:

   $ openstack volume create --image <image> \
   --size <size_gb> --bootable myBootableVolume

   • Replace <image> with the name or ID of the image to write to the volume, retrieved in step 1.
   • Replace <size_gb> with the size of the volume in GB.

3. Retrieve the name or ID of the flavor that has the hardware profile that your instance requires:

   $ openstack flavor list

4. Retrieve the name or ID of the network that you want to connect your instance to:

   $ openstack network list

5. Create an instance with the bootable volume:

   $ openstack server create --flavor <flavor> \
    --volume myBootableVolume --network <network> \
    --wait myInstanceFromVolume

   • Replace <flavor> with the name or ID of the flavor that you retrieved in step 3.
   • Replace <network> with the name or ID of the network that you retrieved in step 4. You can use the --network option more than once to connect your instance to several networks, as required.

Procedure

1. Retrieve the name or ID of the flavor that has the hardware profile that your instance requires:

   $ openstack flavor list

   Note

   Choose a flavor with sufficient size for the image to successfully boot, otherwise the instance will fail to launch.

   Tip

   You can specify the NUMA affinity policy that is applied to your instance for PCI passthrough devices and SR-IOV interfaces, by selecting a flavor that has the policy you require. For more information on the available policies, see Instance PCI NUMA affinity policy in Flavor metadata in Configuring the Compute service for instance creation. If you choose a flavor with a NUMA affinity policy, then the image that you use must have either the same NUMA affinity policy or no NUMA affinity policy.

2. Retrieve the name or ID of the image that has the software profile that your instance requires:

   $ openstack image list

   If the image that you require is not available, you can download or create a new image. For information about how to create or download cloud images, see Using Red Hat Enterprise Linux KVM instance images in Performing storage operations.

   Tip

   You can specify the NUMA affinity policy that is applied to your instance for PCI passthrough devices and SR-IOV interfaces, by selecting an image that has the policy you require. For more information on the available policies, see Instance PCI NUMA affinity policy in Flavor metadata in Configuring the Compute service for instance creation. If you choose an image with a NUMA affinity policy, then the flavor that you use must have either the same NUMA affinity policy or no NUMA affinity policy.

3. Retrieve the name or ID of the network that you want to connect your instance to:

   $ openstack network list

4. Create the type of port that you require for your SR-IOV interface:

   $ openstack port create --network <network> \
    --vnic-type <vnic_type> mySriovPort

   • Replace <network> with the name or ID of the network you retrieved in step 3.

   • Replace <vnic_type> with the one of the following values:

     • direct: Creates a direct mode SR-IOV virtual function (VF) port.
     • direct-physical: Creates a direct mode SR-IOV physical function (PF) port.
     • macvtap: Creates an indirect mode SR-IOV VF port that uses MacVTap to expose the virtio interface to the instance.

5. Create your instance:

   $ openstack server create --flavor <flavor> \
     --image <image> --port <port> \
     --wait mySriovInstance

   • Replace <flavor> with the name or ID of the flavor that you retrieved in step 1.
   • Replace <image> with the name or ID of the image that you retrieved in step 2.
   • Replace <port> with the name or ID of the port that you created in step 4.

Procedure

1. Verify that the port_numa_affinity_policy extension is enabled in the Networking service (neutron):

   $ oc get openstackcontrolplane -o yaml | grep -A 10 "neutron:"

   If the port_numa_affinity_policy extension is not listed in the extension_drivers configuration, enable it by adding port_numa_affinity_policy to extension_drivers in the Neutron definition of OpenStackControlPlane:

   neutron:
     template:
       customServiceConfig: |
         [ml2]
         extension_drivers=qos,port_security,dns_domain_ports,port_numa_affinity_policy

   Note

   The configuration method differs when you use a third-party Neutron mechanism driver.

2. Create a port with the NUMA affinity policy that you require:

   $ openstack port create --network <network> \
     [--numa-policy-required | --numa-policy-preferred | --numa-policy-legacy] \
     myNUMAAffinityPort

   • Replace <network> with the name or ID of the tenant network that you want to connect your instance to.

   • Use one of the following options to specify the NUMA affinity policy to apply to the port:

     • --numa-policy-required - NUMA affinity policy required to schedule this port.
     • --numa-policy-preferred - NUMA affinity policy preferred to schedule this port.
     • --numa-policy-legacy - NUMA affinity policy using legacy mode to schedule this port.

3. Create your instance:

   $ openstack server create --flavor <flavor> \
     --image <image> --port <port> \
     --wait myNUMAAffinityInstance

   • Replace <flavor> with the name or ID of the flavor that has the hardware profile that you require for your instance.
   • Replace <image> with the name or ID of the image that has the software profile that you require for your instance.
   • Replace <port> with the name or ID of the port that you created in step 1.