Ask Your Question

Revision history [back]

  • Roadmap: https://www.openstack.org/software/roadmap/ & live-updated feature implementation status: http://status.openstack.org/release/

Regarding "HA" - which is a topic that has many, many meanings, it sounds like most of what you want is implemeted at the hypervisor layer. For example, Hypervisors such as VMWare, Xen, KVM support live migration without trouble. If you want to do things like "re-start a VM on a different hypervisor if the physical host it was on fails", you can use shared storage and watch and re-act. It depends on your specific use case and hypervisor choice as to how you respond to the monitoring information provided. Similarly, load balancing can be dealt with by the scheduler on vm-creation time, or based on your reaction to monitoring information. OpenStack can't make the choices for you about when to move VMs between hypervisors, since every use-case is very, very different :)

  • Roadmap: https://www.openstack.org/software/roadmap/ & live-updated feature implementation status: http://status.openstack.org/release/

Regarding "HA" - which is a topic that has many, many meanings, it sounds like most of what you want is implemeted at the hypervisor layer. For example, Hypervisors such as VMWare, Xen, KVM support live migration without trouble. If you want to do things like "re-start a VM on a different hypervisor if the physical host it was on fails", you can use shared storage and watch and re-act. It depends on your specific use case and hypervisor choice as to how you respond to the monitoring information provided. Similarly, load balancing can be dealt with by the scheduler on vm-creation time, or based on your reaction to monitoring information. OpenStack can't make the choices for you about when to move VMs between hypervisors, since every use-case is very, very different :)

Having said this, you may be interested in the discussion around a new feature that could be enabled to perform some of these tasks - see the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015326.html

Great to hear the start of your OpenStack Journey has been positive :)

  • Roadmap: https://www.openstack.org/software/roadmap/ & live-updated feature implementation status: http://status.openstack.org/release/

Regarding "HA" - which is a topic that has many, many meanings, it sounds like most of what you want is implemeted at the hypervisor layer. For example, Hypervisors such as VMWare, Xen, KVM support live migration without trouble. If you want to do things like "re-start a VM on a different hypervisor if the physical host it was on fails", you can use shared storage and watch and re-act. It depends on your specific use case and hypervisor choice as to how you respond to the monitoring information provided. Similarly, load balancing can be dealt with by the scheduler on vm-creation time, or based on your reaction to monitoring information. OpenStack can't make the choices for you about when to move VMs between hypervisors, since every use-case is very, very different :)

Having said this, you may be interested in the discussion around a new feature that could be enabled to perform some of these tasks - see the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015326.html

Great to hear the start of your OpenStack Journey has been positive :)

  • Roadmap: https://www.openstack.org/software/roadmap/ & live-updated feature implementation status: http://status.openstack.org/release/

Regarding "HA" - which is a topic that has many, many meanings, it sounds like most of what you want is implemeted at the hypervisor layer. For example, Hypervisors such as VMWare, Xen, KVM support live migration without trouble. trouble and the OpenStack API can be used to trigger this. If you want to do things like "re-start a VM on a different hypervisor if the physical host it was on fails", you can use shared storage and watch and re-act. It depends on your specific use case and hypervisor choice as to how you respond to the monitoring information provided. Similarly, load balancing can be dealt with by the scheduler on vm-creation time, or based on your reaction to monitoring information. OpenStack can't make the choices for you about when to move VMs between hypervisors, since every use-case is very, very different :)

Having said this, you may be interested in the discussion around a new feature that could be enabled to perform some of these tasks - see the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015326.html