Attaching Multiple Network Interfaces and Floating IPs to OpenStack Instances with Neutron

Thu Feb 5 10:49:24 2015

Last edited Thu Feb 5 03:18:40 2015 Posted by Craige McWhirter on

There are a number of use cases where you may need to connect multiple floating IPs to existing OpenStack instances. However the functionality to do this is not exposed via the Horizon Dashboard. This is how I go about attaching multiple network interfaces and floating IPs to OpenStack instances with Neutron.

Assumptions:

You have already configured your workstation as an OpenStack client

You have a working OpenStack cloud :-)

Port Creation and Assignment

When you have your environment sourced appropriately, get a list of networks for this tenant:

% neutron net-list +--------------------------------------+--------------+-------------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------------+-------------------------------------------------------+ | 85314baa-a022-4dd1-918c-a73c83c8cad6 | ext-net | 9248bc58-6cfe-4ff8-b33e-286a60c96c6d 999.999.999.0/23 | | ee31dc0e-e226-423d-a7fe-f564dc17614e | DemoTutorial | 5821de82-3843-46ce-a796-c801bf40fd4c 192.168.71.0/24 | +--------------------------------------+--------------+-------------------------------------------------------+

We're interested in the non-external network. In this case "DemoTutorial". I normally set this to $OS_NET. Now we can create a new port on that network.

% export OS_NET=ee31dc0e-e226-423d-a7fe-f564dc17614e % neutron port-create $OS_NET Created a new port: +-----------------------+---------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+---------------------------------------------------------------------------------------+ | admin_state_up | True | | allowed_address_pairs | | | binding:vnic_type | normal | | device_id | | | device_owner | | | fixed_ips | {"subnet_id": "af150a1e-067a-4641-89a4-24c5b6b8fe3b", "ip_address": "192.168.71.180"} | | id | fd2f78df-cf78-4394-84eb-9e37ed1e5624 | | mac_address | fa:54:6e:f2:ce:a9 | | name | | | network_id | ee31dc0e-e226-423d-a7fe-f564dc17614e | | security_groups | b1240686-7ad9-4d29-a679-d219f76648ca | | status | DOWN | | tenant_id | abcd639c50804cf3end71b92e6ced65e | +-----------------------+---------------------------------------------------------------------------------------+

We now need to note the id or as I do, assign it to $PORT_ID. Next we fire up nova. I'm going to assume that you know either the instance name or ID and have assigned it to $INSTANCE.

% export PORT_ID=fd2f78df-cf78-4394-84eb-9e37ed1e5624 % export INSTANCE=3c7ae1b9-8111-4f15-9945-75e0af157ead % nova interface-attach --port-id $PORT_ID $INSTANCE

You should now have successfully added a second network interface to your OpenStack instance. Let's double check that:

% nova show $INSTANCE | grep network | DemoTutorial network | 192.168.71.180, 192.168.71.181

Great! Now you have two internal IP addresses, one for each port assigned to that tenant.

Assigning Floating IPs

You can now add floating IPs either via the Horizon Dashboard or via the neutron client. I'll cover how to do this via the CLI. Fire up neutron, locate the original port and assign it's UUID to $PORT_ID0:

% neutron port-list | grep 192.168.71.181 fa:46:7e:21:4f:f3 | {"subnet_id": "8f987932-48ee-4262-8b44-0c910512a387", "ip_address": "192.168.71.181"} | % export PORT_ID0=8f987932-48ee-4262-8b44-0c910512a387

Then we get a list of available floating IPs and assign those to variables too:

% neutron floatingip-list +--------------------------------------+------------------+---------------------+---------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+---------+ | 390e4676-0e05-40c3-9012-e5d27eb85dbe | | 999.999.999.123 | | | 16f7ca27-1d11-4967-9f0c-04f578590b01 | | 999.999.999.124 | | | f983b10d-454c-4c19-8f65-d9b96c4d7aa6 | | 999.999.999.125 | | +--------------------------------------+------------------+---------------------+---------+ % export FIP0=16f7ca27-1d11-4967-9f0c-04f578590b01 % export FIP1=f983b10d-454c-4c19-8f65-d9b96c4d7aa6 % neutron floatingip-associate $FIP0 $PORT_ID Associated floating IP 16f7ca27-1d11-4967-9f0c-04f578590b01 % neutron floatingip-associate $FIP1 $PORT_ID0 Associated floating IP f983b10d-454c-4c19-8f65-d9b96c4d7aa6

We can then verify this assignment:

% neutron floatingip-list +--------------------------------------+------------------+---------------------+---------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+---------+ | 390e4676-0e05-40c3-9012-e5d27eb85dbe | | 999.999.999.123 | | | 16f7ca27-1d11-4967-9f0c-04f578590b01 | 192.168.71.180 | 999.999.999.124 | | | f983b10d-454c-4c19-8f65-d9b96c4d7aa6 | 192.168.71.181 | 999.999.999.125 | | +--------------------------------------+------------------+---------------------+---------+

For good measure you can double check how Nova sees this assignment:'

% nova show $INSTANCE | grep network | DemoTutorial network | 192.168.71.180, 192.168.71.181, 999.999.999.124, 999.999.999.125

You're done :-)