qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DISPATCH-80) Management schema: implement annotations and entity inheritance as per AMQP management WD 09
Date Fri, 05 Dec 2014 15:16:13 GMT

     [ https://issues.apache.org/jira/browse/DISPATCH-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alan Conway resolved DISPATCH-80.
    Resolution: Fixed

> Management schema: implement annotations and entity inheritance as per AMQP management
WD 09
> --------------------------------------------------------------------------------------------
>                 Key: DISPATCH-80
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-80
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Management Agent
>    Affects Versions: 0.2
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.3
> The AMQP management draft 9 defines annotations, collections of attributes that can be
applied to entity type definitions. This is very much like the "include" entries in our existing
> To do:
> - Convert the existing "include" entries to conform to standard annotations.
> - Add inheritance between entity types
> - Introduce this simple hierarchy: 
> configurationEntity: base for all entities derived from the config file.
> operationalEntity: base for all entities queried by qdstat.
> "Configuration" information is supplied in advance and expresse intent. For
> example "I want the router to listen on port N", or, "I want the router to
> connect to this address" All the entities that can be used in the configuration
> file are "configurationEntity".
> "Operational" information reflects the actual state of the router at a given
> moment in time.  For example, "how many addresses are presently active on the
> router?" All the entities queried by qdstat are "operationalEntity".
> The two types are often related, for example "I want an on-demand connection to
> this address" and "is there presently a live outgoing connection to this
> address?"  As a matter of good practice we separate the two kinds of
> entities. For example "listener" and "connector" are configuration entities
> expressing the intent to make or receive connectoins. The "connection" entity
> holds live operational information about an actual connection.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message