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/06 15:55] – chudler | cloud:intro [2020/01/17 11:51] – kauffman | ||
---|---|---|---|
Line 1: | Line 1: | ||
=== SCOPE OF THIS DOCUMENT === | === SCOPE OF THIS DOCUMENT === | ||
- | This guide covers | + | This guide covers |
Some things that are not written about here but perhaps should be covered elsewhere | Some things that are not written about here but perhaps should be covered elsewhere | ||
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 167: | Line 167: | ||
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</ | + | openstack router add subnet |
- | With the router created and attached to your subnet, develop it further. | + | With the router created and attached to your own subnet, develop it further. |
- | < | + | |
- | The output of the command | + | After this command, the router will have one leg in your subnet and one leg in the public campus network |
- | < | + | |
- | +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | + | |
- | | Field | Value | | + | |
- | +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | + | |
- | | created_at | + | |
- | | 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 it. **DONT ever take more than you need and free this resource as soon as you project ends.** | 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.** | ||
- | |||
- | 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). The example above gave us 128.135.37.244. | ||
< | < | ||
- | openstack router set --fixed-ip subnet=$(openstack subnet show --format value --column id public37), | + | openstack router set myrouter |
</ | </ | ||
Line 223: | Line 196: | ||
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, |
/var/lib/dokuwiki/data/pages/cloud/intro.txt · Last modified: 2021/04/15 17:50 by chudler