Cloud Quick Start/en: Difference between revisions

Jump to navigation Jump to search
Updating to match new version of source page
(Updating to match new version of source page)
(Updating to match new version of source page)
Line 58: Line 58:
#*''Select Boot Source'': Because it's your first VM select ''Image'' as the boot source. For information about other options see our [[OpenStack#Booting_from_a_Volume|Booting From a Volume]] page.
#*''Select Boot Source'': Because it's your first VM select ''Image'' as the boot source. For information about other options see our [[OpenStack#Booting_from_a_Volume|Booting From a Volume]] page.
#*''Create New Volume'': Click ''Yes''; your VM's data will be stored in the cloud volume (or persistent storage). For more information on volume usage and management see our [[OpenStack#Working_with_Volumes|Working with Volumes]] page.
#*''Create New Volume'': Click ''Yes''; your VM's data will be stored in the cloud volume (or persistent storage). For more information on volume usage and management see our [[OpenStack#Working_with_Volumes|Working with Volumes]] page.
#**''Volume Size (GB)'': If you have a pre-planned volume size use that, otherwise 30 GB is reasonable for the operating system and some modest data needs. For more information on volume usage and management see our [[OpenStack#Working_with_Volumes|Working with Volumes]] page.
#*:''Volume Size (GB)'': If you have a pre-planned volume size use that, otherwise 30 GB is reasonable for the operating system and some modest data needs. For more information on volume usage and management see our [[OpenStack#Working_with_Volumes|Working with Volumes]] page.
#**''Delete Volume on Instance Delete'': Click ''No'' to help prevent your volume from being deleted accidentally; however, if you are confident you always want your volume deleted when your instance is deleted click ''Yes''.
#*:''Delete Volume on Instance Delete'': Click ''No'' to help prevent your volume from being deleted accidentally; however, if you are confident you always want your volume deleted when your instance is deleted click ''Yes''.
#*''Allocating an Available Image'': The list at the bottom of the window shows the '''available''' images your VM can boot. For a beginner on Linux we recommend the most recent '''Ubuntu''' image, but if you prefer one of the other Linux operating systems choose that. To select an image click the upwards pointing arrow on the far right of the row containing your desired image. That row should now show up in the '''Allocated''' list above. '''It is important for later to remember which image you chose''' (ex. ubuntu, fedora, etc.)[[File:Flavor tab.png|500px|thumb]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
#*''Allocating'' and ''Available'' lists: The list at the bottom of the window shows the available images your VM can boot. For a beginner on Linux we recommend the most recent '''Ubuntu''' image, but if you prefer you can choose any one of the other Linux operating systems. To select an image click the upwards pointing arrow on the far right of the row containing your desired image. That row should now show up in the ''Allocated'' list above. '''It is important for later to remember which image you chose''' (ex. ubuntu, fedora, etc.).[[File:Flavor tab.png|500px|thumb]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
#''Flavor''  
#''Flavor''  
#*''Allocated'' and ''Available'' lists: The flavor determines what type of hardware is used for your VM, which determines how much memory and processing capabilities it has. The ''Available'' list shows all the flavors available for your chosen boot image. Click the arrow on 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. issues no alerts), and click the upwards arrow on the far right of that row. That flavor should now show up in the ''Allocated'' list. For more details, see [[Virtual machine flavors]]. <br /><br /><br /><br /><br /><br /><br /><br />
#*''Allocated'' and ''Available'' lists: The flavor determines what type of hardware is used for your VM, which determines how much memory and processing capabilities it has. The ''Available'' list shows all the flavors available for your chosen boot image. Click the arrow on 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. issues no alerts) and click the upwards arrow on the far right of that row. That flavor should now show up in the ''Allocated'' list. For more details, see [[Virtual machine flavors]]. <br /><br /><br /><br /><br /><br /><br /><br />
#''Networks'': '''Do not change this now'''.[[File:Security groups.png|500px|thumb]]
#''Networks'': Do not change this now.[[File:Security groups.png|500px|thumb]]
#''Network Ports'':  '''Do not change this now'''. <br /><br /><br /><br /><br />
#''Network Ports'':  Do not change this now. <br /><br /><br /><br /><br />
#''Security Groups'':  The '''Default Security Group''' should be listed in the '''Allocated''' chart. If it is not, move it from the '''Available''' list to the '''Allocated''' list using the upwards arrow located on the far right of the '''Default Security Group''' row. For more information see our [[OpenStack#Security_Groups|Security Groups]] page.[[File:Key pair tab.png|500px|thumb]]<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
#''Security Groups'':  The ''Default Security Group'' should be listed in the ''Allocated'' list. If it is not, move it from ''Available'' to ''Allocated'' using the upwards arrow located on the far right of the ''Default Security Group'' row. For more information see our [[OpenStack#Security_Groups|Security Groups]] page.[[File:Key pair tab.png|500px|thumb]]<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
#''Key Pair'':  Select the  SSH key pair you created earlier from the '''Available''' list 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 see [[#SSH key pair | above]] for more instructions around Key Pairs. For more detailed information on managing and using key pairs see our [[SSH_Keys|SSH Keys]] page.<br /><br />
#''Key Pair'':  Select the  SSH key pair you created earlier from the '''Available''' list 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 see [[#SSH key pair | above]] for more instructions around Key Pairs. For more detailed information on managing and using key pairs see our [[SSH_Keys|SSH Keys]] page.<br /><br />
#''Customization Script'':  '''Do not change this now'''. For more information on using customization scripts see our [[OpenStack_VM_Setups#using_cloudinit|Cloud Init]] page.
#''Customization Script'':  '''Do not change this now'''. For more information on using customization scripts see our [[OpenStack_VM_Setups#using_cloudinit|Cloud Init]] page.
38,760

edits

Navigation menu