Greetings,

I’ve recently installed Openstack Havana running on multiple Ubuntu 12.04.3 
servers and am seeing the following problem.

If I configure neutron with one external network and multiple tenant routers 
connected to individual tenant private networks, only the first instance that 
boots will successfully receive an address via DHCP on its tenant’s private 
network.  All other instances, in different tenants, will fail at the DHCP 
discover stage of their boot.

The networks / routers are configured in neutron as follows:

(neutron) net-list
+--------------------------------------+------------+----------------------------------------------------+
| id                                   | name       | subnets                   
                         |
+--------------------------------------+------------+----------------------------------------------------+
| 05137211-1660-44e1-ae50-107900090e05 | admin-net  | 
87fe46cd-e668-4d25-9b7a-fb8cfd0ac382 10.0.2.0/24   |
| 1bb61407-bd6f-4d23-9737-63513fad50ec | campus-net | 
be08e3ca-2ebf-4617-96de-b79ad6dc4ac1 173.23.0.0/16 |
| 3c782e04-66b0-4fcb-8cfe-a865a1407271 | da-net     | 
565a4dbd-2607-4a71-9588-2cb859adf387 10.0.3.0/24   |
| 7a2a1fe4-6936-4151-9fb1-8d12ff7d1179 | ws-net     | 
8200a757-382b-4eda-b148-5dd68d9f5e59 10.0.1.0/24   |
+--------------------------------------+------------+----------------------------------------------------+
(neutron) subnet-list
+--------------------------------------+-------------------+---------------+----------------------------------------------------+
| id                                   | name              | cidr          | 
allocation_pools                                   |
+--------------------------------------+-------------------+---------------+----------------------------------------------------+
| 565a4dbd-2607-4a71-9588-2cb859adf387 | da-net.private    | 10.0.3.0/24   | 
{"start": "10.0.3.2", "end": "10.0.3.254"}         |
| 8200a757-382b-4eda-b148-5dd68d9f5e59 | ws-net.private    | 10.0.1.0/24   | 
{"start": "10.0.1.2", "end": "10.0.1.254"}         |
| 87fe46cd-e668-4d25-9b7a-fb8cfd0ac382 | admin-net.private | 10.0.2.0/24   | 
{"start": "10.0.2.2", "end": "10.0.2.254"}         |
| be08e3ca-2ebf-4617-96de-b79ad6dc4ac1 | campus-net.pooled | 173.23.0.0/16 | 
{"start": "173.23.182.2", "end": "173.23.183.254"} |
+--------------------------------------+-------------------+---------------+----------------------------------------------------+
(neutron) router-list
+--------------------------------------+----------+-----------------------------------------------------------------------------+
| id                                   | name     | external_gateway_info       
                                                |
+--------------------------------------+----------+-----------------------------------------------------------------------------+
| 1a0d2733-45db-4eca-860e-2f4091689e3d | admin-gw | {"network_id": 
"1bb61407-bd6f-4d23-9737-63513fad50ec", "enable_snat": true} |
| bf2642fd-b4ec-494f-9ca5-fc7b282fc629 | ws-gw    | {"network_id": 
"1bb61407-bd6f-4d23-9737-63513fad50ec", "enable_snat": true} |
+--------------------------------------+----------+-----------------------------------------------------------------------------+
(neutron)

Both routers have campus-net set as their gateways and campus-net is a “shared” 
network.

The following dnsmasq processes are running on the network controller:

3924 ?        S      0:00 dnsmasq --no-hosts --no-resolv --strict-order 
--bind-interfaces --interface=tapc1c5379d-d8 --except-interface=lo 
--pid-file=/var/lib/neutron/dhcp/05137211-1660-44e1-ae50-107900090e05/pid 
--dhcp-hostsfile=/var/lib/neutron/dhcp/05137211-1660-44e1-ae50-107900090e05/host
 
--dhcp-optsfile=/var/lib/neutron/dhcp/05137211-1660-44e1-ae50-107900090e05/opts 
--leasefile-ro --dhcp-range=set:tag0,10.0.2.0,static,86400s 
--dhcp-lease-max=256 --conf-file= --domain=openstacklocal
 4035 ?        S      0:00 dnsmasq --no-hosts --no-resolv --strict-order 
--bind-interfaces --interface=tap87773916-c3 --except-interface=lo 
--pid-file=/var/lib/neutron/dhcp/7a2a1fe4-6936-4151-9fb1-8d12ff7d1179/pid 
--dhcp-hostsfile=/var/lib/neutron/dhcp/7a2a1fe4-6936-4151-9fb1-8d12ff7d1179/host
 
--dhcp-optsfile=/var/lib/neutron/dhcp/7a2a1fe4-6936-4151-9fb1-8d12ff7d1179/opts 
--leasefile-ro --dhcp-range=set:tag0,10.0.1.0,static,86400s 
--dhcp-lease-max=256 --conf-file= --domain=openstacklocal
 6289 ?        S      0:00 dnsmasq --no-hosts --no-resolv --strict-order 
--bind-interfaces --interface=tape5641d4f-22 --except-interface=lo 
--pid-file=/var/lib/neutron/dhcp/3c782e04-66b0-4fcb-8cfe-a865a1407271/pid 
--dhcp-hostsfile=/var/lib/neutron/dhcp/3c782e04-66b0-4fcb-8cfe-a865a1407271/host
 
--dhcp-optsfile=/var/lib/neutron/dhcp/3c782e04-66b0-4fcb-8cfe-a865a1407271/opts 
--leasefile-ro --dhcp-range=set:tag0,10.0.3.0,static,86400s 
--dhcp-lease-max=256 --conf-file= --domain=openstacklocal

with the campus-net.pooled subnet having DHCP disabled for floating IP use.

All servers are at the latest patch level using the Ubuntu cloud archives.

I believe that if I create a ‘provider’ router and attach each client network 
to a port on the provider network that everything works OK - however this 
configuration limits the usefulness of using neutron as the network service.

More than likely I have yet another configuration bug, however is this a known 
issue? Or does anyone have any suggestions.  Thanks in advance.

Regards
Ross



--
Ross Lillie
Distinguished Member of Technical Staff
Motorola Solutions, Inc.

motorolasolutions.com<http://motorolasolutions.com>
O: +1.847.576.0012
M: +1.847.980.2241
E: [email protected]


[cid:[email protected]]

<<inline: MSI-Email-Identity-sm.png>>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to