From Fedora Project Wiki
< Features
| (42 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
<!-- 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 --> | ||
= | = AMQP Infrastructure = | ||
<!-- The name of your feature --> | <!-- The name of your feature --> | ||
| Line 10: | Line 10: | ||
<!-- A or sentence summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A or sentence summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
AMQP Infrastructure (AMQPI) is a technology that makes it easy to build scalable, interoperable, high-performance enterprise applications. | |||
AMQPI is based on version 0-10 of [http://amqp.org AMQP] or Advanced Message Queuing Protocol. | |||
== Owner == | == Owner == | ||
<!--This should like to your home wiki page. Your home wiki page should include an email address that you can be reached at should people want to contact you about helping with your feature or to request status --> | <!--This should like to your home wiki page. Your home wiki page should include an email address that you can be reached at should people want to contact you about helping with your feature or to request status --> | ||
* Name: [[User: | * Name: [[User:Tross| Ted Ross]] | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/10| Fedora 10 ]] | ||
* Last updated: | * Last updated: September 11, 2008 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
* There is a web-based console application for AMQPI that has not yet been packaged for Fedora. However, AMQPI is fully functional as it currently exists. | |||
<!-- 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. --> | ||
== 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 consists of an AMQP (protocol version 0-10) messaging broker/server, client bindings for C++, Python, and Ruby, and a set of cli configuration/management utilities. | |||
Also included is a high-performance asynchronous message store for durable messages and messaging configuration. | |||
== 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?--> | ||
AMQP Infrastructure provides an enterprise-class messaging infrastructure that supports multiple programming languages and provides interoperability among those languages. | |||
AMQP Infrastructure is made up of the following packages, which may be installed using "yum install": | |||
* qpidc | |||
* amqp | |||
* rhm | |||
* python-qpid | |||
* ruby-qpid | |||
== 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?--> | ||
AMQP Infrastructure is complete and has been uploaded to the Rawhide distribution as ".fc10" rpms. | |||
== Test Plan == | == Test Plan == | ||
| Line 48: | Line 62: | ||
--> | --> | ||
Red Hat Messaging should be tested on i386 and x86_64 architectures. | |||
There is an examples RPM (rhm-examples) that provides a comprehensive set of runnable examples (in all supported languages). The set of examples and scripts to run them in various combinations provides the basis for a good feature test. | |||
== 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. --> | ||
This is an infrastructure/middleware feature. It is not visible to users but provides powerful communication facilities to developers. | |||
== 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 == | ||
<!-- 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. --> | ||
None necessary. This feature is not critical to other features in Fedora. | |||
== 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. --> | ||
Documentation for AMQP Infrastructure can be found at [http://www.redhat.com/mrg/resources http://www.redhat.com/mrg/resources] | |||
== Release Notes == | == Release Notes == | ||
| Line 66: | Line 86: | ||
<!-- 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. --> | ||
The most recent [http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.0/html/Release_Notes release notes] for Red Hat Enterprise MRG, the commercial product that is a superset of AMQP Infrastructure. | |||
Note that AMQP Infrastructure contains the messaging components of Red Hat Enterprise MRG. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/AMQP Infrastructure]] <!-- 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: | [[Category:FeatureAcceptedF10]] | ||
<!-- 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 --> | ||
Latest revision as of 23:29, 2 December 2008
AMQP Infrastructure
Summary
AMQP Infrastructure (AMQPI) is a technology that makes it easy to build scalable, interoperable, high-performance enterprise applications.
AMQPI is based on version 0-10 of AMQP or Advanced Message Queuing Protocol.
Owner
- Name: Ted Ross
Current status
- Targeted release: Fedora 10
- Last updated: September 11, 2008
- Percentage of completion: 100%
- There is a web-based console application for AMQPI that has not yet been packaged for Fedora. However, AMQPI is fully functional as it currently exists.
Detailed Description
This feature consists of an AMQP (protocol version 0-10) messaging broker/server, client bindings for C++, Python, and Ruby, and a set of cli configuration/management utilities.
Also included is a high-performance asynchronous message store for durable messages and messaging configuration.
Benefit to Fedora
AMQP Infrastructure provides an enterprise-class messaging infrastructure that supports multiple programming languages and provides interoperability among those languages.
AMQP Infrastructure is made up of the following packages, which may be installed using "yum install":
- qpidc
- amqp
- rhm
- python-qpid
- ruby-qpid
Scope
AMQP Infrastructure is complete and has been uploaded to the Rawhide distribution as ".fc10" rpms.
Test Plan
Red Hat Messaging should be tested on i386 and x86_64 architectures.
There is an examples RPM (rhm-examples) that provides a comprehensive set of runnable examples (in all supported languages). The set of examples and scripts to run them in various combinations provides the basis for a good feature test.
User Experience
This is an infrastructure/middleware feature. It is not visible to users but provides powerful communication facilities to developers.
Dependencies
None
Contingency Plan
None necessary. This feature is not critical to other features in Fedora.
Documentation
Documentation for AMQP Infrastructure can be found at http://www.redhat.com/mrg/resources
Release Notes
The most recent release notes for Red Hat Enterprise MRG, the commercial product that is a superset of AMQP Infrastructure.
Note that AMQP Infrastructure contains the messaging components of Red Hat Enterprise MRG.
Comments and Discussion