Features/High Availability Container Resources

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m
m
Line 18: Line 18:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/19 | Fedora 19 ]]  
* Last updated: (DATE)
+
* Last updated: 1-25-2013
* Percentage of completion: XX%
+
* Percentage of completion: 60%
  
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
Line 26: Line 26:
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 +
This feature is in response to the growing desire for high availability functionality to be extended outside of the host into virtual guest instances.  Pacemaker is currently capable of managing virtual guests, meaning Pacemaker can start/stop/monitor/migrate virtual guests around the cluster, but Pacemaker has no ability to manage the resources that live within the virtual guests.  At the moment these virtual guests are very much a black box to Pacemaker.
 +
 +
The Container Resources concept changes this by giving Pacemaker the ability to reach into the virtual guests and manage resources in the exact same way resources are managed on the host nodes. Ultimately this gives the HA stack the ability to manage resources across all the nodes in cluster as well as any virtual guests that reside on those cluster nodes.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==

Revision as of 18:33, 25 January 2013


Contents

High Availability Container Resources

Summary

The Container Resources feature allows the HA stack (Pacemaker + Corosync) residing on a host machine to extend management of resources into virtual guest instances (KVM/LXC).

Owner

  • Email: <dvossel@redhat.com>

Current status

  • Targeted release: Fedora 19
  • Last updated: 1-25-2013
  • Percentage of completion: 60%


Detailed Description

This feature is in response to the growing desire for high availability functionality to be extended outside of the host into virtual guest instances. Pacemaker is currently capable of managing virtual guests, meaning Pacemaker can start/stop/monitor/migrate virtual guests around the cluster, but Pacemaker has no ability to manage the resources that live within the virtual guests. At the moment these virtual guests are very much a black box to Pacemaker.

The Container Resources concept changes this by giving Pacemaker the ability to reach into the virtual guests and manage resources in the exact same way resources are managed on the host nodes. Ultimately this gives the HA stack the ability to manage resources across all the nodes in cluster as well as any virtual guests that reside on those cluster nodes.

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion