Ask Your Question
0

Changes to nova.conf not being picked up by nova-network

asked 2011-12-16 22:30:50 -0500

kenneth-jiang gravatar image

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?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2011-12-17 17:23:49 -0500

kenneth-jiang gravatar image

Thanks a lot Vish. After wresting with MySQL tables I was able to switch from Vlan to FlatDHCP.

edit flag offensive delete link more
0

answered 2011-12-16 22:48:41 -0500

kenneth-jiang gravatar image

I dug into nova-network.log and confirmed that my changes found their way into the log:

2011-12-16 14:21:18,204 DEBUG nova [-] Full set of FLAGS: from (pid=4297) wait /usr/lib/python2.7/dist-packages/nova/service.py:352 .....

2011-12-16 14:21:18,208 DEBUG nova [-] public_interface : br100 from (pid=4297) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 ... 2011-12-16 14:21:18,218 DEBUG nova [-] flat_interface : eth0.1728 from (pid=4297) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 ... 2011-12-16 14:21:18,229 DEBUG nova [-] network_manager : nova.network.manager.FlatDHCPManager from (pid=4297) wait /usr/lib/python2.7/dist-packages/nova/service.py:355

However, further down in the log nova-network for some reason stubbornly insisted the old behavior: ... 2011-12-16 14:21:18,519 DEBUG nova.utils [aca5807e-1a5d-4d31-9295-d03b546f75fd None None] Running cmd (subprocess): ip link show dev vlan100 from (pid=4297) execute /usr/lib/python2.7/dist-packages/nova/utils.py:166 ... 2011-12-16 14:21:18,526 DEBUG nova.utils [aca5807e-1a5d-4d31-9295-d03b546f75fd None None] Running cmd (subprocess): ip link show dev br100 from (pid=4297) execute /usr/lib/python2.7/dist-packages/nova/utils.py:166 2011-12-16 14:21:18,532 DEBUG nova.utils [aca5807e-1a5d-4d31-9295-d03b546f75fd None None] Running cmd (subprocess): sudo brctl addif br100 vlan100 from (pid=4297) execute /usr/lib/python2.7/dist-packages/nova/utils.py:166 ...

Again maybe I missed something obvious here?

edit flag offensive delete link more
0

answered 2011-12-17 00:31:33 -0500

vishvananda gravatar image

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).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2011-12-16 22:30:50 -0500

Seen: 35 times

Last updated: Dec 17 '11