Features/OpenStack using Qpid

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(add to clod)
Line 92: Line 92:
 
<!-- 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 -->
 +
 +
[[Category:Cloud SIG]]

Revision as of 16:22, 12 January 2012


Contents

Feature Name

OpenStack using Qpid.

Summary

Provide an alternative to using RabbitMQ as the AMQP backend for an OpenStack deployment. This requires a new module inside of OpenStack nova.

Owner

Current status

  • Targeted release: Fedora 17
  • Last updated: 2012-01-09
  • Percentage of completion: 80%


Detailed Description

OpenStack deployments currently use RabbitMQ as the AMQP backend for messaging between OpenStack nova services on different nodes. This feature will allow the use of Qpid as an alternative.

Benefit to Fedora

With this feature in place, OpenStack administrators have more choice about what infrastructure they would like to put in place for their cloud.

Scope

This is primarily an upstream development effort. We must develop a new module that will be incorporated into OpenStack nova to support using Qpid. We aim to get this completed and integrated into the OpenStack Essex release. At that point we will just need to make sure that the new module is properly packaged and is compatible with the version of Qpid in Fedora.

How To Test

  1. Install the qpid-cpp-server package.
  2. Start the qpidd service.
  3. Set --rpc_backend=nova.rpc.impl_qpid in /etc/nova/nova.conf
  4. Use OpenStack nova as usual from there. For example, one could follow the test day test cases.

User Experience

The user experience will be the same.

Dependencies

None.

Contingency Plan

If this feature is not completed in time, it will get pulled and bumped to the next release. No other feature depends on this one.

Documentation

Release Notes

  • OpenStack: Support for using Qpid as the messaging backend for nova.

Comments and Discussion