38,760
edits
Cloud Quick Start/en: Difference between revisions
Updating to match new version of source page
(Updating to match new version of source page) Tags: Mobile edit Mobile web edit |
(Updating to match new version of source page) Tags: Mobile edit Mobile web edit |
||
| Line 61: | Line 61: | ||
#*:''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''. | ||
#*''Allocated'' 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. | #*''Allocated'' 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. 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 /> | #*''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. 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 95: | Line 95: | ||
#Important notes | #Important notes | ||
#*'''Do not remove the default security rules''' as this will affect the ability of your VM to function properly (see [[OpenStack#Security_Groups|Security Groups]]). | #*'''Do not remove the default security rules''' as this will affect the ability of your VM to function properly (see [[OpenStack#Security_Groups|Security Groups]]). | ||
#*'''Security rules cannot be edited''', they can only be deleted and re-added. | #*'''Security rules cannot be edited''', 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-campus vs working from home) you are changing your network location. | #*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. | ||
#*If you do not have a static IP address for the network you are using, remember that it can sometimes change, so if you can no longer connect to your VM after a period of time sometimes it's worth checking to see if your IP address has changed. You can do this by putting [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser and seeing if it matches what you have in your security rule. If your IP address changes frequently, but the left-most numbers always stay the same, it could make more sense to add a range of IP addresses rather than frequently modifying your security rules. Use [https://www.ipaddressguide.com/cidr this tool] for determining a CIDR IP range from an IP range or learn more about CIDR notation [https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation here]. | #*If you do not have a static IP address for the network you are using, remember that it can sometimes change, so if you can no longer connect to your VM after a period of time sometimes it's worth checking to see if your IP address has changed. You can do this by putting [http://ipv4.icanhazip.com ipv4.icanhazip.com] in your browser and seeing if it matches what you have in your security rule. If your IP address changes frequently, but the left-most numbers always stay the same, it could make more sense to add a range of IP addresses rather than frequently modifying your security rules. Use [https://www.ipaddressguide.com/cidr this tool] for determining a CIDR IP range from an IP range or learn more about CIDR notation [https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation here]. | ||
| Line 101: | Line 101: | ||
==Connecting to your VM with SSH== | ==Connecting to your VM with SSH== | ||
In the first step of this quick guide you saved a private key to your computer | In the first step of this quick guide you saved a private key to your computer. Make sure you remember where you saved it because you will need it to connect to your VM. You will also need to remember which type of image you used (Ubuntu, Fedora, etc.) and which public IP address is associated with your VM. | ||
==Connecting from a Linux or Mac machine== | ==Connecting from a Linux or Mac machine== | ||
If the computer you are using to connect to your VM has a Linux or Mac operating system, use the following instructions to connect to your VM. Otherwise skip down to the next section to connect with a Windows computer. | If the computer you are using to connect to your VM has a Linux or Mac operating system, use the following instructions to connect to your VM. Otherwise skip down to the next section to connect with a Windows computer.</br></br> | ||
Open a terminal and input the following command: | Open a terminal and input the following command: | ||
{{Command| ssh -i /path/where/your/private/key/is/my_key.key <user name>@<public IP of your server>}} | {{Command| ssh -i /path/where/your/private/key/is/my_key.key <user name>@<public IP of your server>}} | ||
| Line 128: | Line 128: | ||
==Connecting from a Windows machine== | ==Connecting from a Windows machine== | ||
[[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 '''MobaXTerm''', and will show the instructions for connecting with MobaXTerm below. If you want to | 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 '''MobaXTerm''', and will show the instructions for connecting with MobaXTerm below. If you want to connect using PuTTY instead, see [[Connecting with PuTTY]]. | ||
[[File:MobaXterm ssh key.png|400px|thumb| Specifying a private key (Click for larger image)]] | [[File:MobaXterm ssh key.png|400px|thumb| Specifying a private key (Click for larger image)]] | ||
To download MobaXterm [http://mobaxterm.mobatek.net/ | To download MobaXterm [http://mobaxterm.mobatek.net/ click here]. | ||
To connect to your VM using MobaXterm follow these instructions: | To connect to your VM using MobaXterm follow these instructions: | ||
#Open the MobaXterm application | #Open the MobaXterm application. | ||
#Click | #Click on ''Sessions'' then press ''New session''. </br></br></br></br> | ||
#Select an | #Select an SSH session. | ||
#Enter the public IP address for your VM in the | #Enter the public IP address for your VM in the ''Remote host'' address field. | ||
#Ensure that the | #Ensure that the ''Specify username'' checkbox is checked, then enter the image type for your VM (ubuntu for example) into the username field, all lowercase. | ||
#Click the | #Click on the ''Advanced SSH settings'' tab, and check the ''Use private key'' checkbox. | ||
#Click the page icon in the far right of the | #Click on the page icon in the far right of the ''Use private key'' field box. In the pop up dialogue box select the key pair (.pem file) that you saved to your computer at the beginning of this quick guide. | ||
#Then click | #Then click on OK. MobaXterm will then save that session information you just entered for future connections, and also open an SSH connection to your VM. It also opens an SFTP connection which allows you to transfer files to and from your VM using drag-and-drop via the left hand panel. | ||
[[File:MobaXterm connected.png|400px|border| Connected to a remote host (Click for larger image)]] | [[File:MobaXterm connected.png|400px|border| Connected to a remote host (Click for larger image)]] | ||
=Important | =Important notes= | ||
=Where to go from here= | =Where to go from here= | ||
* | * Learn about using the [[Linux_introduction|Linux command line]] in your VM | ||
* | * Learn about [[security considerations when running a VM]] | ||
* [[Configuring a data or web server]] | * See [[Configuring a data or web server]] | ||
* | * Use an [[OpenStack VM Setups|available pre-made cloud configuration]] | ||
* | * Learn more about working with [[OpenStack]] | ||
* [[ | * [[Automating VM creation]] | ||
* [[ | * [[Backing up your VM]] | ||
* Compute Canada [[technical support]] | * Compute Canada [[technical support]] | ||
</tab> | </tab> | ||