amqp — archive

AMQP Management Workstream

From: Jakub Scholz <[email protected]>
To: [email protected]
Date: Mon, 20 May 2013 16:03:00 -0000

Hi Rob, Thanks for preparing the first draft and for organizing the conference calls. Bellow are my questions / review comments to the document ... 1) According to 2.4, "This specification does not define the collection of supported Manageable Entity Types". Where will they be defined? I assume the entities org.amqp.* mentioned in 2.2 should be defined somewhere by the AMQP TCs. Together with the list of the entities, we might also include some recommended attribute names to avoid incompatibilities between implementations even for a basic stuff. 2) According to 3.3, the management node should respond with a message containing a body with a map of the actual attributes. These attributed may differ from those required. Does it mean that the management node can change any attribute as it wants and still return success? What should be the main benefit of giving such freedom to the management node? 3) What is the expected response if some of the operations in chapter 3 are not supported for certain manageable entities? 501 Not Implemented? 4) For all defined operations, we say that the response must be empty in case the request was unsuccessful. Shouldn't this be also part of the chapter 3.2 to enforce this rule also on any custom operations the builders may implement? 5) As already mentioned by Rafael, some sort of handling for large data sets for READALL and DISCOVER operations might be very useful 6) What is the difference between "All manageable entities" and "all ManageableEntities on which Management Operations can be performed"? (READALL versus DISCOVER) How should these terms be interpreted when the management node has some security layer which allows different users manage different entities / use only some selected operations? 7) The READALL and DISCOVER operations are partially overlapping. Maybe we can move the first part of the DISCOVER functionality - "(a) the list of ManageableEntities on which Management Operations can be performed" - as one of the filtering possibilities for READALL. 8) While the description of the DESCOVER-MGMT-NODES, REGISTER and DEREGISTER operations is quite clear, I'm missing some kind of explanation what is their purpose. 9) The document describes only request/response processing. Is there some reasons why we do not want some sort of management broadcasts? Thanks & Regards Jakub ---------------------------------------------------------------------------- Deutsche Börse Services s.r.o. Managing Directors/Geschäftsführung: Michael Gassmann, Mats Andersson. Limited liability company with registered office at Sokolovská 662/136B, CZ-186 00 Prague 8 recorded in the Commercial Register IC: 275 77 015. Maintained by the city court in Prague, Sec. C, File No. 116874. --------------------------- + --------------------------------------------------------------------------------------------------------- > "Rob Dolin (MS OPEN TECH)" <[email protected]> Sent by: To <[email protected]> "[email protected]" <[email protected]> cc "[email protected]" <[email protected]> 17/05/2013 15:52 Subject RE: [amqp] RE: AMQP Management Workstream --------------------------- + --------------------------------------------------------------------------------------------------------- > > --------------------------- > --------------------------- THANK YOU very much Rafael for your thoughtful comments. I'm going to work on addressing / incorporating them into a Doc using track changes and will schedule a ConCall with shared screen for review next week. Please let me know if you have any conflicts with the following days/times: * Tue, 11am Eastern / 8am Pacific * Tue, 1pm Eastern / 10am Pacific * Wed, 11am Eastern / 8am Pacific If others have comments, please also share on the list. Thanks very much-- --Rob D. P.S. Once the call is scheduled, I'll send the info to the AMQP TC so folks who are interested in participating can join.