cloud:intro
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| cloud:intro [2019/12/09 08:04] – chudler | cloud:intro [2020/01/17 12:04] – kauffman | ||
|---|---|---|---|
| Line 82: | Line 82: | ||
| Use your favorite package manager on your own computer. Pip is preferred because the upstream packages it for themselves and it is in pure python. The general CS infrastructure will become a managed client for you to use in the near future (e.g., linux.cs.uchicago.edu). However, our experience has been that the software installs cleanly and is free from dependency problems. | Use your favorite package manager on your own computer. Pip is preferred because the upstream packages it for themselves and it is in pure python. The general CS infrastructure will become a managed client for you to use in the near future (e.g., linux.cs.uchicago.edu). However, our experience has been that the software installs cleanly and is free from dependency problems. | ||
| - | Try: < | + | Try: < |
| == PRELIMINARY SETUP == | == PRELIMINARY SETUP == | ||
| Line 146: | Line 146: | ||
| You are free to use the Network called __cloud__, if you don't need your hosts to be L2 isolated from other people, and you would like to proceed directly to creating servers. | You are free to use the Network called __cloud__, if you don't need your hosts to be L2 isolated from other people, and you would like to proceed directly to creating servers. | ||
| Using the __cloud__ network cuts down your complexity significantly, | Using the __cloud__ network cuts down your complexity significantly, | ||
| - | < | + | |
| + | < | ||
| + | openstack network list | ||
| + | </ | ||
| [EDITOR NOTE: This section should be isolated from the main body] | [EDITOR NOTE: This section should be isolated from the main body] | ||
| Line 153: | Line 156: | ||
| Should you want to create a network of your own that your hosts will be on, not all of these options are necessary | Should you want to create a network of your own that your hosts will be on, not all of these options are necessary | ||
| - | < | + | < |
| + | openstack network create mynet \ | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| Now create a subnet for your network. This is mandatory for launching instances in the network that you just created. | Now create a subnet for your network. This is mandatory for launching instances in the network that you just created. | ||
| Line 163: | Line 171: | ||
| You are now advised that there is no " | You are now advised that there is no " | ||
| - | < | + | < |
| + | openstack subnet create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| After creating your own network and subnet(s), a router is also needed. However, a router is **not** needed if your instances only talk to each other. The router will take the gateway of your subnet automatically, | After creating your own network and subnet(s), a router is also needed. However, a router is **not** needed if your instances only talk to each other. The router will take the gateway of your subnet automatically, | ||
| - | < | ||
| - | openstack router add subnet mysubnet</ | ||
| - | With the router created and attached to your subnet, develop it further. First, you need to obtain a free IP address on the UC Campus. We call this network __campus37__. | ||
| - | < | ||
| - | The output of the command is shown below. Take note of the IP Address: | ||
| < | < | ||
| - | +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | + | openstack router create |
| - | | Field | Value | | + | </ |
| - | +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | + | < |
| - | | created_at | + | openstack router add subnet myrouter mysubnet |
| - | | description | + | </ |
| - | | dns_domain | + | |
| - | | dns_name | + | |
| - | | fixed_ip_address | + | |
| - | | floating_ip_address | 128.135.37.244 | + | |
| - | | floating_network_id | f6a5f729-d5bf-4fa7-9cd9-e4ed23c7d48f | + | |
| - | | id | 7110ea40-8c32-4f99-8454-9a091bcd4623 | + | |
| - | | location | + | |
| - | | name | 128.135.37.244 | + | |
| - | | port_details | + | |
| - | | port_id | + | |
| - | | project_id | + | |
| - | | qos_policy_id | + | |
| - | | revision_number | + | |
| - | | router_id | + | |
| - | | status | + | |
| - | | subnet_id | + | |
| - | | tags | [] | | + | |
| - | | updated_at | + | |
| - | +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+</ | + | |
| - | Only you will be able to use this address until you destroy | + | With the router created and attached |
| - | Give this address to your Router, on a new interface. | + | After this command, the router will have one leg in your subnet and one leg in the public campus network (and internet). |
| + | |||
| + | Only you will be able to use this address until you destroy it. **DONT ever take more than you need and free this resource as soon as you project ends.** | ||
| < | < | ||
| - | openstack router set --fixed-ip subnet=$(openstack subnet show --format value --column id public37), | + | openstack router set myrouter \ |
| + | | ||
| + | | ||
| </ | </ | ||
| Line 219: | Line 216: | ||
| Like other openstack activities, creating a server has __many__ complex options and scenarios. This is a simple and ordinary depiction, creating one server | Like other openstack activities, creating a server has __many__ complex options and scenarios. This is a simple and ordinary depiction, creating one server | ||
| - | < | + | |
| + | < | ||
| + | openstack server create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| The command executed asynchronously, | The command executed asynchronously, | ||
| - | < | + | < |
| - | openstack server show myserver</ | + | openstack server list --name myserver |
| + | </ | ||
| + | < | ||
| + | openstack server show myserver | ||
| + | </ | ||
| Here's an example for creating 10 of them, as promised (only the change at the end of the command) | Here's an example for creating 10 of them, as promised (only the change at the end of the command) | ||
| - | < | + | < |
| + | openstack server create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | myserver | ||
| + | </ | ||
| Here's a nasty thing I use to determine what the security group is for a server (it can be determined also by looking at security groups directly) [ITS BRITTLE, BEWARE] | Here's a nasty thing I use to determine what the security group is for a server (it can be determined also by looking at security groups directly) [ITS BRITTLE, BEWARE] | ||
| - | < | + | < |
| + | SEC_GROUP=$(openstack port list \ | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | sed ' | ||
| + | </ | ||
| If I learned the security group successfully, | If I learned the security group successfully, | ||
| - | < | + | < |
| + | openstack security group rule create | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| In actual fact, all of the servers you create will be in the same security group. The above was attempting to suggest effective use of the tools, in combination. | In actual fact, all of the servers you create will be in the same security group. The above was attempting to suggest effective use of the tools, in combination. | ||
| Line 243: | Line 278: | ||
| You could also use the web interface to access the console, but that's not quite the same. | You could also use the web interface to access the console, but that's not quite the same. | ||
| As before, in the Network Gear section, get a campus IP address from our pool. | As before, in the Network Gear section, get a campus IP address from our pool. | ||
| - | < | + | |
| - | openstack server add floating ip myserver | + | |
| + | Where do you want to create your floating IP? | ||
| + | < | ||
| + | openstack network list | ||
| + | </ | ||
| + | Use the network from the previous command: | ||
| + | < | ||
| + | openstack floating ip create | ||
| + | </ | ||
| + | You now have an IP you can use: | ||
| + | < | ||
| + | openstack server add floating ip myserver | ||
| </ | </ | ||
/var/lib/dokuwiki/data/pages/cloud/intro.txt · Last modified: 2021/04/15 17:50 by chudler