Launching Instances

Launching an Instance

  1. Log in to the dashboard, choose a project, and click Launch Instance. (Note: Instances can also be launched from from the Images page.)

  2. In the Launch Instance dialog box, specify the following values and click Launch. Once submitted, the instance starts on a compute node in the cloud.

Instance Details

Availability Zone:  By default, this value is set to the current availability zone.

Instance Name:  Assign a name to the virtual machine. The name associated with the instance will become the initial host name of the server. After the server is built, if the server name is updated using the API or change the hostname directly, the name will not automatically be updated on the dashboard. Server names are not guaranteed to be unique when created which could potentially cause two instances to have the same host names.

Flavor: The flavor specifies memory and CPU topology of the instance to launch.

Instance Count:  The number of instances you would like to provision. The default value is set to one. To launch multiple instances, enter a value greater than one.  If multiple instances are launched a unique id will be appended to the name of each instance.

Instance Boot Source: There are two options available for boot source. 

1. Boot from image 

2. Boot from snapshot 

Image Name / Instance Snapshot:  These two fields are conditional fields based on your boot source selection. If you chose to launch an instance using an image, the Image Name field displays allowing you to select an image name from the drop-down list.

If you chose to launch an instance using a snapshot, the image snapshot field displays allowing you to select the snapshot name from the drop-down list.

Access & Security

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 the section called “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

Post-Creation

Customization Script: This feature allows you to specify a customization script that runs after your instance launches

Please Note:

The Instances page displays the instance name, any IP addresses it has been assigned, size, status, task, and state.

If you did not provide a key pair, security groups, or rules, users can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible without an ICMP rule configured. To access the instance through a VNC console, see the section called View instance logs and get console access.

The Instances page shows the instance's name, any IP addresses it has been assigned, size, status, task, and power state.

If you did not provide a key pair, security groups, or rules, users can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible without an ICMP rule configured. To access the instance through a VNC console, see the section called View instance logs and get console access

Have more questions? Submit a request
Powered by Zendesk