When you start an instance from an image, OpenStack creates a local copy of the image on the compute node where the instance starts. You can observe OpenStack instances in vSphere as VMs, but you must manage them in OpenStack.


Verify that images, flavors, block storage, and networks are configured and available to start an instance.


  1. Log in to the VMware Integrated OpenStack dashboard.
  2. Select the project from the drop-down menu in the title bar.
  3. Select Project > Compute > Images.
    The Images page lists the images available to the current user.
  4. In the Actions column of the image, click Launch.
  5. On the Details tab .
    Setting Description
    Availability Zone Set by default to the availability zone that the cloud provider gives, for example: nova.
    Instance Name Name assigned to the VM. This value is a label and is not validated. When you create an instance, a UUID is assigned to the instance. When you view the VM in vSphere, you can identify the instance by the UUID but not by the instance name.
    Flavor Size of the instance to start. The cloud administrator defines and manages flavors.
    Instance Count Number of instances started. The default is 1.
    Instance Boot Source Select Boot from image, and select the image from the list.
  6. On the Access & Security tab of the Launch Instance dialog box .
    Setting Description
    Key Pair

    Specify a key pair.

    If the image uses a static root password or a static key set, you do not need to provide a key pair to start the instance, but using a key pair is a best practice.

    Security Groups

    Select the security groups to be assigned to the instance.

    Security groups are sets of rules that determine which incoming network traffic is forwarded to instances. If you did not create security groups, you can assign only the default security group to the instance.

  7. On the Networking tab, click the + icon in the Available Networks field to add a network to the instance.
  8. (Optional) On the Post-Creation tab, specify a customization script that runs after the instance launches.
  9. On the Advanced Options tab, select the type of disk partition from the drop-down list.
    Setting Description
    Automatic The entire disk is a single partition and resizes.
    Manual Enables faster build times but requires manual partitioning.
  10. Click Launch.
    The new instance starts on a node in the Compute cluster.
  11. To view the new instance, select Project > Compute > Instances.
    The Instances page shows the instance name, its private and public IP addresses, size, status, task, and power state.