User Tools

Site Tools


cloud:intro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
cloud:intro [2020/01/17 11:51] kauffmancloud:intro [2020/01/17 11:54] kauffman
Line 153: Line 153:
  
 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
-<code>openstack network create mynet  --provider-network-type geneve  --enable-port-security --internal</code>+<code> 
 +openstack network create mynet 
 +  --provider-network-type geneve 
 +  --enable-port-security 
 +  --internal 
 +</code>
  
 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 168:
 You are now advised that there is no "correct" choice for subnet range and IP. Overlaps are **not** a concern unless you intend to perform route/tunneling among the overlapping regions. You are now advised that there is no "correct" choice for subnet range and IP. Overlaps are **not** a concern unless you intend to perform route/tunneling among the overlapping regions.
  
-<code>openstack subnet create --network mynet --ip-version 4 --subnet-range 192.168.222.0/24 --allocation-pool start=192.168.222.10,end=192.168.222.240 --dns-nameserver 128.135.164.141 mysubnet --gateway 192.168.222.1 --dhcp</code>+<code> 
 +openstack subnet create 
 +  --network mynet 
 +  --ip-version 4 
 +  --subnet-range 192.168.222.0/24 
 +  --allocation-pool start=192.168.222.10,end=192.168.222.240 
 +  --dns-nameserver 128.135.164.141 mysubnet 
 +  --gateway 192.168.222.1 
 +  --dhcp 
 +</code>
  
 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, and allow clients to access the internet via outbound NAT. Much more is possible, and a router is a prerequisite for the next step, which is inbound NAT (DNAT). 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, and allow clients to access the internet via outbound NAT. Much more is possible, and a router is a prerequisite for the next step, which is inbound NAT (DNAT).
-<code>openstack router create --enable myrouter + 
-openstack router add subnet myrouter mysubnet</code>+<code> 
 +openstack router create --enable myrouter 
 +</code> 
 +<code> 
 +openstack router add subnet myrouter mysubnet 
 +</code>
  
 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 195:
  
 <code> <code>
-openstack router set myrouter --external-gateway campus37 --enable-snat+openstack router set myrouter 
 +  --external-gateway campus37 
 +  --enable-snat
 </code> </code>
  
Line 198: Line 219:
 <code> <code>
 openstack server list --name myserver openstack server list --name myserver
 +</code>
 +<code>
 openstack server show myserver openstack server show myserver
 </code> </code>
Line 229: Line 252:
 If I learned the security group successfully, I can let in SSH. By default, **no communication is possible**. If I learned the security group successfully, I can let in SSH. By default, **no communication is possible**.
  
-<code>openstack security group rule create --ingress --dst-port 22 --protocol tcp $SEC_GROUP</code>+<code> 
 +openstack security group rule create 
 +  --ingress 
 +  --dst-port 22 
 +  --protocol tcp $SEC_GROUP 
 +</code>
  
 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 265:
 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.
-<code>openstack floating ip create+ 
 +<code> 
 +openstack floating ip create 
 +</code> 
 +<code>
 openstack server add floating ip myserver 128.135.37.XX openstack server add floating ip myserver 128.135.37.XX
 </code> </code>
/var/lib/dokuwiki/data/pages/cloud/intro.txt · Last modified: 2021/04/15 17:50 by chudler

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki