Cloud Quick Start: Difference between revisions

**''Flavor'': The flavor defines virtual machine hardware specifications. <p>The ''c1-3.75gb-36'' flavor has one virtual CPU, 3.75GB of RAM (memory) and an ephemeral disk of 36GB. Ephemeral disks are disks created and destroyed with the instance; they reside on the local hardware running the virtual machine. Flavors starting with a "p" do not have an extra ephemeral disk and thus no "-##" on the end. They also have a very small root disk of only 2.2GB, with a typical OS taking about 770MB of that. The root disk, as you might have guessed, is mounted at the root of the Linux file system. Flavors starting with a "c" have an extra ephemeral disk attached, as well as a 20GB root disk.</p>

**''Instance Count'': Number of virtual machines to create.

**''Instance Boot Source'': What source should be used to boot the VM. <p>''Boot from image'' indicates that you wish to boot from an already created image. Another common option is ''Boot from volume'' which allows one to boot form an existing volume which is commonly done with "p" flavors.</p>

**''Image Name'': name of the image to boot from, e.g. ''CentOS-7-x86-64-GenericCloud-1503''.

**''Project Limits'': The green bars reflect the fraction of your available resources that will be consumed by the VM you are about to launch. If the bars become red, the flavor chosen will consume more resources than your project has available. Blue bars indicate any existing resources your project may be using.

*''Access & Security'' tab

**''Key Pair'': Select your SSH key pair.<p>If you have only one, it is selected by default. If you do not have a key pair, please see above [[Cloud Quick Start#SSH Key Pair]].</p>

:*''Security Groups'': Do not remove the check-mark for ''default''.

*''Networking tab'': Do not change this now. <p>Networking will be discussed later, after you have launched a virtual machine.</p>

*''Post-Creation Tab'': Do not change this now. <p>This is where you would paste a cloud-init script which can do things such as install and configure software, add users, and additional SSH keys (see [[OpenStack#Accessing a VM with Multiple Users]]) in an automated step after the VM is created. See [http://cloudinit.readthedocs.org/en/latest/index.html# cloudinit] for more details about clout-init.</p>

The ''Instances'' list will be displayed and the ''Task'' field will show the current task for the VM; it will likely be ''spawning'' initially. Once the VM has spawned it will have the ''Power State'' of ''Running''. It may take a few minutes for your virtual machine to start, depending on a variety of factors.