search

termie / nova-migration-demo

Nova is a cloud computing fabric controller (the main part of an IaaS system). It is written in Python.
http://openstack.org/projects/compute/
Apache License 2.0
2 stars 0 forks source link

Add optional support for --libvirt_xml_template reloading #547

Open termie opened 13 years ago

termie commented 13 years ago

Using the flag "--libvirt_xml_template" in nova.conf, the template file is only read one when starting nova-compute. For each change in the template file you have to restart nova-compute.

Imported from Launchpad using lp2gh.

termie commented 13 years ago

(by vishvananda) I don't think this is really a bug. Perhaps it could be a feature request, but I'm not sure of the value of it. In production the xml shouldn't change. In dev mode it isn't that bad to have to restart the worker if you change it.

Vish

On Feb 22, 2011, at 8:34 AM, Andre Nähring wrote:

Public bug reported:

Using the flag "--libvirt_xml_template" in nova.conf, the template file is only read one when starting nova-compute. For each change in the template file you have to restart nova-compute.

\ Affects: nova Importance: Undecided Status: New

You received this bug notification because you are a member of Nova Bug Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/723235

Title: flag --libvirt_xml_template only read once while nova-services launching

Status in OpenStack Compute (Nova): New

Bug description: Using the flag "--libvirt_xml_template" in nova.conf, the template file is only read one when starting nova-compute. For each change in the template file you have to restart nova-compute.

termie commented 13 years ago

(by ttx) Could you explain your use case ?

termie commented 13 years ago

(by naehring) We have been testing special images running in xen in use with nova. Several changes to the xml template have been neccessary to use with our images. It took some time to me, to find out why the changes won't be applied.

Maybe we can add another flag e.g. "--debug_libvirt_template=[true/false]" ? When true, compute should read the libvirt template each time an instance is created. When false (default) it should be read only once.

If this is interesting to you, I would spend time to learn some python and create the neccessary changes. But this does only make sense if I am not the only person with this use case.

termie commented 13 years ago

(by ttx) I think that's a bit of a corner case... but if you want to scratch your own itch, I certainly won't prevent you from contributing code :)