We have a prototype of similar capabilities targeting Nova services, using
ZooKeeper (heartbeat/membership, leader election, etc -- will share with
the community soon). Would be interesting to compare the two approaches.
Regards,
Alex
From: Martin Gerhard Loschwitz
To: openstack@lists
original host recovers, it does not cause
corruption of the instance file on shared storage (e.g., by removing the
corresponding VM from the original host on startup)
Regards,
Alex
Alex Glikson
> From: "Daniel P. Berrange"
> On Tue, Jul 31, 2012 at 10:50:02AM -0700, Bhuvaneswaran A wrote:
> > Stefano,
> >
> > If a subscriber reply to a mailing list message, it's sent to the
> > author only. Each subscriber should use "Reply to All" every time, to
> > post a reply to mailing list.
> >
>
iated.
Thanks,
Alex
========
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html |
https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
Email: glik...@il.ibm.com | P
> From: Ryan Lane
> > We have submitted a patch https://review.openstack.org/#/c/11086/ to
address
> > https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha that
simplifies
> > recovery from a node failure by introducing an API that recreates an
> > instance on *another* host (similar to th
Can you elaborate what is the purpose of this database?
If we compare it to KVM support, the 'primary' location of VMs' metadata
is in libvirt internal store (outside of Nova), and then it is cached in
Nova DB, for Nova purposes.
A similar approach might make for bare-metal machines too -- keep
d approach.
====
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html |
https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
Email: glik...@il.ibm.com | Phone: +972-4-8281085 | Mobile:
+972-54-646
As stated below, the following patch addresses the VM recovery in this and
few other scenarios: https://review.openstack.org/#/c/11086/
Also, there is another patch which can be used to simplify failure
detection: https://review.openstack.org/#/c/10903/
Unfortunately, neither of the two made it f
Are there any additional details regarding the usage of workflows in
Horizon? http://docs.openstack.org/developer/horizon/ref/workflows.html
Is this something that can be also reused outside of Horizon, in the
broader context of workflows for OpenStack?
Thanks,
Alex
_
Was great to see many stackers at the summit!
Following-up on one of the design discussions, the consensus seemed to be
that the operation which puts a host in maintenance mode should probably
only disable further provisioning requests to that host, while the
orchestration of migrating the indivi
Alex Glikson
Manager, Cloud Operating System Technologies, IBM Haifa Research Lab
http://w3.haifa.ibm.com/dept/stt/cloud_sys.html |
http://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml
Email: glik...@il.ibm.com | Phone: +972-4-8281085 | Mobile:
+972-54-647 | Fax: +972-4
y
To: ch...@christopherbartels.com,
Cc: Alex Glikson/Haifa/IBM@IBMIL, openstack@lists.launchpad.net
Date: 01/06/2013 07:39 AM
Subject:Re: [Openstack] VM disk affinity during live migration
Hi Chris,
I think that you are using live migration without specifying target host,
One of the goals was to separate between instance placement calculation
logic and the orchestration logic, having each in a separate runtime (see
https://blueprints.launchpad.net/nova/+spec/query-scheduler). Scheduler
and conductor (respectively) seemed like a reasonable choice.
Regards,
Alex
Try "nova evacuate VM1 compute-node2 --on-shared-storage".
Regards,
Alex
From: Ray Sun
To: OpenStack Maillist ,
Date: 24/06/2013 07:04 AM
Subject:[Openstack] How can I recover my VM on a broken hardware?
Sent by:"Openstack"
I have three nodes, two of them is com
14 matches
Mail list logo
