Module fe2o3_amqp_management::operations::node
source · Expand description
A Management Node Operation is an operation directed to the Management Node itself rather than an entity it is managing. Of the standard application-properties (see Section 3.1), name MUST be provided with a value of “self”, type MUST be provided with a value of “org.amqp.management” and identity MUST NOT be provided. The following Management Node Operations SHOULD be supported: • QUERY • GET-TYPES • GET-ANNOTATIONS • GET-ATTRIBUTES • GET-OPERATIONS • GET-MGMT-NODES The following Management Node Operations MAY be supported: • REGISTER • DEREGISTER
Structs§
- DEREGISTER
- No information is carried in the message body therefore any message body is valid and MUST be ignored.
- GET-ANNOTATIONS
- Response to a GetAnnotations request.
- GET-ATTRIBUTES
- If the request was successful then the statusCode MUST be 200 (OK) and the body of the message MUST contain a map. The keys in the map MUST be the set of Manageable Entity Types for which attribute names are being provided. For any given key, the value MUST be a list of strings representing the attribute names that this Manageable Entity Type possesses. It should be noted that for each entry in the map, the attribute names returned MUST be only those defined by the associated Manageable Entity Type rather than those that are defined by other Manageable Entity Types that extend it. For any given Manageable Entity Type, the set of attribute names returned MUST include every attribute name defined by Manageable Entity Types that it extends, either directly or indirectly.
- GET-MGMT-NODES
- If the request was successful then the statusCode MUST be 200 (OK) and the body of the message MUST consist of an amqp-value section containing a list of addresses of other Management Nodes known by this Management Node (each element of the list thus being a string). If no other Management Nodes are known then the amqp-value section MUST contain a list of zero elements.
- GET-OPERATIONS
- If the request was successful then the statusCode MUST be 200 (OK) and the body of the message MUST consist of an amqp-value section containing a map. The keys in the map MUST be the set of Manageable Entity Types for which the list of Management Operations is being provided. For any given key, the value MUST itself be a map, where each key is the string name of a Management Operation that can be performed against this Manageable Entity Type via this Management Node, and the value for a given key is a list of strings giving the names of the arguments (passed via the application- properties of a request message) which the operation defines. For any given Manageable Entity Type, the set of operations returned MUST include every operation supported by Manageable Entity Types that it extends, either directly or indirectly.
- GET-TYPES
- The response to a GetTypes request.
- Retrieve selected attributes of Manageable Entities that can be read at this Management Node.
- Response to a Query request.
- REGISTER
- No information is carried in the message body therefore any message body is valid and MUST be ignored.
Traits§
- A trait for handling Deregister request on a Manageable Node.
- A trait for handling GetAnnotations request on a Manageable Node.
- A trait for handling GetAttributes request on a Manageable Node.
- A trait for handling GetMgmtNodes request on a Manageable Node.
- A trait for handling GetOperations request on a Manageable Node.
- A trait for handling GetTypes request on a Manageable Node.
- Management Node Operations
- A trait for handling Query request on a Manageable Node.
- A trait for handling Register request on a Manageable Node.