Features/pacemaker-cloud

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Created page with '{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...')
 
(initial development of feature page)
Line 11: Line 11:
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
  
= Feature Name <!-- The name of your feature --> =
+
= pacemaker-cloud <!-- The name of your feature --> =
  
 
== Summary ==
 
== Summary ==
 +
The pacemaker-cloud project demonstrates the current community work in providing application service high availability in a cloud environment.
 +
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
 
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
  
 
== Owner ==
 
== Owner ==
 
<!--This should link to your home wiki page so we know who you are-->
 
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:FASAcountName| Your Name]]
+
* Name: [[User:sdake| Steven Dake]]
  
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: <sdake@redhat.com>
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/16 | Fedora 16 ]]  
* Last updated: (DATE)
+
* Last updated: (May 26, 2011)
* Percentage of completion: XX%
+
* Percentage of completion: 20%
  
 
<!-- 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 32: Line 34:
 
== 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. -->
 +
The software provides a cli which allows:
 +
Create a VM from a template.
 +
Launch deployable on local machine.
 +
Kill/restart applications if failure detected.
 +
Kill/restart assembly if failure detected.
 +
Kill/restart deployable if failure detected.
 +
Notification of failures of any of the objects in the system.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
+
This brings high availability of the deployable/assembly VM model to the system single node.  In future versions we intend to integrate with other cloud management systems.
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
This is a standalone package but has several dependencies on other parts of Fedora 16.
  
 
== How To Test ==
 
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
+
Binaries have not been named, as such this section is TODO.
  
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
+
yum install pacemaker-cloud
 
+
Launch the cli shell
A good "how to test" should answer these four questions:
+
create deployables via the cli shell
 
+
Launch deployables via the cli shell
0. What special hardware / data / etc. is needed (if any)?
+
Kill individual applications and expect the cli to print the application failure.
1. How do I prepare my system to test this feature? What packages
+
Kill individual assemblies and expect the cli to print the assembly failure.
need to be installed, config files edited, etc.?
+
After an application is killed, validate that the application is restarted.
2. What specific actions do I perform to check that the feature is
+
After an assembly is killed, validate that the assembly and it's applications are running again.
working like it's supposed to?
+
3. What are the expected results of those actions?
+
-->
+
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
There are no user experience changes.
  
 
== Dependencies ==
 
== Dependencies ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 +
Previously packaged in Fedora rawhide:
 +
glib2
 +
dbus-glib
 +
libxml2
 +
libqb
 +
pacemaker-libs
 +
qmf
 +
libxslt
 +
 +
Needs packaging in Fedora rawhide:
 +
oz
  
 
== Contingency Plan ==
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 +
If this feature is not ready by deadline, it can moved to a later Fedora version.
  
 
== Documentation ==
 
== Documentation ==
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
+
 
 +
https://github.com/pacemaker-cloud/pacemaker-cloud
  
 
== Release Notes ==
 
== Release Notes ==
Line 73: Line 94:
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Features/pacemaker-cloud]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
  
  

Revision as of 22:35, 26 May 2011

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Contents

pacemaker-cloud

Summary

The pacemaker-cloud project demonstrates the current community work in providing application service high availability in a cloud environment.


Owner

  • Email: <sdake@redhat.com>

Current status

  • Targeted release: Fedora 16
  • Last updated: (May 26, 2011)
  • Percentage of completion: 20%


Detailed Description

The software provides a cli which allows: Create a VM from a template. Launch deployable on local machine. Kill/restart applications if failure detected. Kill/restart assembly if failure detected. Kill/restart deployable if failure detected. Notification of failures of any of the objects in the system.

Benefit to Fedora

This brings high availability of the deployable/assembly VM model to the system single node. In future versions we intend to integrate with other cloud management systems.

Scope

This is a standalone package but has several dependencies on other parts of Fedora 16.

How To Test

Binaries have not been named, as such this section is TODO.

yum install pacemaker-cloud Launch the cli shell create deployables via the cli shell Launch deployables via the cli shell Kill individual applications and expect the cli to print the application failure. Kill individual assemblies and expect the cli to print the assembly failure. After an application is killed, validate that the application is restarted. After an assembly is killed, validate that the assembly and it's applications are running again.

User Experience

There are no user experience changes.

Dependencies

Previously packaged in Fedora rawhide: glib2 dbus-glib libxml2 libqb pacemaker-libs qmf libxslt

Needs packaging in Fedora rawhide: oz

Contingency Plan

If this feature is not ready by deadline, it can moved to a later Fedora version.

Documentation

https://github.com/pacemaker-cloud/pacemaker-cloud

Release Notes

Comments and Discussion