Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Cloud Quick Start: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
=Launching your first instance (VM)= | =Launching your first instance (VM)= | ||
==Login to the East or West Cloud== | ==Login to the East or West Cloud== | ||
[[File:OpenStack-Dashboard-Compute-Overview.png|400px|thumb| OpenStack Dashboard, Compute Overview (Click for larger image)]] | [[File:OpenStack-Dashboard-Compute-Overview.png|400px|thumb| OpenStack Dashboard, Compute Overview (Click for larger image)]] | ||
Go to [https://east.cloud.computecanada.ca https://east.cloud.computecanada.ca] or [https://west.cloud.computecanada.ca https://west.cloud.computecanada.ca] and enter your WestGrid credentials. After you have logged in, you are presented with the dashboard. From here you can see an overview of the resources you are using. | |||
==SSH Key Pair== | ==SSH Key Pair== | ||
When | When you start a virtual machine (or "instance") there is no password for admin or root account on the VM, and no one can log in to it using a password. We do this for security reasons: You would not want a hacker to be able to access the brand new VM you just started using some default password. Therefore OpenStack will create your VM with one SSH public key installed, and you can only log in to it with that SSH key pair. You can either import an existing SSH key pair through OpenStack, or you can create a new pair. | ||
In order to manage your | In order to manage your key pair, click on “Access & Security” from the left menu, then on the “Key Pairs” tab. | ||
===Importing an Existing Key Pair=== | ===Importing an Existing Key Pair=== | ||
[[File:Import-Key-Pair-Form.png|400px|thumb| Import key pair (Click for larger image)]] | |||
#Click [[File:Import-Key-Pair-Button.png]] | #Click [[File:Import-Key-Pair-Button.png]] | ||
#Then, | #Then, | ||
| Line 15: | Line 15: | ||
##Paste your public key. | ##Paste your public key. | ||
##Click on the blue Import Key Pair button. | ##Click on the blue Import Key Pair button. | ||
===Creating a New Key Pair=== | ===Creating a New Key Pair=== | ||
[[File:Create-Key-Pair-Form.png|400px|thumb| Create key pair (Click for larger image)]] | |||
#Click [[File:Create-Key-Pair-Button.png]] | #Click [[File:Create-Key-Pair-Button.png]] | ||
#Then, | #Then, | ||
| Line 25: | Line 24: | ||
##Save the <key name>.pem on your disk. | ##Save the <key name>.pem on your disk. | ||
On UNIX hosts, you will need to <code>chmod 400 <key name>.pem</code> in order to connect later on | On UNIX hosts, you will need to <code>chmod 400 <key name>.pem</code> in order to connect later on. This needs to be done on your machine, not the VM. | ||
==Launching a VM== | ==Launching a VM== | ||
To launch an | [[File:Launch-Instance-Form.png|400px|thumb| Launch Instance (Click for larger image)]] | ||
To launch an instance, click on the Instances menu on the left, then click [[File:Launch-Instance-Button.png]] | |||
You are now presented with a form to define your | You are now presented with a form to define your instance. For this walk-through, fill in the arbitrary values described below. | ||
*Details | *Details tab | ||
**Instance name: <code>test</code><br/> | **Availability Zone: There is only one zone. Leave it unchanged. | ||
**Flavor: <code>c1-3.75gb-36</code><br/>The flavor name defines the | **Instance name: <code>test</code><br/>Make up a name for your instance. | ||
**Instance Count : <code>1</code><br/>Instance Boot Source: Boot from image | **Flavor: <code>c1-3.75gb-36</code><br/>The flavor name defines the specifications of the VM. This particular flavor has one virtual CPU, 3.75 GB of RAM (memory) and an ephemeral disk of 36GB. | ||
**Instance Count: <code>1</code><br/>Instance Boot Source: Boot from image | |||
**Image Name: <code>CentOS-7-x86-64-GenericCloud-1503</code> | **Image Name: <code>CentOS-7-x86-64-GenericCloud-1503</code> | ||
*Access & Security | **Project Limits: The green bars reflect the fraction of your available resources that will be consumed by the VM you are about to launch. | ||
*Networking | *Access & Security tab<br/> | ||
*Post-Creation Tab<br/> | **Key Pair: Select your SSH key pair. If you have only one, it will be selected by default. | ||
**Security Groups: Leave <code>default</code> selected here. | |||
*Networking tab<br/>You do not need to change this now. Networking will be discussed below after you have launched in instance. | |||
*Post-Creation Tab<br/>No need to change this now. This is where you can paste a '''cloud-init''' script which can do things like install and configure software, add users, and add additional SSH keys, in an automated step after the VM is created. See [http://cloudinit.readthedocs.org/en/latest/index.html# cloudinit] for more details. | |||
*Advanced Options tab<br/>Leave Disk Partition on "Automatic" for now. | |||
Once you have reviewed all the tabs and defined your instance, click on the blue Launch button and your instance will be created. The Instances list will appear, and the Status field will change, reflecting the different tasks that have to happen until it is running. It may take a few minutes for your instance to start, depending on a variety of factors. | |||
Note: When creating a persistent service, we recommend that you boot your instance from a volume. | Note: When creating a persistent service, we recommend that you boot your instance from a volume. See [[Persistent Services In The Cloud]]. | ||
==Network== | ==Network== | ||
===Private IP=== | ===Private IP=== | ||
On the Instance list, you will see the IP addresses to which your | On the Instance list, you will see the IP addresses to which your instance is linked. By default a network on <code>192.168.X.0</code> is created for your tenant. You can see the private IP your instance has on the Instance list screen. You can use this IP to communicate with other instances you have started on the same cloud. | ||
===Public IP (Assign a public IP)=== | ===Public IP (Assign a public IP)=== | ||
To assign a public IP, you need to select “Associate Floating IP” from the More button of the Actions column. | To assign a public IP, you need to select “Associate Floating IP” from the More button of the Actions column. If this is your first time through this Quick Start Guide, your tenant is new and hasn’t used an IP address yet. You need to click on the “+” sign to allocate an IP (since there is only one pool of public address, it should be already selected). Then click on the blue Allocate IP button. The public IP will appear on the IP Address field, and the port to which it should be nated should | ||
already be selected. Simply click on the blue Associate button. | already be selected. Simply click on the blue Associate button. | ||