rsnt_translations
56,430
edits
Cloud Quick Start: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 68: | Line 68: | ||
#*:''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 [[OpenStack#Working_with_Volumes|Working with Volumes]]. | #*:''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 [[OpenStack#Working_with_Volumes|Working with Volumes]]. | ||
#*:''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'' 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 /> | #*''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 on 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 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. 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 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. issues no alerts) and click on 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 /> | ||
| Line 89: | Line 89: | ||
#Assign a Public IP Address | #Assign a Public IP Address | ||
#*Ensure you are still viewing the instances list where you were redirected as your VM launched. If you need to use the navigation panel, select options ''Compute->Instances'' on the OpenStack menu. | #*Ensure you are still viewing the instances list where you were redirected as your VM launched. If you need to use the navigation panel, select options ''Compute->Instances'' on the OpenStack menu. | ||
#*Click the drop-down arrow menu (indicated by ▼) on the far right of the row for your VM and select ''Associate Floating IP''. | #*Click on the drop-down arrow menu (indicated by ▼) on the far right of the row for your VM and select ''Associate Floating IP''. | ||
#*If this is your first time associating a floating IP, you need to click on the “+” sign in the ''Manage Floating IP Associations'' dialog box. If you need to allocate a public IP address for this VM again in the future, you can select one from the list by clicking the ▼ in the ''IP Address'' field. | #*If this is your first time associating a floating IP, you need to click on the “+” sign in the ''Manage Floating IP Associations'' dialog box. If you need to allocate a public IP address for this VM again in the future, you can select one from the list by clicking the ▼ in the ''IP Address'' field. | ||
#*Click on the ''Associate'' button. | #*Click on the ''Associate'' button. | ||
| Line 95: | Line 95: | ||
#''Configure the firewall'' | #''Configure the firewall'' | ||
#*On the OpenStack left menu, select ''Network->Security Groups''. | #*On the OpenStack left menu, select ''Network->Security Groups''. | ||
#*On the group row named ''default'', click the ''Manage Rules'' button on the far right. | #*On the group row named ''default'', click on the ''Manage Rules'' button on the far right. | ||
#*On the next screen, click on the ''+Add Rule'' button near the top right corner. | #*On the next screen, click on the ''+Add Rule'' button near the top right corner. | ||
#*In the ''Rule'' drop-down menu select | #*In the ''Rule'' drop-down menu select ''SSH''. | ||
#* The ''Remote'' Text box should automatically have ''CIDR'' in it, '''Do not change this.''' | #* The ''Remote'' Text box should automatically have ''CIDR'' in it, '''Do not change this.''' | ||
#*In the ''CIDR'' dialogue box replace the <code>0.0.0.0/0</code> in the CIDR text box with <code>your-ip/32</code>. Note that this is the IP address of the physical computer you are wanting to use to connect to your VM. If you don't know your current IP address you can see it by going to [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser. If you want to access your VM from other IPs you can add more rules with different IP addresses. If you want to specify a range of IP addresses use [https://www.ipaddressguide.com/cidr this tool] to calculate your CIDR rule for a range of IP addresses. | #*In the ''CIDR'' dialogue box replace the <code>0.0.0.0/0</code> in the CIDR text box with <code>your-ip/32</code>. Note that this is the IP address of the physical computer you are wanting to use to connect to your VM. If you don't know your current IP address you can see it by going to [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser. If you want to access your VM from other IPs you can add more rules with different IP addresses. If you want to specify a range of IP addresses use [https://www.ipaddressguide.com/cidr this tool] to calculate your CIDR rule for a range of IP addresses. | ||