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 [2020/01/17 11:51] – kauffman | cloud:intro [2020/05/12 19:23] – [Annotated Example] chudler | ||
---|---|---|---|
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 myrouter mysubnet</ | + | < |
+ | openstack router create --enable myrouter | ||
+ | </ | ||
+ | < | ||
+ | openstack router add subnet myrouter mysubnet | ||
+ | </ | ||
With the router created and attached to your own subnet, develop it further. You need to obtain a free IP address on the UC Campus. We call this network __campus37__. The Internet-connected subnet on that network is called __public37__. | With the router created and attached to your own subnet, develop it further. You need to obtain a free IP address on the UC Campus. We call this network __campus37__. The Internet-connected subnet on that network is called __public37__. | ||
Line 176: | Line 198: | ||
< | < | ||
- | openstack router set myrouter --external-gateway campus37 --enable-snat | + | openstack router set myrouter |
+ | | ||
+ | | ||
</ | </ | ||
Line 192: | 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, | ||
Line 198: | Line 232: | ||
< | < | ||
openstack server list --name myserver | openstack server list --name myserver | ||
+ | </ | ||
+ | < | ||
openstack server show myserver | openstack server show myserver | ||
</ | </ | ||
Line 229: | Line 265: | ||
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 237: | 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 | ||
</ | </ | ||
Line 286: | Line 338: | ||
Q: What about containers (docker)? | Q: What about containers (docker)? | ||
- | A: We do not provide any support for them directly. We expect that you will want to manage this from inside the VMs that you create. We have no plans to deploy Magnum right now. | + | A: [[ cloud: |
Q: My servers are in ERROR state!!! | Q: My servers are in ERROR state!!! |
/var/lib/dokuwiki/data/pages/cloud/intro.txt · Last modified: 2021/04/15 17:50 by chudler