So right now, the networks are created via the information in the database. This data is set when the network is created, so you will have to update the interface in the networks table to match.

On Dec 16, 2011, at 2:31 PM, Tianchen Jiang wrote:

New question #182159 on OpenStack Compute (nova): https://answers.launchpad.net/nova/+q...

I made several changes to /etc/nova/nova.conf but they didn't seem to be picked up by nova-network. And I not only restarted nova-network, but also rebooted the machine!

In /etc/nova/nova.conf, I made the following changes:

... --public_interface=eth0 --vlan_interface=eth1 ...

---->

..... --network_manager=nova.network.manager.FlatDHCPManager --public_interface=br100 --flat_interface=eth0.1728 ...

I checked and the right conf path was given to nova-network

ps -ef | grep nova-network

nova 4012 1 0 14:09 ? 00:00:00 su -c nova-network --flagfile=/etc/nova/nova.conf nova nova 4019 4012 0 14:09 ? 00:00:02 /usr/bin/python /usr/bin/nova-network --flagfile=/etc/nova/nova.conf

However after rebooting the machine, nova-network still bridged vlan100 to br100, and completely ignored eth0.1728:

brctl show

bridge name bridge id STP enabled interfaces br100 8000.02163e3e4a7e no vlan100 virbr0 8000.000000000000 yes

I also checked to make sure eth0.1728 was brought up correct:

ip link show eth0.1728

4: eth0.1728@eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc noqueue state UP link/ether 98:4b:e1:5f:e7:e2 brd ff:ff:ff:ff:ff:ff

I probably missed something obvious here. Any hints why that happened?

---

You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).