delete_network kills dnsmasq on wrong machine

Thanks JC.

For Essex, I would say that you need to run nova-manage from the host running nova-network. To avoid the problem, I would think a simple check if self.host == network['host'], with an error printed if this is false, would work.

In Folsom, nova-network will likely go away all together when using Quantum, so there's no point in adding anything too fancy.

In the mean time, I think I will update this in the docs.

Dan, Somik,

    Are you updating the all in one tar with quantum and your plugin ? We are moving to essex-4 tomorrow and was wondering if this was ready.
    By the way, it seems that the quantum package in https://launchpad.net/~openstack-ppa/+archive/milestone-proposed is broken. It fails :
Unpacking quantum (from .../quantum_2012.1~rc1~20120319.r765-0ubuntu0~oneiric17_all.deb) ...
Processing triggers for ureadahead ...
Setting up quantum (2012.1~rc1~20120319.r765-0ubuntu0~oneiric17) ...
Warning: The home dir /usr/share/quantum you specified can't be accessed: No such file or directory
adduser: The group `quantum' does not exist.
dpkg: error processing quantum (--configure):
 subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)

JC

Hi JC, since the PPA issue is a separate bug, I've file it here: https://bugs.launchpad.net/openstack-ppa/+bug/959859

I don't know who maintains those PPAs, but hopefully they will be able to help out.

Sorry, this comment was sent by mistake to this bug. It was a separate conversation.
It seems that launchpad played tricks with outlook.

I believe this was both fixed in trunk, and we updated the documentation to say that for essex, nova-manage network delete commands should be run on the host actually running nova-network.