Cloud Quick Start: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 2: Line 2:
<translate>
<translate>
=Getting a Cloud account= <!--T:1-->
=Getting a Cloud account= <!--T:1-->
1. If you do not have a Compute Canada account, create one [https://www.computecanada.ca/research-portal/account-management/apply-for-an-account/ here].  
1. If you do not have a Compute Canada account, create one at [https://www.computecanada.ca/research-portal/account-management/apply-for-an-account/ https://www.computecanada.ca/research-portal/account-management/apply-for-an-account/].  


2. If you do not have a WestGrid account, create one by connecting to [https://ccdb.computecanada.ca/ CCDB].
2. If you do not have a WestGrid account, create one at [https://ccdb.computecanada.ca/ https://ccdb.computecanada.ca/].


:Click the ''Apply'' button next to ''WestGrid''.
:Under ''My Account'', select ''Apply for a Consortium Account'' [?other steps?] and click the ''Apply'' button next to ''WestGrid''.
:You need confirmation from WestGrid to continue.
:You need confirmation from WestGrid to continue.


3. Apply for your cloud account [https://www.computecanada.ca/create-a-cloud-account/ on this page].
3. Apply for your cloud account at [https://www.computecanada.ca/create-a-cloud-account/ https://www.computecanada.ca/create-a-cloud-account/].


=Launching your first instance (VM)= <!--T:26-->
=Launching your first instance (VM)= <!--T:26-->
==Login to the East or West Cloud==
==Login to the East or West Cloud==
[[ I think we should choose INSTANCE or VM and stick with the term instead of using both without distinction]]
[[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)]]
Depending on where your project is located, 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.
Depending on where your project is located [??], 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.
When you log in, the dashboard is displayed and you have an overview of your resources.  
When you log in, the dashboard is displayed and you have an overview of your resources.  


==SSH Key Pair== <!--T:2-->
==SSH Key Pair== <!--T:2-->
[[ should we use KEY or KEY PAIR (sometimes just PAIR) ?]]
When you start an instance, there is no password for an admin or a root account on the virtual machine. This is for security reasons, so that no one can log in with a password (you wouldn't want a hacker to be able to access the brand new VM you just started using some default password...)
When you start an instance, there is no password for an admin or a root account on the virtual machine. This is for security reasons, so that no one can log in with a password (you wouldn't want a hacker to be able to access the brand new VM you just started using some default password...)


[?this is not clear; does OS create the keyPair or does it need to be imported or do I need to create the keyPair?]
OpenStack creates your VM with one SSH public key installed; you can only log in with this SSH key pair.
OpenStack creates your VM with one SSH public key installed; you can only log in with this SSH key pair.
You can either import an existing SSH key pair through OpenStack or you can create a new pair.
You can either import an existing SSH key pair through OpenStack or you can create a new pair.
Line 53: Line 59:
*''Details'' tab
*''Details'' tab
**''Availability Zone'': There is only one zone; do not change its name.
**''Availability Zone'': There is only one zone; do not change its name.
**''Instance name'': <code>test</code><br/>Enter a name for your instance.
**''Instance name'': <code>test</code><br/>Enter a name for your instance. [[? are there naming constraints ? length, character types, etc.) ?]]
**''Flavor'': <code>c1-3.75gb-36</code><br/>The flavor defines [instance/VM] specifications. This particular flavor has one virtual CPU, 3.75GB of RAM (memory) and an ephemeral disk of 36GB. Ephemeral disks are disks created and destroyed with the instance; they reside on the local hardware running the VM.
**''Flavor'': <code>c1-3.75gb-36</code><br/>The flavor defines [instance/VM] specifications. This particular flavor has one virtual CPU, 3.75GB of RAM (memory) and an ephemeral disk of 36GB. Ephemeral disks are disks created and destroyed with the instance; they reside on the local hardware running the VM.


Line 60: Line 66:
Flavors starting with a "c" have an extra ephemeral disk attached, as well as a 20GB root disk.
Flavors starting with a "c" have an extra ephemeral disk attached, as well as a 20GB root disk.
**''Instance Count'': <code>1</code><br/>Number of VMs to create.
**''Instance Count'': <code>1</code><br/>Number of VMs to create.
**''Instance Boot Source'': Boot from image<br/> Indicates that you wish to boot from an already created image.  
**''Instance Boot Source'': Boot from image<br/> Indicates that you wish to boot from an already created image. [[??]]
**''Image Name'': <code>CentOS-7-x86-64-GenericCloud-1503</code><br/>Name of the image to boot from.
**''Image Name'': <code>CentOS-7-x86-64-GenericCloud-1503</code><br/>Name of the image to boot from.
**''Project Limits'': The green bars reflect the fraction of your available resources that will be consumed by the VM you are about to launch.
**''Project Limits'': The green bars reflect the fraction of your available resources that will be consumed by the VM you are about to launch.
Line 73: Line 79:
**''Security Groups'': Do not change <code>default</code>.
**''Security Groups'': Do not change <code>default</code>.
*''Networking tab''<br/>Do not change this now. Networking will be discussed later, after you have launched an instance.
*''Networking tab''<br/>Do not change this now. Networking will be discussed later, after you have launched an instance.
*''Post-Creation Tab''<br/>Do not change this now. This is where you would paste a '''cloud-init''' script which can do things like install and configure software and add users and additional SSH keys (see [[OpenStack#Accessing a VM with Multiple Users]]) in an automated step after the VM is created. See [http://cloudinit.readthedocs.org/en/latest/index.html# cloudinit] for more details about clout-init.
*''Post-Creation Tab''<br/>Do not change this now. This is where you would paste a '''cloud-init''' script which can do things [[?working?]]like install and configure software and add users and additional SSH keys (see [[OpenStack#Accessing a VM with Multiple Users]]) in an automated step after the VM is created. See [http://cloudinit.readthedocs.org/en/latest/index.html# cloudinit] for more details about clout-init.
*''Advanced Options'' tab<br/>Leave ''Disk Partition'' on ''Automatic'' for now.
*''Advanced Options'' tab<br/>Leave ''Disk Partition'' on ''Automatic'' for now.


Line 86: Line 92:


===Private IP=== <!--T:11-->
===Private IP=== <!--T:11-->
On the ''Instances'' list, are 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 (also referred to as a "project" on the OpenStack dashboard).
On the ''Instances''[[sing or plur?] list, are 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 (also referred to as a "project" on the OpenStack dashboard).
The ''Instances'' list shows your instance's private IP. You can use this IP to communicate with other instances running on the same cloud.
The ''Instances''[[sing or plur?] list shows your instance's private IP. You can use this IP to communicate with other instances running on the same cloud.


===Public IP (Assign a public IP)=== <!--T:12-->
===Public IP (Assign a public IP)=== <!--T:12-->
Line 106: Line 112:


<!--T:17-->
<!--T:17-->
SSH rules are predefined. Simply select SSH in the'' Rules'' dropdown menu and leave ''CIDR' under ''Remote''.
SSH rules are predefined. Simply select SSH in the'' Rules'' dropdown menu and leave ''CIDR' under ''Remote''[[?]].


<!--T:18-->
<!--T:18-->
rsnt_translations
56,430

edits