Chapter 5. Managing floating IP addresses

Procedure

1. In the dashboard, select Admin > Networks > Create Network > Project.
2. Select the project that you want to host the new network with the Project drop-down list.

3. 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.

4. Click Create Network.

   Review the Project Network Topology to validate that the network has been successfully created.

Procedure

1. Enter the following command to allocate a floating IP address from the pool. In this example, the network is named public.

   Example

   $ openstack floating ip create public

   Sample output

   In the following example, the newly allocated floating IP is 192.0.2.200. You can assign it to an instance.

   +---------------------+--------------------------------------------------+
   | Field               | Value                                            |
   +---------------------+--------------------------------------------------+
   | fixed_ip_address    | None                                             |
   | floating_ip_address | 192.0.2.200                                      |
   | floating_network_id | f0dcc603-f693-4258-a940-0a31fd4b80d9             |
   | id                  | 6352284c-c5df-4792-b168-e6f6348e2620             |
   | port_id             | None                                             |
   | router_id           | None                                             |
   | status              | ACTIVE                                           |
   +---------------------+--------------------------------------------------+

2. Enter the following command to locate your instance:

   $ openstack server list

   Sample output

   +-------------+-------------+--------+-------------+-------+-------------+
   | ID          | Name        | Status | Networks    | Image | Flavor      |
   +-------------+-------------+--------+-------------+-------+-------------+
   | aef3ca09-88 | prod-serv1  | ACTIVE | public=198. | rhel8 | review-     |
   | 7d-4d20-872 |             |        | 51.100.56   |       | ephemeral   |
   | d-1d1b49081 |             |        |             |       |             |
   | 958         |             |        |             |       |             |
   |             |             |        |             |       |             |
   +-------------+-------------+--------+-------------+-------+-------------+

3. Associate the instance name or ID with the floating IP.

   Example

   $ openstack server add floating ip prod-serv1 192.0.2.200

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. In a custom environment YAML file, set the port_forwarding service plug-in:

   parameter_defaults:
     NeutronPluginExtensions: "router,port_forwarding"

   Note

   The port_forwarding service plug-in requires that you also set the router service plug-in.

4. If you use the ML2/OVS mechanism driver with the Networking service, you must also set the port_forwarding extension for the OVS L3 agent:

   parameter_defaults:
     NeutronPluginExtensions: "router,port_forwarding"
     NeutronL3AgentExtensions: "port_forwarding"

5. Deploy your overcloud and include the core heat templates, environment files, and this new custom environment file.

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   $ openstack overcloud deploy --templates \
    -e <your_environment_files> \
    -e /home/stack/templates/my-environment.yaml

   RHOSP users can now set up port forwarding for floating IPs. For more information, see Section 5.7, “Creating port forwarding for a floating IP”.

Verification

1. Source the overcloud credentials file.

   Example

   $ source ~/overcloudrc

2. Ensure that the Networking service has successfully loaded the port_forwarding and router service plug-ins:

   $ openstack extension list --network -c Name -c Alias --max-width 74 | \
   grep -i -e 'Neutron L3 Router' -i -e floating-ip-port-forwarding

   Sample output

   A successful verification produces output similar to the following:

   | Floating IP Port Forwarding       | floating-ip-port-forwarding        |
   | Neutron L3 Router                 | router                             |

Procedure

1. Source your credentials file.

   Example

   $ source ~/overcloudrc

2. Use the following command to create port forwarding for a floating IP:

   $ openstack floating ip port forwarding create \
   --internal-ip-address <internal-ip-address> \
   --port <port> \
   --internal-protocol-port <port-number> \
   --external-protocol-port <port-number> \
   --protocol <protocol> \
   <floating-ip>

   • Replace <internal-ip-address> with the internal, destination IP address.

     This is the IP address that is associated with the instance on which the application is running.

   • Replace <port> with the name or ID of the Networking service port to which the instance is attached.

   • Replace <port-number> in --internal-protocol-port with the internal, destination port number.

     This is the port number that the application running in the instance uses.

   • Replace <port-number> in --external-protocol-port with the external, source port number.

     This is the port number that the application running outside of your RHOSP cloud uses.

   • Replace <protocol> with the protocol, such as TCP or UDP, used by the application that receives the port-forwarded traffic.

   • Replace <floating-ip> with the floating IP whose specified port traffic you want to forward.

     Example

     This example creates port fowarding for an instance that is attached to the floating IP 198.51.100.47. The floating IP uses the Networking service port 1adfdb09-e8c6-4708-b5aa-11f50fc22d62. When the Networking service detects incoming, external traffic addressed to 198.51.100.47:80, it forwards the traffic to the internal IP address, 203.0.113.107, on TCP port, 8080:

     $ openstack floating ip port forwarding create \
     --internal-ip-address 203.0.113.107 \
     --port 1adfdb09-e8c6-4708-b5aa-11f50fc22d62 \
     --internal-protocol-port 8080 \
     --external-protocol-port 80 \
     --protocol tcp \
     198.51.100.47

Procedure

1. 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:

     # vi /etc/sysconfig/network-scripts/ifcfg-eth0
     DEVICE=eth0
     TYPE=OVSPort
     DEVICETYPE=ovs
     OVS_BRIDGE=br-ex
     ONBOOT=yes

2. 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:

   # 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

   You can now assign floating IP addresses to instances and make them available to the physical network.

1. In the dashboard, select Project > Network > Network Topology.
2. Locate the router that you want to manage, hover your mouse over it, and click Add Interface.

3. 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.

4. Click Add interface.

   The Network Topology diagram automatically updates to reflect the new interface connection between the router and subnet.

1. In the dashboard, select Project > Network > Routers.
2. Click the name of the router that hosts the interface that you want to delete.
3. Select the interface type (Internal Interface), and click Delete Interfaces.