Chapter 3. Common administrative networking tasks
Chapter 3. Common administrative networking tasks OpenStack Networking (neutron) is the software-defined networking component of Red Hat OpenStack Platform. The virtual network infrastructure enables connectivity between instances and the physical external network. This section contains information about common administration tasks, such as adding and removing subnets and routers to suit your Red Hat OpenStack Platform deployment. 3.1. Creating a network Create a network so that your instances can communicate with each other and receive IP addresses using DHCP. You can also integrate a network with external networks in your Red Hat OpenStack Platform deployment, or elsewhere, such as the physical network. This integration allows your instances to communicate with outside systems. For more information, see Bridge the physical network . When creating networks, it is important to know that networks can host multiple subnets. This is useful if you intend to host distinctly different systems in the same network, and prefer a measure of isolation between them. For example, you can designate that only webserver traffic is present on one subnet, while database traffic traverses another. Subnets are isolated from each other, and any instance that wants to communicate with another subnet must have their traffic directed by a router. Consider placing systems that require a high volume of traffic amongst themselves in the same subnet, so that they do not require routing, and can avoid the subsequent latency and load. In the dashboard, select Project > Network > Networks . Click +Create Network and specify the following values: Field Description Network Name Descriptive name, based on the role that the network will perform. If you are integrating the network with an external VLAN, consider appending the VLAN ID number to the name. For example, webservers_122 , if you are hosting HTTP web servers in this subnet, and your VLAN tag is 122 . Or you might use internal-only if you intend to keep the network traffic private, and not integrate the network with an external network. Admin State Controls whether the network is immediately available. Use this field to create the network in a Down state, where it is logically present but inactive. This is useful if you do not intend to enter the network into production immediately. Click the button, and specify the following values in the Subnet tab: Field Description Create Subnet Determines whether to create a subnet. For example, you might not want to create a subnet if you intend to keep this network as a placeholder without network connectivity. Subnet Name Enter a descriptive name for the subnet. Network Address Enter the address in CIDR format, which contains the IP address range and subnet mask in one value. To determine the address, calculate the number of bits masked in the subnet mask and append that value to the IP address range. For example, the subnet mask 255.255.255.0 has 24 masked bits. To use this mask with the IPv4 address range 192.168.122.0, specify the address 192.168.122.0/24. IP Version Specifies the internet protocol version, where valid types are IPv4 or IPv6. The IP address range in the Network Address field must match whichever version you select. Gateway IP IP address of the router interface for your default gateway. This address is the hop for routing any traffic destined for an external location, and must be within the range that you specify in the Network Address field. For example, if your CIDR network address is 192.168.122.0/24, then your default gateway is likely to be 192.168.122.1. Disable Gateway Disables forwarding and isolates the subnet. Click to specify DHCP options: Enable DHCP - Enables DHCP services for this subnet. You can use DHCP to automate the distribution of IP settings to your instances. IPv6 Address - Configuration Modes. If you create an IPv6 network, you must specify how to allocate IPv6 addresses and additional information: No Options Specified - Select this option if you want to set IP addresses manually, or if you use a non OpenStack-aware method for address allocation. SLAAC (Stateless Address Autoconfiguration) - Instances generate IPv6 addresses based on Router Advertisement (RA) messages sent from the OpenStack Networking router. Use this configuration to create an OpenStack Networking subnet with ra_mode set to slaac and address_mode set to slaac. DHCPv6 stateful - Instances receive IPv6 addresses as well as additional options (for example, DNS) from the OpenStack Networking DHCPv6 service. Use this configuration to create a subnet with ra_mode set to dhcpv6-stateful and address_mode set to dhcpv6-stateful. DHCPv6 stateless - Instances generate IPv6 addresses based on Router Advertisement (RA) messages sent from the OpenStack Networking router. Additional options (for example, DNS) are allocated from the OpenStack Networking DHCPv6 service. Use this configuration to create a subnet with ra_mode set to dhcpv6-stateless and address_mode set to dhcpv6-stateless. Allocation Pools - Range of IP addresses that you want DHCP to assign. For example, the value 192.168.22.100,192.168.22.100 considers all up addresses in that range as available for allocation. DNS Name Servers - IP addresses of the DNS servers available on the network. DHCP distributes these addresses to the instances for name resolution. Host Routes - Static host routes. First, specify the destination network in CIDR format, followed by the hop that you want to use for routing (for example, 192.168.23.0/24, 10.1.31.1). Provide this value if you need to distribute static routes to instances. Click Create . You can view the complete network in the Networks tab. You can also click Edit to change any options as needed. When you create instances, you can configure them now to use its subnet, and they receive any specified DHCP options. 3.2. Creating an advanced network Advanced network options are available for administrators, when creating a network from the Admin view. Use these options to specify projects and to define the network type that you want to use. To create an advanced network, complete the following steps: In the dashboard, select Admin > Networks > Create Network > Project . Select the project that you want to host the new network with the Project drop-down list. Review the options in Provider Network Type : Local - Traffic remains on the local Compute host and is effectively isolated from any external networks. Flat - Traffic remains on a single network and can also be shared with the host. No VLAN tagging or other network segregation takes place. VLAN - Create a network using a VLAN ID that corresponds to a VLAN present in the physical network. This option allows instances to communicate with systems on the same layer 2 VLAN. GRE - Use a network overlay that spans multiple nodes for private communication between instances. Traffic egressing the overlay must be routed. VXLAN - Similar to GRE, and uses a network overlay to span multiple nodes for private communication between instances. Traffic egressing the overlay must be routed. Click Create Network . Review the Project Network Topology to validate that the network has been successfully created. 3.3. Adding network routing To allow traffic to be routed to and from your new network, you must add its subnet as an interface to an existing virtual router: In the dashboard, select Project > Network > Routers . Select your virtual router name in the Routers list, and click Add Interface . In the Subnet list, select the name of your new subnet. You can optionally specify an IP address for the interface in this field. Click Add Interface . Instances on your network can now communicate with systems outside the subnet. 3.4. Deleting a network There are occasions where it becomes necessary to delete a network that was previously created, perhaps as housekeeping or as part of a decommissioning process. You must first remove or detach any interfaces where the network is still in use, before you can successfully delete a network. To delete a network in your project, together with any dependent interfaces, complete the following steps: In the dashboard, select Project > Network > Networks . Remove all router interfaces associated with the target network subnets. To remove an interface, find the ID number of the network that you want to delete by clicking on your target network in the Networks list, and looking at the ID field. All the subnets associated with the network share this value in the Network ID field. Navigate to Project > Network > Routers , click the name of your virtual router in the Routers list, and locate the interface attached to the subnet that you want to delete. You can distinguish this subnet from the other subnets by the IP address that served as the gateway IP. You can further validate the distinction by ensuring that the network ID of the interface matches the ID that you noted in the step. Click the Delete Interface button for the interface that you want to delete. Select Project > Network > Networks , and click the name of your network. Click the Delete Subnet button for the subnet that you want to delete. Note If you are still unable to remove the subnet at this point, ensure it is not already being used by any instances. Select Project > Network > Networks , and select the network you would like to delete. Click Delete Networks . 3.5. Purging the networking for a project Use the neutron purge command to delete all neutron resources that belong to a particular project. For example, to purge the neutron resources of the test-project project prior to deletion, run the following commands: 3.6. Working with subnets Use subnets to grant network connectivity to instances. Each instance is assigned to a subnet as part of the instance creation process, therefore it's important to consider proper placement of instances to best accommodate their connectivity requirements. You can create subnets only in pre-existing networks. Remember that project networks in OpenStack Networking can host multiple subnets. This is useful if you intend to host distinctly different systems in the same network, and prefer a measure of isolation between them. For example, you can designate that only webserver traffic is present on one subnet, while database traffic traverse another. Subnets are isolated from each other, and any instance that wants to communicate with another subnet must have their traffic directed by a router. Therefore, you can lessen network latency and load by grouping systems in the same subnet that require a high volume of traffic between each other. 3.6.1. Creating a subnet To create a subnet, follow these steps: In the dashboard, select Project > Network > Networks , and click the name of your network in the Networks view. Click Create Subnet , and specify the following values: Field Description Subnet Name Descriptive subnet name. Network Address Address in CIDR format, which contains the IP address range and subnet mask in one value. To determine the CIDR address, calculate the number of bits masked in the subnet mask and append that value to the IP address range. For example, the subnet mask 255.255.255.0 has 24 masked bits. To use this mask with the IPv4 address range 192.168.122.0, specify the address 192.168.122.0/24. IP Version Internet protocol version, where valid types are IPv4 or IPv6. The IP address range in the Network Address field must match whichever protocol version you select. Gateway IP IP address of the router interface for your default gateway. This address is the hop for routing any traffic destined for an external location, and must be within the range that you specify in the Network Address field. For example, if your CIDR network address is 192.168.122.0/24, then your default gateway is likely to be 192.168.122.1. Disable Gateway Disables forwarding and isolates the subnet. Click to specify DHCP options: Enable DHCP - Enables DHCP services for this subnet. You can use DHCP to automate the distribution of IP settings to your instances. IPv6 Address - Configuration Modes. If you create an IPv6 network, you must specify how to allocate IPv6 addresses and additional information: No Options Specified - Select this option if you want to set IP addresses manually, or if you use a non OpenStack-aware method for address allocation. SLAAC (Stateless Address Autoconfiguration) - Instances generate IPv6 addresses based on Router Advertisement (RA) messages sent from the OpenStack Networking router. Use this configuration to create an OpenStack Networking subnet with ra_mode set to slaac and address_mode set to slaac. DHCPv6 stateful - Instances receive IPv6 addresses as well as additional options (for example, DNS) from the OpenStack Networking DHCPv6 service. Use this configuration to create a subnet with ra_mode set to dhcpv6-stateful and address_mode set to dhcpv6-stateful. DHCPv6 stateless - Instances generate IPv6 addresses based on Router Advertisement (RA) messages sent from the OpenStack Networking router. Additional options (for example, DNS) are allocated from the OpenStack Networking DHCPv6 service. Use this configuration to create a subnet with ra_mode set to dhcpv6-stateless and address_mode set to dhcpv6-stateless. Allocation Pools - Range of IP addresses that you want DHCP to assign. For example, the value 192.168.22.100,192.168.22.100 considers all up addresses in that range as available for allocation. DNS Name Servers - IP addresses of the DNS servers available on the network. DHCP distributes these addresses to the instances for name resolution. Host Routes - Static host routes. First, specify the destination network in CIDR format, followed by the hop that you want to use for routing (for example, 192.168.23.0/24, 10.1.31.1). Provide this value if you need to distribute static routes to instances. Click Create . You can view the subnet in the Subnets list. You can also click Edit to change any options as needed. When you create instances, you can configure them now to use its subnet, and they receive any specified DHCP options. 3.7. Deleting a subnet You can delete a subnet if it is no longer in use. However, if any instances are still configured to use the subnet, the deletion attempt fails and the dashboard displays an error message. Complete the following steps to delete a specific subnet in a network: In the dashboard, select Project > Network > Networks . Click the name of your network. Select the target subnet, and click Delete Subnets . 3.8. Adding a router OpenStack Networking provides routing services using an SDN-based virtual router. Routers are a requirement for your instances to communicate with external subnets, including those in the physical network. Routers and subnets connect using interfaces, with each subnet requiring its own interface to the router. The default gateway of a router defines the hop for any traffic received by the router. Its network is typically configured to route traffic to the external physical network using a virtual bridge. To create a router, complete the following steps: In the dashboard, select Project > Network > Routers , and click Create Router . Enter a descriptive name for the new router, and click Create router . Click Set Gateway to the entry for the new router in the Routers list. In the External Network list, specify the network that you want to receive traffic destined for an external location. Click Set Gateway . After you add a router, you must configure any subnets you have created to send traffic using this router. You do this by creating interfaces between the subnet and the router. Important The default routes for subnets must not be overwritten. When the default route for a subnet is removed, the L3 agent automatically removes the corresponding route in the router namespace too, and network traffic cannot flow to and from the associated subnet. If the existing router namespace route has been removed, to fix this problem, perform these steps: Disassociate all floating IPs on the subnet. Detach the router from the subnet. Re-attach the router to the subnet. Re-attach all floating IPs. 3.9. Deleting a router You can delete a router if it has no connected interfaces. To remove its interfaces and delete a router, complete the following steps: In the dashboard, select Project > Network > Routers , and click the name of the router that you want to delete. Select the interfaces of type Internal Interface , and click Delete Interfaces . From the Routers list, select the target router and click Delete Routers . 3.10. Adding an interface You can use interfaces to interconnect routers with subnets so that routers can direct any traffic that instances send to destinations outside of their intermediate subnet. To add a router interface and connect the new interface to a subnet, complete these steps: Note This procedure uses the Network Topology feature. Using this feature, you can see a graphical representation of all your virtual routers and networks while you to perform network management tasks. In the dashboard, select Project > Network > Network Topology . Locate the router that you want to manage, hover your mouse over it, and click Add Interface . Specify the Subnet that you want to connect to the router. You can also specify an IP address. The address is useful for testing and troubleshooting purposes, since a successful ping to this interface indicates that the traffic is routing as expected. Click Add interface . The Network Topology diagram automatically updates to reflect the new interface connection between the router and subnet. 3.11. Deleting an interface You can remove an interface to a subnet if you no longer require the router to direct traffic for the subnet. To delete an interface, complete the following steps: In the dashboard, select Project > Network > Routers . Click the name of the router that hosts the interface that you want to delete. Select the interface type ( Internal Interface ), and click Delete Interfaces . 3.12. Configuring IP addressing Follow the procedures in this section to manage your IP address allocation in OpenStack Networking. 3.12.1. Creating floating IP pools You can use floating IP addresses to direct ingress network traffic to your OpenStack instances. First, you must define a pool of validly routable external IP addresses, which you can then assign to instances dynamically. OpenStack Networking routes all incoming traffic destined for that floating IP to the instance that you associate with the floating IP. Note OpenStack Networking allocates floating IP addresses to all projects (tenants) from the same IP ranges/CIDRs. As a result, all projects can consume floating IPs from every floating IP subnet. You can manage this behavior using quotas for specific projects. For example, you can set the default to 10 for ProjectA and ProjectB , while setting the quota for ProjectC to 0 . When you create an external subnet, you can also define the floating IP allocation pool. If the subnet hosts only floating IP addresses, consider disabling DHCP allocation with the --no-dhcp option in the openstack subnet create command: For example: 3.12.2. Assigning a specific floating IP You can assign a specific floating IP address to an instance using the nova command. In this example, a floating IP address is allocated to an instance named corp-vm-01 : 3.12.3. Assigning a random floating IP To dynamically allocate floating IP addresses to instances, complete these steps: Enter the following openstack command: In this example, you do not select a particular IP address, but instead request that OpenStack Networking allocate a floating IP address from the pool: After you allocate the IP address, you can assign it to a particular instance. Enter the following command to locate the port ID associated with your instance: (The port ID maps to the fixed IP address allocated to the instance.) Associate the instance ID with the port ID of the instance: openstack server add floating ip INSTANCE_NAME_OR_ID FLOATING_IP_ADDRESS For example: Validate that you used the correct port ID for the instance by making sure that the MAC address (third column) matches the port on the instance. 3.13. Creating multiple floating IP pools OpenStack Networking supports one floating IP pool for each L3 agent. Therefore, you must scale your L3 agents to create additional floating IP pools. Note Make sure that in /var/lib/config-data/neutron/etc/neutron/neutron.conf the property handle_internal_only_routers is set to True for only one L3 agent in your environment. This option configures the L3 agent to manage only non-external routers. 3.14. Bridging the physical network Bridge your virtual network to the physical network to enable connectivity to and from virtual instances. In this procedure, the example physical interface, eth0 , is mapped to the bridge, br-ex ; the virtual bridge acts as the intermediary between the physical network and any virtual networks. As a result, all traffic traversing eth0 uses the configured Open vSwitch to reach instances. For more information, see Chapter 11, Configuring bridge mappings . To map a physical NIC to the virtual Open vSwitch bridge, complete the following steps: Open /etc/sysconfig/network-scripts/ifcfg-eth0 in a text editor, and update the following parameters with values appropriate for the network at your site: IPADDR NETMASK GATEWAY DNS1 (name server) Here is an example: Open /etc/sysconfig/network-scripts/ifcfg-br-ex in a text editor and update the virtual bridge parameters with the IP address values that were previously allocated to eth0: You can now assign floating IP addresses to instances and make them available to the physical network.
openstack project list +----------------------------------+--------------+ | ID | Name | +----------------------------------+--------------+ | 02e501908c5b438dbc73536c10c9aac0 | test-project | | 519e6344f82e4c079c8e2eabb690023b | services | | 80bf5732752a41128e612fe615c886c6 | demo | | 98a2f53c20ce4d50a40dac4a38016c69 | admin | +----------------------------------+--------------+ neutron purge 02e501908c5b438dbc73536c10c9aac0 Purging resources: 100% complete. Deleted 1 security_group, 1 router, 1 port, 1 network. openstack project delete 02e501908c5b438dbc73536c10c9aac0 openstack subnet create --no-dhcp --allocation-pool start=IP_ADDRESS,end=IP_ADDRESS --gateway IP_ADDRESS --network SUBNET_RANGE NETWORK_NAME openstack subnet create --no-dhcp --allocation_pool start=192.168.100.20,end=192.168.100.100 --gateway 192.168.100.1 --network 192.168.100.0/24 public nova floating-ip-associate INSTANCE_NAME IP_ADDRESS nova floating-ip-associate corp-vm-01 192.168.100.20 openstack floating ip create openstack floating ip create public +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | fixed_ip_address | | | floating_ip_address | 192.168.100.20 | | floating_network_id | 7a03e6bc-234d-402b-9fb2-0af06c85a8a3 | | id | 9d7e2603482d | | port_id | | | router_id | | | status | ACTIVE | | tenant_id | 9e67d44eab334f07bf82fa1b17d824b6 | +---------------------+--------------------------------------+ openstack port list openstack port list +--------+------+-------------+--------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------+------+-------------+--------------------------------------------------------+ | ce8320 | | 3e:37:09:4b | {"subnet_id": "361f27", "ip_address": "192.168.100.2"} | | d88926 | | 3e:1d:ea:31 | {"subnet_id": "361f27", "ip_address": "192.168.100.5"} | | 8190ab | | 3e:a3:3d:2f | {"subnet_id": "b74dbb", "ip_address": "10.10.1.25"} | +--------+------+-------------+--------------------------------------------------------+ openstack server add floating ip VM1 172.24.4.225 openstack port list +--------+------+-------------+--------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------+------+-------------+--------------------------------------------------------+ | ce8320 | | 3e:37:09:4b | {"subnet_id": "361f27", "ip_address": "192.168.100.2"} | | d88926 | | 3e:1d:ea:31 | {"subnet_id": "361f27", "ip_address": "192.168.100.5"} | | 8190ab | | 3e:a3:3d:2f | {"subnet_id": "b74dbb", "ip_address": "10.10.1.25"}| +--------+------+-------------+--------------------------------------------------------+ vi /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=OVSPort DEVICETYPE=ovs OVS_BRIDGE=br-ex ONBOOT=yes vi /etc/sysconfig/network-scripts/ifcfg-br-ex DEVICE=br-ex DEVICETYPE=ovs TYPE=OVSBridge BOOTPROTO=static IPADDR=192.168.120.10 NETMASK=255.255.255.0 GATEWAY=192.168.120.1 DNS1=192.168.120.1 ONBOOT=yes