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
From: Daniel P. Berrange berra...@redhat.com
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.
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
From: Ryan Lane rl...@wikimedia.org
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
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
.
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-647 | Fax: +972
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
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
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 xiaoq...@gmail.com
To: OpenStack Maillist openstack@lists.launchpad.net,
Date: 24/06/2013 07:04 AM
Subject:[Openstack] How can I recover my VM on a broken hardware?
Sent by:Openstack
11 matches
Mail list logo