openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

VERY IMPORTANT FIRST STEP: nova will have moved the ip from eth0 (or whichever device br100 is on) to br100, so if that ip address is needed, you will have to move it back to eth0. If you are connecting over that ip you will have to do it in a script so your connection doesn't drop. Check the <ip>/<netmask> by using ip addr show.

DISCLAIMER: writing this from memory so check for typos
(if br100 was bridged into a device without an ip address you can skip moving the ips but i would still delete br100)

On each node running nova-network:
ip addr del <ip>/<netmask> dev br100
ifconfig br100 down
brctl delbr br100
ip addr add <ip>/<netmask> dev eth0 


Now you should be able to make nova recreate everything for you
On each node running nova-network:
stop nova-network
killall dnsmasq
rm /var/lib/nova/networks/*
start nova-network

Vish

On Sep 7, 2012, at 8:33 AM, Jonathan Proulx <jon@xxxxxxxxxxxxx> wrote:

> Hi All,
> 
> Running Essex on Ununtu 12.04 using multi-host  FlatDHCP nova-networking
> 
> I ran out of IPs on my fixed_ip range so I shut everything (instances,
> nova-network, nova-compute) down deleted the old network and recreated
> it with a smaller netmask.  This seems to have almost worked.
> 
> I can start more instances than I previously had fixed ip's, the right
> ones seem to be being assigned and the mask on the recreated bridge
> interfaces is correct, but the (ubuntu-cloudimage) instances can't
> seem to see their NIC's any more, or perhaps aren't getting dhcp
> properly I'm still trying to force my way in as our instances rather
> rely on net access for accounts.
> 
> On the compute node things seem OK the bridge is up and the right
> things are connected:
> 
> root@nova-5:/var/log/nova# brctl show br100
> bridge name	bridge id		STP enabled	interfaces
> br100		8000.60eb69d22521	no		eth1
> 							vnet0
> 							vnet1
> 							vnet2
> 
> 
> I do notice this in iptables:
> 
> Chain nova-network-POSTROUTING (1 references)
> target     prot opt source               destination
> ACCEPT     all  --  10.0.0.0/16          nova-5.csail.mit.edu
> ACCEPT     all  --  10.0.0.0/16          10.128.0.0/24
> ACCEPT     all  --  10.0.0.0/16          10.0.0.0/16          ! ctstate DNAT
> 
> 
> my fixed range is 10.0.0.0/16 not sure where 10.128.0.0/24 comes into
> it as I don't use that network, but can't see that as a problem.
> 
> Can any one tell me what I've looked?
> 
> -Jon
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp