[Openstack-operators] A couple of questions regarding Nova

Armando Migliaccio Armando.Migliaccio at eu.citrix.com
Mon Jan 30 15:12:01 UTC 2012

As for issue 1, have you thought of implementing the stop functionality as a combination of Snapshot+Terminate?

As for issue 2, there is a blueprint<https://blueprints.launchpad.net/nova/+spec/guest-ha> to deal with these sorts of scenarios.  Unfortunately that’s not going to help you in the immediate term because the effort hasn’t started yet (for lack of time more than anything else).

Hope this help!

From: openstack-operators-bounces at lists.openstack.org [mailto:openstack-operators-bounces at lists.openstack.org] On Behalf Of Gerrit Tamboer
Sent: 29 January 2012 09:38
To: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] A couple of questions regarding Nova


Unfortunately, no reply yet.
Does anyone have an idea how to solve these issues?

Especially the second question is a pain :)



On Fri, 27 Jan 2012 09:25:41 +0100, Gerrit Tamboer <gerrit at gerr1t.nl> wrote:


We are currently testing the Openstack Nova product, but we have 2 problems/questions which we haven't find a decent solution for yet.

1. In The Nova-api v1.1 there is no option to Stop and Start an instance, only Reboot and Terminate. I know that these options are available in v2.0 which is in Beta right now.
Because we would like to work with the stable version of the Nova-Api we are not planning to move to v2.0 for now.
We are wondering if anyone has managed to find a solution for this issue? Is there a 'clean' way to implement and use a Stop and Start function in the API? We can of course make an exception by using custom shell scripts for the stop and start function (using virsh destroy/start) but this is kinda nasty ;)..

2. On our Nova-Compute machines we have shared storage using an iSCSI target which gives us the ability to use Live Migration. This is working perfectly! The only problem we are facing at this moment is that we want to be able to start an instance on a different Compute Node when the original Compute Node goes down. Is there an easy way or (even better) an API call which can be used for this? The Live Migration function does not work when the original Nova Compute node is down. We are currently planning to implement our own patch which detects a compute node going down and automatically starts the instances on different compute nodes using various algorithms. Only the last part (starting an instance on a different node) is something we need to figure out, hopefully you guys can help! :)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120130/26d0a5c8/attachment-0002.html>

More information about the Openstack-operators mailing list