OpenStack Compute (nova)

VLAN Networking Inconsistency

Bug #889060 reported by Kiall Mac Innes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Firstly, I'm not sure how to mark this as a Feature Request rather than a Bug.. So, Apologies!

There appears to be some inconsistency in what IP address instances are able to talk to other instances on. There seems to be no way to have 1 IP that all other instances can use to talk to. Details Below

Given the following setup:
=====================

2x Servers:
 - Server01 is running all services, including compute and network.
 - Server02 is running compute and network.

Both servers are configured for VLAN networking.

172.16.x.x = Fixed IP range (Configured for multi-host)
78.153.x.x = Floating IP range

4x Instances:
 - On Server 1:
   - Instance01, FixedIP assigned, No FloatingIP
   - Instance02, FixedIP assigned, FloatingIP assigned
 - On Server 2:
   - Instance03, FixedIP assigned, No FloatingIP
   - Instance04, FixedIP assigned, FloatingIP assigned

The following are the results of pinging instances from each other:
======================================================

On Instance01:
============

ping Instance02-FixedIP - Success
ping Instance02-FloatingIP - Success

ping Instance03-FixedIP - Success

ping Instance04-FixedIP - Success
ping Instance04-FloatingIP - FAILURE

On Instance02:
============

ping Instance01-FixedIP - Success

ping Instance03-FixedIP - FAILURE

ping Instance04-FixedIP - FAILURE
ping Instance04-FloatingIP - Success

Revision history for this message
Kiall Mac Innes (kiall) wrote :

I probably should have included the nova.conf:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--force_dhcp_release=True
--use_deprecated_auth
--iscsi_helper=tgtadm
--verbose
--sql_connection=mysql://nova:XXX@78.153.xxx.xxx/nova
--vlan_interface=eth1
--zone_name=dub01
--node_availability_zone=dub01
--storage_availability_zone=dub01
--allow_admin_api=true
--enable_zone_routing=true
--resume_guests_state_on_host_boot=true
--api_paste_config=api-paste-keystone.ini
--vncserver_host=78.153.xxx.xxx
--vncproxy_url=http://78.153.xxx.xxx:6080
--ajax_console_proxy_url=http://78.153.xxx.xxx:8000
--glance_api_servers=78.153.xxx.xxx:9292
--ec2_dmz_host=78.153.xxx.xxx
--s3_dmz=78.153.xxx.xxx
--ec2_host=78.153.xxx.xxx
--s3_host=78.153.xxx.xxx
--osapi_host=78.153.xxx.xxx
--rabbit_host=78.153.xxx.xxx
--dmz_net=172.16.0.0
--dmz_mask=255.240.0.0

Revision history for this message
Kiall Mac Innes (kiall) wrote :

After poking around with the iptables rules, I discovered I was missing the --fixed_range=172.16.0.0/12 flag..

Apologies for the noise :)

Changed in nova:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.