{{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 read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}

−

−

{{admon/important | 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}}

−

−

{{admon/note | All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed }}

−

−

<!-- All fields on this form are required to be accepted by FESCo.

<!-- All fields on this form are required to be accepted by FESCo.

We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

We have a test suite that can be run which provides automated validation the software functions properly.

We have a test suite that can be run which provides automated validation the software functions properly.

Manually the following operations can be done:

Manually the following operations can be done:

−

<code>

+

<pre>

root# pcloudsh

root# pcloudsh

pcloudsh# jeos_create F14 x86_64

pcloudsh# jeos_create F14 x86_64

Line 82:

Line 79:

pcloudsh# assembly_clone assy1 assy2

pcloudsh# assembly_clone assy1 assy2

pcloudsh# assembly_clone assy1 assy3

pcloudsh# assembly_clone assy1 assy3

−

pcloudsh# assembly_resource_add httpd httpd assy1

+

pcloudsh# assembly_resource_add httpdone httpd assy1

−

pcloudsh# assembly_resource_add httpd httpd assy2

+

pcloudsh# assembly_resource_add httpdtwo httpd assy2

−

pcloudsh# assembly_resource_add httpd httpd assy3

+

pcloudsh# assembly_resource_add httpdthree httpd assy3

pcloudsh# deployable_create dep1

pcloudsh# deployable_create dep1

pcloudsh# deployable_assembly_add dep1 assy1

pcloudsh# deployable_assembly_add dep1 assy1

Line 90:

Line 87:

pcloudsh# deployable_assembly_add dep1 assy3

pcloudsh# deployable_assembly_add dep1 assy3

pcloudsh# deployable_start dep1

pcloudsh# deployable_start dep1

−

</code>

+

</pre>

+

Keep pcloudsh running and in another shell:

Keep pcloudsh running and in another shell:

Line 112:

Line 110:

<!-- 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:

Previously packaged in Fedora rawhide:

+

<pre>

glib2

glib2

dbus-glib

dbus-glib

libxml2

libxml2

+

libuuid

libqb

libqb

−

pacemaker-libs and its many dependencies

+

pacemaker-libs

qmf

qmf

libxslt

libxslt

qpid-cpp-server

qpid-cpp-server

qpid-cpp-client

qpid-cpp-client

−

python-qpid-qmf

+

python-qmf

−

+

matahari-service

−

Needs packaging in Fedora rawhide:

+

matahari-host

−

oz (currently under review)

+

libqb

+

oz

+

systemd

+

</pre>

Dependency with broken functionality:

Dependency with broken functionality:

−

systemd - systemd guests don't work properly because systemd is not LSB compliant. F14 and RHEL6 guests will work properly, but without bug fixing in systemd, F15 and F16 are nonfunctional.

+

systemd - systemd guests don't work properly because systemd is not LSB compliant. A patch to resolve this issue has been merged upstream and tested working with the current pacemaker-cloud code in a f15 JEOS + upstream patch on top of latest rawhide systemd rpm.

== 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.

+

If this feature is not ready by July 26, it can moved to a later Fedora version. If systemd is not LSB compliant by July 26, appropriate release notes should indicate that systemd is in the progress of updating its build with upstream packages. More then likely this will just be fixed as part of f16 release of systemd.

== 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. -->

<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->

<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->

<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->

<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->

−

Guests using systemd are non-funtional with this feature and that fact may need release notes as to not confuse the audience.

+

+

Pacemaker-Cloud provides high availability for application services inside virtual machines on a single node. This feature provides a shell for creating virtual machine images, associating resources with the virtual machines, and combining these images into a deployable. A deployable can then be launched and monitored for high availability. If virtual machines or applications fail, these components will be restarted reducing MTTR (mean time to repair) improving availability over manual operator restart.

+

+

Fedora ''guest virtual machines using systemd'' are currently non-functional until the following bugzilla is merged into rawhide: See [https://bugzilla.redhat.com/show_bug.cgi?id=702621 systemd defect 702621] discussion.

== Comments and Discussion ==

== Comments and Discussion ==

Line 147:

Line 157:

−

[[Category:FeaturePageIncomplete]]

+

[[Category:FeatureAcceptedF16]]

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->

<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->

<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

This feature provides a preview of high availability for cloud environments using a building block that is reusable in other cloud management systems. This feature provides only single node deployable high availability, but for F17 we plan to integrate with other distributed cloud management tools such as Aeolus.

This is a standalone package but has several dependencies on other parts of Fedora 16. We are in good shape relatng to dependencies, however, systemd is not LSB compliant currently resulting in our software not being able to provide high availability for F15 or Rawhide guests.

We are nearing code completion for the single node case and have some basic packaging done.

Dependency with broken functionality:
systemd - systemd guests don't work properly because systemd is not LSB compliant. A patch to resolve this issue has been merged upstream and tested working with the current pacemaker-cloud code in a f15 JEOS + upstream patch on top of latest rawhide systemd rpm.

If this feature is not ready by July 26, it can moved to a later Fedora version. If systemd is not LSB compliant by July 26, appropriate release notes should indicate that systemd is in the progress of updating its build with upstream packages. More then likely this will just be fixed as part of f16 release of systemd.

Pacemaker-Cloud provides high availability for application services inside virtual machines on a single node. This feature provides a shell for creating virtual machine images, associating resources with the virtual machines, and combining these images into a deployable. A deployable can then be launched and monitored for high availability. If virtual machines or applications fail, these components will be restarted reducing MTTR (mean time to repair) improving availability over manual operator restart.

Fedora guest virtual machines using systemd are currently non-functional until the following bugzilla is merged into rawhide: See systemd defect 702621 discussion.