Cloud Quick Start/en: Difference between revisions

Jump to navigation Jump to search

Cloud Quick Start/en (view source)

Revision as of 20:45, 19 June 2023

82 bytes added ,  1 year ago
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)
Line 75: Line 75:
On the <i>Instances</i> page is a list of VMs with their IP address(es) displayed in the <i>IP Address</i> 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. The private IP address provides inter VM networking but does not allow for connection to the outside world. 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 your VM via your personal computer to perform administrative tasks or serve up web content. Public IPs can also be pointed to by domain names.
On the <i>Instances</i> page is a list of VMs with their IP address(es) displayed in the <i>IP Address</i> 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. The private IP address provides inter VM networking but does not allow for connection to the outside world. 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 your VM via your personal computer to perform administrative tasks or serve up web content. Public IPs can also be pointed to by domain names.


#Assign a Public IP Address
#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, select options ''Compute->Instances'' on the OpenStack menu.
#*Ensure you are still viewing the instances list where you were redirected as your VM launched. If you need to use the navigation panel, select options <i>Compute->Instances</i> on the OpenStack menu.
#*Click on the drop-down arrow menu (indicated by &#x25BC;) on the far right of the row for your VM and select ''Associate Floating IP'', then in the ''Allocate Floating IP'' window, click on the ''Allocate IP'' button. If this is your first time associating a floating IP, you need to click on the “+” sign in the ''Manage Floating IP Associations'' 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'' field.
#*Click on the drop-down arrow menu (indicated by &#x25BC;) on the far right of the row for your VM and select <i>Associate Floating IP</i>, then in the <i>Allocate Floating IP</i> window, click on the <i>Allocate IP</i> button. If this is your first time associating a floating IP, you need to click on the “+” sign in the <i>Manage Floating IP Associations</i> 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 <i>IP Address</i> field.
#*Click on the ''Associate'' button.
#*Click on the <i>Associate</i> button.
#*You should now have two IP addresses in your IP address column. One will be of the form <code>192.168.X.Y</code>, the other 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.
#*You should now have two IP addresses in your IP address column. One will be of the form <code>192.168.X.Y</code>, the other is your public IP. You can also find a list of your public IP addresses and their associated projects by going to <i>Network->Floating IPs</i>. You will need your public IP when you are trying to connect to your VM.
#Configure the firewall
#Configure the firewall
#*On the OpenStack left menu, select ''Network->Security Groups''.
#*On the OpenStack left menu, select <i>Network->Security Groups</i>.
#*On the group row named ''default'', click on the ''Manage Rules'' button on the far right.
#*On the group row named <i>default</i>, click on the </i>Manage Rules</i> button on the far right.
#*On the next screen, click on the ''+Add Rule'' button near the top right corner.
#*On the next screen, click on the <i>+Add Rule</i> button near the top right corner.
#*In the ''Rule'' drop-down menu, select ''SSH''.
#*In the <i>Rule</i> drop-down menu, select <i>SSH</i>.
#* The ''Remote'' text box should automatically have ''CIDR'' in it; do not change this.
#* The <i>Remote</i> text box should automatically have <i>CIDR</i> in it; do not change this.
#*In the ''CIDR'' text box, replace <code>0.0.0.0/0</code> 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.
#*In the <i>CIDR</i> text box, replace <code>0.0.0.0/0</code> 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 on the ''Add'' button. Now the rule you just created should show up on the list in security groups.
#*Finally, click on the <i>Add</i> button. Now the rule you just created should show up on the list in security groups.
#Important notes
#Important notes
#*<b>Do not remove the default security rules</b> as this will affect the ability of your VM to function properly (see [[Managing_your_cloud_resources_with_OpenStack#Security_Groups|Security Groups]]).
#*<b>Do not remove the default security rules</b> as this will affect the ability of your VM to function properly (see [[Managing_your_cloud_resources_with_OpenStack#Security_Groups|Security Groups]]).
#*<b>Security rules cannot be edited</b>, 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.
#*<b>Security rules cannot be edited</b>, 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 <i>Delete Rule</i> 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 <i>+Add Rule</i> 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 135: Line 135:
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 on ''Sessions'' then press ''New session''. </br></br></br></br>
#Click on <i>Sessions</i> then press <i>New session</i>. </br></br></br></br>
#Select an SSH session.
#Select an SSH session.
#Enter the public IP address for your VM in the ''Remote host'' address field.
#Enter the public IP address for your VM in the <i>Remote host</i> address field.
#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.
#Ensure that the <i>Specify username</i> checkbox is checked, then enter the image type for your VM (ubuntu for example) into the username field, all lowercase.
#Click on the ''Advanced SSH settings'' tab, and check the ''Use private key'' checkbox.
#Click on the <i>Advanced SSH settings</i> tab, and check the <i>Use private key</i> checkbox.
#Click on the page icon in the far right of the ''Use private key'' field. 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.   
#Click on the page icon in the far right of the <i>Use private key</i> field. 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 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.
#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|thumb| Connected to a remote host (Click for larger image)]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
[[File:MobaXterm connected.png|400px|thumb| Connected to a remote host (Click for larger image)]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
FuzzyBot
Bots
38,760

edits

Retrieved from "https://docs.alliancecan.ca/wiki/Special:MobileDiff/139002"

Navigation menu