Cloud Quick Start/en: Difference between revisions

#'''Have a cloud project''' <br> If you don't already have a cloud [[OpenStack#Projects|project]] see [[Cloud#Getting_a_Cloud_project|getting a cloud project]]. '''You cannot access the Cloud without first having a cloud project.''' Once you have a cloud project associated with your account you will receive a confirmation email which will have important details you will need to access your project and get started with cloud. Make sure you have this confirmation email ready.  

#'''Have a compatible browser''' <br> The web interface for accessing your cloud project works well with both the [https://www.mozilla.org/en-US/firefox/new/ Firefox] and [https://www.google.com/chrome/ Chrome] web browsers. Other browsers may work also, however some browsers have shown the error message <code>Danger: There was an error submitting the form. Please try again.</code> which suggests that your browser is not supported by our system. This error message was noticed with certain versions of the Safari web browser on Macs, upgrading Safari may help. If you see this error message please try using a [https://www.mozilla.org/en-US/firefox/new/ Firefox] or [https://www.google.com/chrome/ Chrome] web browser. If you are still having issues email [mailto:cloud-support@computecanada.ca cloud support].

# '''Login to the Cloud interface to access your project''' <br> The confirmation email you received will include a link to the cloud interface your project is associated with. Click on the link to open it in your default web browser. If your default web browser is not compatible, open a compatible web browser and copy and paste the link address into the browser. If you know the name of your associated cloud, but don't have the login URL see [[Cloud#Using_the_Cloud|using the cloud]] for the list of cloud interface URLs at which you can login. Use your Compute Canada username (not your email address) and password to login.

#'''Checkout your OpenStack dashboard''' <br> After logging in to the Cloud interface (the platform is called ''OpenStack'') you will see a dashboard that shows an overview of all the resources available in your project. If you want to know more about navigating and understanding your OpenStack dashboard check out the official [https://www.google.com/url?q=https://docs.openstack.org/horizon/latest/user/index.html&sa=D&ust=1590163536427000&usg=AFQjCNGLQWBiQHOmlw0CEF5uTdGDnOKuLg OpenStack documentation].

Below there are instructions starting a Windows VM or a Linux VM, depending on which tab you select. '''Remember this is the operating system for the virtual machine or 'instance' you are creating, not the operating system of the physical computer you are using to connect'''. It should be clear from your project pre-planning whether you will be using Linux or Windows for your VM operating system, but if you are unsure please email [mailto:cloud-support@computecanada.ca cloud support].

When you create a virtual machine (also referred to as an ''instance'' or a ''VM''), password authentication is disabled for security reasons.

 

Instead OpenStack creates your VM with one SSH (secure shell) public key installed, and you can only log in using this SSH key pair. If you have used SSH keys before, the SSH public key can come from a key pair which you have already created on some other machine. In this case follow the instructions below for '''Importing an existing key pair'''. If you have not used SSH key pairs before, or don't currently have a pair you want to use, OpenStack can create a pair for you. In this case follow the instructions below for '''Creating a new key pair'''. For more information on creating and managing your key pairs see the [[SSH Keys/en|SSH Keys page]] in our wiki.

#Give your key pair a name so you can recognize the file when it saves to your computer, you can only use letters,numbers, spaces and dashes, no other special characters are permitted.

#The key pair file will download to your default download folder on your pc. It will have a .pem file extension on it. Make sure to save the file to your dekstop (or another easy access folder on your hard drive).

 

To create a virtual machine, click on the ''Instances'' menu item on the left, then click on [[File:Launch-Instance-Button.png]] [[File:Details tab.png|500px|thumb]]

After clicking '''Launch Instance''', you will be presented with a series of options:

#*''Instance Name'': Enter a name for your virtual machine. Do not include spaces or special characters in your instance name. For more details around naming rules see our restrictions on valid host names wiki page.

#*''Create New Volume'': Click '''Yes'''. This means 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.

#*''Delete Volume on Instance Delete''': Click '''No'''. This can help prevent your volume from being deleted accidentally, but 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 an Available Flavor'': 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 (has 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 />

#''Security Groups Tab '':  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 />

#''Key Pair Tab'':  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.

#Once you have reviewed all the tabs and defined your virtual machine, click on the '''Launch''' button and your virtual machine will be created. 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 show the '''Running''' state.

==Network Settings==

On the ''Instances'' page is a list VMs with their IP address(es) displayed in the ''IP Address'' column. Each VM will have at least one private IP address, but some may also have a second public IP assigned to it.When your OpenStack project is created a local network is also created for you. This local network is used to connect VMs to each other and to an internet gateway within that project, allowing them to communicate with each other and the outside world. Their private IP address does not allow the outside world to reference that VM. Any VM created in your project will have a private IP address assigned to it from this network of the form <code>192.168.X.Y</code>. Public IPs allow outside services and tools to initiate contact with your VM, such as allowing you to connect to it to perform administrative tasks or serve up web content. Public IPs can also be pointed to by domain names.

#''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 on the left hand side and go to '''Compute -> Instances'''.

#*Click the drop down arrow menu on the far right of the row for your VM and select ''Associate Floating IP'' from the drop-down menu button (indicated by &#x25BC;).

#*If this is your first time associating a floating IP, you need to click on the “+” sign in the ''IP Address'' 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 &#x25BC; in the '''IP Address''' dialogue box.

#*Click on the ''Associate'' button.

#*You should now have two IP address in your IP address column. One will be of the form <code>192.168.X.Y</code>, the other one is your public IP. You can also find a list of your public IP addresses and their associated projects by going to '''Network->Floating IPs. You will need your public IP when you are trying to connect to your VM.'''

#*Using the left navigation pane go to '''Network->Security Groups'''.

#*On the group row named '''default''', click the [[File:Manage-Rules-Button.png]] on the far right.

#*On the next screen, click [[File:Add-Rule-Button.png]] near the top right corner.

#*In the ''' Rules''' drop-down menu select '''SSH'''

#* 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.

#*Finally, click the ''Add'' button. Now the rule you just created should show up on the list in 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]]).

#*It can be helpful to add a description about what a security rule is for, e.g. home or office. That way you will know which rule is no longer needed if you need to add a new rule while connecting, for example, from home.

In the first step of this quick guide you saved a private key to your computer, make sure you remember where you saved it, 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==

{{Command| ssh -i /path/where/your/private/key/is/my_key.key <user name>@<public IP of your server>}}

where <code><user name></code> is the name of the user connecting and <code><public IP of your VM></code> is the public IP you associated with your VM in the [[#Public IP | previous step]]. The default user name depends on the image.

These default users have full sudo privileges. Connecting directly to the root account via SSH is disabled.

 

 

 

<tab name="Windows">