Cloud Quick Start: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
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==
Simply go to [https://east.cloud.computecanada.ca https://east.cloud.computecanada.ca] or [https://west.cloud.computecanada.ca https://west.cloud.computecanada.ca], depending on which cloud you want to launch your instances, and enter your WestGrid credentials. After you have successfully logged in, you are presented with the dashboard. From here you can see an overview of the resources you are using. When your tenant (project) is created, most of the configuration is done at the same time.
[[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 starting an instance, there is no password for admin or root account on your server. You can only authenticate to your server with an SSH key. You can either import your SSH key in OpenStack, or you can create a new one.
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 Key Pair, click on “Access & Security” from the left menu, then on the “Key Pairs” tab.
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.
See Import Key Pair
[[File:Import-Key-Pair-Form.png|400px|thumb| Import key pair (Click for larger image)]]


===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 (This need to be done on your machine, not the VM).
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.
 
[[File:Create-Key-Pair-Form.png|400px|thumb| Create key pair (Click for larger image)]]


==Launching a VM==
==Launching a VM==
To launch an Instance, simply click on Instances menu on the left, then click [[File:Launch-Instance-Button.png]]
[[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 Instance.
You are now presented with a form to define your instance. For this walk-through, fill in the arbitrary values described below.
*Details Tab
*Details tab
**Instance name: <code>test</code><br/>This is the name of your instance.
**Availability Zone: There is only one zone.  Leave it unchanged.
**Flavor: <code>c1-3.75gb-36</code><br/>The flavor name defines the specs of the VM. This particular flavor has 1 vcpu,3.75 GB of ram and an Ephemeral disk of 36GB,
**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 Tab<br/>This is where you select your SSH Key Pair. If you have only one, it will be selected by default. You can also select which security group to add to your instance.
**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 Tab<br/>Select which network to connect to. You do not need to change this now. Networking will be discussed below after you have Launched in instance.
*Access & Security tab<br/>
*Post-Creation Tab<br/>This allows you to add a configuration script. This is where you can paste a cloud-init script ( see [http://cloudinit.readthedocs.org/en/latest/index.html# cloudinit] for more details), which can do things like install and configure software, add users, and additional ssh keys in an automated step after the VM is created.
**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.
Once you have defined your Instance, click on the blue Launch button and your Instance will be created. The Instance you just defined is going to appear in the Instance list. It will proceed through different tasks and then start, depending on a variety of factors, it can take up to a few minutes for your instance to start. You will see some information on your instance.
*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.


[[File:Launch-Instance-Form.png|400px|thumb| Launch Instance (Click for larger image)]]
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 Instance are 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 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. Since 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
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.



Revision as of 18:49, 29 February 2016

Launching your first instance (VM)

Login to the East or West Cloud

OpenStack Dashboard, Compute Overview (Click for larger image)

Go to https://east.cloud.computecanada.ca or 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

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 key pair, click on “Access & Security” from the left menu, then on the “Key Pairs” tab.

Importing an Existing Key Pair

Import key pair (Click for larger image)
  1. Click Import-Key-Pair-Button.png
  2. Then,
    1. Give a name to your key.
    2. Paste your public key.
    3. Click on the blue Import Key Pair button.

Creating a New Key Pair

Create key pair (Click for larger image)
  1. Click Create-Key-Pair-Button.png
  2. Then,
    1. Give your key a name.
    2. Click on the blue Create Key Pair button.
    3. Save the <key name>.pem on your disk.

On UNIX hosts, you will need to chmod 400 <key name>.pem in order to connect later on. This needs to be done on your machine, not the VM.

Launching a VM

Launch Instance (Click for larger image)

To launch an instance, click on the Instances menu on the left, then click Launch-Instance-Button.png

You are now presented with a form to define your instance. For this walk-through, fill in the arbitrary values described below.

  • Details tab
    • Availability Zone: There is only one zone. Leave it unchanged.
    • Instance name: test
      Make up a name for your instance.
    • Flavor: c1-3.75gb-36
      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: 1
      Instance Boot Source: Boot from image
    • Image Name: CentOS-7-x86-64-GenericCloud-1503
    • Project Limits: The green bars reflect the fraction of your available resources that will be consumed by the VM you are about to launch.
  • Access & Security tab
    • Key Pair: Select your SSH key pair. If you have only one, it will be selected by default.
    • Security Groups: Leave default selected here.
  • Networking tab
    You do not need to change this now. Networking will be discussed below after you have launched in instance.
  • Post-Creation Tab
    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 cloudinit for more details.
  • Advanced Options tab
    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. See Persistent Services In The Cloud.

Network

Private IP

On the Instance list, you will see the IP addresses to which your instance is linked. By default a network on 192.168.X.0 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)

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.

Manage Floating IP (Click for larger image)

Note that the public IP is NATted (Network Adress Translation) to the private IP of your instance.

Firewall, Add Rules to Allow SSH

In order to be able to connect to your instance via SSH, you will need to allow SSH to get through.

Go to “Access & Security”, in the “Security Groups” tab, then on the default row click Manage-Rules-Button.png

On the next screen, click Add-Rule-Button.png

For SSH, there are already predefined rules. Simply select SSH in the Rules drop down menu, then under Remote, keep CIDR.

If you know which address you are connecting from, type it in the CIDR text field; otherwise keep 0.0.0.0/0. This will allow the whole world to connect to your server via SSH.

Finally, click the blue Add button.

Add Rule (Click for larger image)

Connecting To Your Instance With SSH.

If you created a key pair on the first step, you will need to know where it is.

If connecting from a Linux machine:

ssh -i /path/where/your/key/is/my_key.key username@<public IP of your server>

Most common Linux distributions have standardized on the name of the distro as the username. To connect to the provided CentOS images, you would use:

ssh -i /path/where/your/key/is/my_key.key centos@<public IP of your server>

Ubuntu instances have the username “ubuntu”; Debian ones are “debian”. By default the preconfigured cloud username will have full sudo privileges. The root account is normally disabled.

You are now connected to your instance.

If connecting from a windows machine

see Connecting with PuTTY or Connecting with MobaXTerm

Where To Go From Here