You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by tr...@apache.org on 2013/10/22 23:43:03 UTC
svn commit: r1534810 - in /qpid/site:
docs/components/dispatch-router/amqp-mapping.html
input/components/dispatch-router/amqp-mapping.md
Author: tross
Date: Tue Oct 22 21:43:02 2013
New Revision: 1534810
URL: http://svn.apache.org/r1534810
Log:
QPID-5001 - Added content about Qpid Dispatch compliance with the AMQP Management specification.
Modified:
qpid/site/docs/components/dispatch-router/amqp-mapping.html
qpid/site/input/components/dispatch-router/amqp-mapping.md
Modified: qpid/site/docs/components/dispatch-router/amqp-mapping.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch-router/amqp-mapping.html?rev=1534810&r1=1534809&r2=1534810&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch-router/amqp-mapping.html (original)
+++ qpid/site/docs/components/dispatch-router/amqp-mapping.html Tue Oct 22 21:43:02 2013
@@ -105,6 +105,53 @@ the details of Dispatch Router's use of
</tbody>
</table>
+<h2 id="implementation-of-the-amqp-management-specification">Implementation of the AMQP Management Specification</h2>
+
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant to a limited degree with the emerging AMQP Management specification. This section provides the details of what is supported and what is not and what is planned and what is not.</p>
+
+<p>Non-compliance occurs for one of the following reasons:</p>
+
+<ul>
+<li>Implementation of an optional feature is not planned</li>
+<li>Implementation is not complete as of the current time</li>
+<li>The specified operation is considered suboptimal or unimplementable. In all of these cases, an issue is pending with the AMQP Technical Committee.</li>
+</ul>
+
+<h3 id="compliance-matrix">Compliance Matrix</h3>
+
+<table>
+<tbody>
+<tr><td><em>Operation/Feature</em></td><td><em>Requirement</em></td><td><em>Supported</em></td><td><em>Remarks</em></td></tr>
+<tr><td>CREATE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>READ</td><td>Should</td><td>No</td><td>Not yet implemented</td></tr>
+<tr><td>UPDATE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>DELETE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>READALL</td><td>Should</td><td>No</td><td>A non-standard version of this operation is supported that retrieves data from all entities of a type. There is an outstanding issue raised with the AMQP Technical Committee to address this requirement.</td></tr>
+<tr><td>DISCOVER-NAMES</td><td>Should</td><td>No</td><td>Not yet implemented</td></tr>
+<tr><td>DISCOVER-TYPES</td><td>Should</td><td>Yes</td><td>There are no types that implement base types</td></tr>
+<tr><td>DISCOVER-OPERATIONS</td><td>Should</td><td>Yes</td><td></td></tr>
+<tr><td>DISCOVER-MGMT-NODES</td><td>Should</td><td>Yes</td><td>This operation yields the addresses of all of the router nodes in the known network</td></tr>
+<tr><td>REGISTER</td><td>May</td><td>Not Planned</td><td>The router has a specific way to discover peers that does not involve these operations</td></tr>
+<tr><td>DEREGISTER</td><td>May</td><td>Not Planned</td><td>The router has a specific way to discover peers that does not involve these operations</td></tr>
+</tbody>
+</table>
+
+<h3 id="manageable-entities">Manageable Entities</h3>
+
+<table>
+<tbody>
+<tr><td><em>Type Name</em></td><td><em>Description</em></td></tr>
+<tr><td>org.apache.qpid.dispatch.allocator</td><td>Per-type memory allocation statistics</td></tr>
+<tr><td>org.apache.qpid.dispatch.container</td><td>General state and statistics for the AMQP container</td></tr>
+<tr><td>org.apache.qpid.dispatch.container.node_type</td><td>Description of registered node types</td></tr>
+<tr><td>org.apache.qpid.dispatch.container.node</td><td>Description of registered nodes in the container</td></tr>
+<tr><td>org.apache.qpid.dispatch.router</td><td>General state and statistics for the router node</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.link</td><td>Per-link state and statistics for links attached to the router node</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.node</td><td>Per-node state and statistics for remote router nodes in the known network</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.address</td><td>Per-address state and statistics for addresses known to this router</td></tr>
+</tbody>
+</table>
+
</div>
<div id="bottom">
<ul id="apache-navigation">
Modified: qpid/site/input/components/dispatch-router/amqp-mapping.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch-router/amqp-mapping.md?rev=1534810&r1=1534809&r2=1534810&view=diff
==============================================================================
--- qpid/site/input/components/dispatch-router/amqp-mapping.md (original)
+++ qpid/site/input/components/dispatch-router/amqp-mapping.md Tue Oct 22 21:43:02 2013
@@ -61,3 +61,40 @@ The following AMQP addresses and address
|| /_local/qdxhello || The router entity in each of the connected routers. This address is used to communicate with neighbor routers and is exclusively for the HELLO discovery protocol. ||
|| /_local/qdxrouter || The router entity in each of the connected routers. This address is used by a router to communicate with other routers in the network. ||
|| <span style="white-space: nowrap;">/_topo/A2/Router.E/qdxrouter</span> || The router entity at the specifically indicated router. This address form is used by a router to communicate with a specific router that may or may not be a neighbor. ||
+
+## Implementation of the AMQP Management Specification
+
+Qpid Dispatch is manageable remotely via AMQP. It is compliant to a limited degree with the emerging AMQP Management specification. This section provides the details of what is supported and what is not and what is planned and what is not.
+
+Non-compliance occurs for one of the following reasons:
+
+ - Implementation of an optional feature is not planned
+ - Implementation is not complete as of the current time
+ - The specified operation is considered suboptimal or unimplementable. In all of these cases, an issue is pending with the AMQP Technical Committee.
+
+### Compliance Matrix
+
+ || *Operation/Feature* || *Requirement* || *Supported* || *Remarks* ||
+ || CREATE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || READ || Should || No || Not yet implemented ||
+ || UPDATE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || DELETE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || READALL || Should || No || A non-standard version of this operation is supported that retrieves data from all entities of a type. There is an outstanding issue raised with the AMQP Technical Committee to address this requirement. ||
+ || DISCOVER-NAMES || Should || No || Not yet implemented ||
+ || DISCOVER-TYPES || Should || Yes || There are no types that implement base types ||
+ || DISCOVER-OPERATIONS || Should || Yes || ||
+ || DISCOVER-MGMT-NODES || Should || Yes || This operation yields the addresses of all of the router nodes in the known network ||
+ || REGISTER || May || Not Planned || The router has a specific way to discover peers that does not involve these operations ||
+ || DEREGISTER || May || Not Planned || The router has a specific way to discover peers that does not involve these operations ||
+
+### Manageable Entities
+
+ || *Type Name* || *Description* ||
+ || org.apache.qpid.dispatch.allocator || Per-type memory allocation statistics ||
+ || org.apache.qpid.dispatch.container || General state and statistics for the AMQP container ||
+ || org.apache.qpid.dispatch.container.node_type || Description of registered node types ||
+ || org.apache.qpid.dispatch.container.node || Description of registered nodes in the container ||
+ || org.apache.qpid.dispatch.router || General state and statistics for the router node ||
+ || org.apache.qpid.dispatch.router.link || Per-link state and statistics for links attached to the router node ||
+ || org.apache.qpid.dispatch.router.node || Per-node state and statistics for remote router nodes in the known network ||
+ || org.apache.qpid.dispatch.router.address || Per-address state and statistics for addresses known to this router ||
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org