Features/OpenStack using Qpid

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(move to OpenStack category)
 
(9 intermediate revisions by 3 users not shown)
Line 13: Line 13:
 
== Owner ==
 
== Owner ==
 
* Name: [[User:russellb| Russell Bryant]]
 
* Name: [[User:russellb| Russell Bryant]]
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: rbryant at redhat dot com
  
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/17 | Fedora 17 ]]  
 
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Last updated: 2011-12-20
+
* Last updated: 2012-01-09
* Percentage of completion: 15%
+
* Percentage of completion: 100%
  
 
<!-- 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 25: Line 25:
 
<!-- 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. -->
  
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.  Qpid supports some features, such as active-active clustering and federation of message brokers, that are not available with RabbitMQ.
+
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 ==
 
== Benefit to Fedora ==
Line 35: Line 35:
 
<!-- 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 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.
+
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 [https://fedoraproject.org/wiki/Features/OpenStack_Essex 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 ==
 
== How To Test ==
Line 51: Line 51:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
 +
# Install the <code>qpid-cpp-server</code> package.
 +
# Start the <code>qpidd</code> service.
 +
# Set <code>--rpc_backend=nova.rpc.impl_qpid</code> in <code>/etc/nova/nova.conf</code>
 +
# Use OpenStack nova as usual from there.  For example, one could follow the [https://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day test day test cases].
  
 
== 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. -->
 +
 +
The user experience will be the same.
  
 
== 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)? -->
 +
 +
None.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 65: Line 74:
 
== 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://blueprints.launchpad.net/nova/+spec/apache-qpid-rpc Upstream feature blueprint]
 
+
* The [https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova Getting Started with OpenStack Nova] page will be updated with information on how to use Qpid.
 
+
  
 
== Release Notes ==
 
== 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 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. -->
*
+
 
 +
* OpenStack: Support for using Qpid as the messaging backend for nova.
  
 
== 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/OpenStack_using_Qpid]]  <!-- 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 -->
  
  
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF17]]
 
<!-- 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 -->
 +
 +
[[Category:OpenStack]]

Latest revision as of 06:05, 25 April 2012


Contents

[edit] Feature Name

OpenStack using Qpid.

[edit] Summary

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

[edit] Owner

[edit] Current status

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


[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] User Experience

The user experience will be the same.

[edit] Dependencies

None.

[edit] 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.

[edit] Documentation

[edit] Release Notes

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

[edit] Comments and Discussion