Dashboard > AMQP Public Site > ... > In Progress > Management SIG

View Info

Management SIG

Charter & Scope

Motivation

It is anticipated that AMQP will grow to global scales of deployment. AMQP will become a critical part of doing business, and consequently the users of it will need to be able to monitor AMQP and manage AMQP deployments within their environment, potentially across several different AMQP implementations.

In order that management does not itself become an avenue for vendor lock-in of the messaging solution, the Management SIG will standardise the critical elements of AMQP's management capabilities.

Objectives

The purpose of the Management SIG is to:

  1. Specify the operational and management console services which MUST, SHOULD or MAY be expected of any AMQP compliant message broker
  2. Define the logical architecture for how AMQP is managed
  3. Document a concrete protocol and management command interface which compliant AMQP brokers must implement   

SIG Membership

  • John O'Hara (JPMC)
  • Mark Blair (Credit Suisse) -- Project Lead
  • Ted Ross(Red Hat)
  • Pieter Hintjens (iMatix)
  • Robert Godfrey (JPMC)

SIG Mailing List

  • Mailing List ==>  amqp-management-sig@lists.amqp.org
  • Click here to join this mailing list
  • Click here to send a message to this mailing list

SIG Weekly Meeting

   

Scope and Schedule

  • The Management work can be considered orthogonal to the main specification work stream, consequently, management can evolve at its own schedule, and may not be tied to the main specification releases.
  • It is anticipated due to the broad extent of Management that the protocol will be delivered in segments over the next 2 - 3 specification releases.

Phase Deliverables

First Phase * Definition of the use cases and requirements
* Definition of the architectural model for management
* Analysis and selection of a transport protocol (or protocols) for management
* Definition of a set of logical data models for broker query and command execution
* Definition of a mapping from the logical data model to the physical wire format,
   and mapping to transport
Second Phase * Definition of a logical data model for management eventing
* Definition of mappings to other management protocols (e.g. SNMP, JMX, etc)
Third Phase * Definition of a logical data model for management watchlists

All Children:



Browse Space
- Pages
- Labels
- Attachments
- Mail
- News
- Activity
- Advanced

Explore Confluence
- Popular Labels
- Notation Guide

Your Account
Log In

Other Features

View a printable version of the current page.

Add Content


Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007)
Bug/feature request - Contact Administrators