Hi,
It seems due to an OVS quantum bug, we need to run the utility
quantum-ovs-cleanup before any of the quantum services start, upon a
server reboot.
Where is the best place to put this utility to run automatically when
a server reboots so that the OVS issue is automatically addressed? A
script
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I put it in the file:/etc/init/quantum-server.conf
post-start script
/usr/bin/quantum-ovs-cleanup
exit 1
end script
On 04/24/2013 02:45 AM, Balamurugan V G wrote:
Hi,
It seems due to an OVS quantum bug, we need to run the
Thanks Steve.
I came across another way at
https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems
to work as well. But your solution is simpler :)
Regards,
Balu
On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand steve.heist...@nasa.gov wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it was mentioned to me (by Mr Mihaiescu) that this only works if controller and
network node
are on the same machine. For the compute nodes I had forgotten its in a
different
place. On them I am doing it in a pre-start script in
Right now, I have a single node setup on which I am qualifying my use
cases but eventually I will have a controller node, network node and
several compute nodes. In that case, do you mean it should something
like this?
Controller : post-start of quantum-server.cong
Network : post-start of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The network node probably wont be running quantum server just one
of the agents, so you put the command in one of those configs not
quantum-server.
That is what Im doing currently and it is working for me.
at some point if you have running VMs with
Ok thanks, this helps a lot. But isnt this being done to avoid those
disruptions/issues with networking after a restart. Do you mean do
doing this will result in disruptions after a restart?
Regards,
Balu
On Wed, Apr 24, 2013 at 9:12 PM, Steve Heistand steve.heist...@nasa.gov wrote:
-BEGIN
7 matches
Mail list logo
