rsnt_translations
57,772
edits
Cloud Quick Start: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 69: | Line 69: | ||
#*:<i>Volume Size (GB):</i> 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 [[Working_with_volumes|Working with volumes]]. | #*:<i>Volume Size (GB):</i> 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 [[Working_with_volumes|Working with volumes]]. | ||
#*:<i>Delete Volume on Instance Delete:</i> Click on <i>No</i> 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 on <i>Yes</i>. | #*:<i>Delete Volume on Instance Delete:</i> Click on <i>No</i> 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 on <i>Yes</i>. | ||
#*<i>Allocated</i> and <i>Available</i> 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 | #*<i>Allocated</i> and <i>Available</i> 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 <b>Ubuntu</b> 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 <i>Allocated</i> list above. <b>It is important for later to remember which image you chose</b> (ex. Ubuntu, Fedora, etc.).[[File:Flavor tab.png|500px|thumb]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /> | ||
#<i>Flavor</i> | #<i>Flavor</i> | ||
#*<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 ''Allocated'' list. For more details, see [[Virtual machine flavors]]. <br /><br /><br /><br /><br /><br /><br /><br /> | #*<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 ''Allocated'' list. For more details, see [[Virtual machine flavors]]. <br /><br /><br /><br /><br /><br /><br /><br /> | ||
| Line 102: | Line 102: | ||
#*Finally, click on the ''Add'' button. Now the rule you just created should show up on the list in security groups. | #*Finally, click on the ''Add'' button. Now the rule you just created should show up on the list in security groups. | ||
#Important notes | #Important notes | ||
#* | #*<b>Do not remove the default security rules</b> as this will affect the ability of your VM to function properly (see [[Managing_your_cloud_resources_with_OpenStack#Security_Groups|Security Groups]]). | ||
#* | #*<b>Security rules cannot be edited</b>, they can only be deleted and re-added. If you make a mistake when creating a security group rule, you need to delete it using the ''Delete Rule'' button on the far left of the row for that rule in the security groups screen, and then re-add it correctly from scratch using the ''+Add Rule'' button. | ||
#*If you change your network location (and therefore your IP address) then you need to add the security rule described in this section for that new IP address. Remember that when you change your physical location (example working on | #*If you change your network location (and therefore your IP address) then you need to add the security rule described in this section for that new IP address. Remember that when you change your physical location (example working on | ||
campus vs working from home) you are changing your network location. | campus vs working from home) you are changing your network location. | ||
| Line 143: | Line 143: | ||
==Connecting from a Windows machine== <!--T:22--> | ==Connecting from a Windows machine== <!--T:22--> | ||
[[File:MobaXterm basic.png|400px|thumb| Creating an SSH session (Click for larger image)]] | [[File:MobaXterm basic.png|400px|thumb| Creating an SSH session (Click for larger image)]] | ||
If you want to use a Windows computer to connect to your VM, you will need to have an interface application to handle the SSH connection. We recommend | If you want to use a Windows computer to connect to your VM, you will need to have an interface application to handle the SSH connection. We recommend <b>MobaXTerm</b<, and will show the instructions for connecting with MobaXTerm below. If you want to connect using PuTTY instead, see [[Connecting with PuTTY]]. | ||
<!--T:1--> | <!--T:1--> | ||