Cloud Quick Start: Difference between revisions

#*<i>Allocated</i> and <i>Available</i> lists: The flavor determines what type of hardware is used for your VM, which determines how much memory and processing capabilities it has. The <i>Available</i> list shows all the flavors available for your chosen boot image. Click on the > icon at the far left of a row to see how that particular flavor matches up with what you have been allocated for your project. If there is an alert icon on one of the specifications, that means that your project doesn't have enough of that resource to support that flavor. Choose a flavor that your project can support (i.e. doesn't issue an alert)  and click on the upwards arrow on the far right of that row. That flavor should now show up in the <i>Allocated'' list. For more details, see [[Virtual machine flavors]]. <br /><br /><br /><br /><br /><br /><br /><br />

#<i>Networks:'' Do not change this now.[[File:Security groups.png|500px|thumb]]

#<i>Network Ports:'' Do not change this now. <br /><br /><br /><br /><br />

#<i>Security Groups:'' The default security group should be in the <i>Allocated'' list. If it is not, move it from <i>Available'' to <i>Allocated'' using the upwards arrow located on the far right of the group's row. For more information see [[Managing_your_cloud_resources_with_OpenStack#Security_Groups|Security Groups]].[[File:Key pair tab.png|500px|thumb]]<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />

#<i>Key Pair:'' From the <i>Available'' list, select the SSH key pair you created earlier  by clicking the upwards arrow on the far right of its row. If you do not have a key pair, you can create or import one from this window using the buttons at the top of the window (please [[#SSH key pair | see above]]). For more detailed information on managing and using key pairs see [[SSH_Keys|SSH Keys]].<br /><br />

#<i>Configuration:'' Do not change this now. For more information on customization scripts see [[Automating VM creation#Using_CloudInit|Using CloudInit]].

#<i>Server Groups:'' Do not change this now.  

#<i>Scheduler Hints:'' Do not change this now.

#<i>Metadata:'' Do not change this now.<br /><br />

Once you have reviewed all the options and defined your virtual machine, click on the <i>Launch Instance'' button and your virtual machine will be created. The list of instances will be displayed and the <i>Task'' field will show the current task for the VM; it will likely be <i>Spawning'' initially. Once the VM has spawned, it will have the power state of <i>Running''; this may take a few minutes.

On the <i>Instances'' page is a list of VMs with their IP address(es) displayed in the <i>IP Address'' column. Each VM will have at least one private IP address, but some may also have a second public IP assigned to it. When your OpenStack project is created, a local network is also created for you. This local network is used to connect VMs to each other and to an internet gateway within that project, allowing them to communicate with each other and the outside world. The private IP address provides inter VM networking but does not allow for connection to the outside world. Any VM created in your project will have a private IP address assigned to it from this network of the form <code>192.168.X.Y</code>. Public IPs allow outside services and tools to initiate contact with your VM, such as allowing you to connect to your VM via your personal computer to perform administrative tasks or serve up web content. Public IPs can also be pointed to by domain names.