After communication initialization is complete, Oracle VM Server for SPARC-defined XML messages are sent next. The two general types of XML messages are:
Request and response messages, which use the <LDM_interface> tag. This type of XML message is used for communicating commands and getting results back from the Logical Domains Manager, analogous to executing commands using the command-line interface (CLI). This tag is also used for event registration and unregistration.
Event messages, which use the <LDM_event> tag. This type of XML message is used to asynchronously report events posted by the Logical Domains Manager.
The XML interface into Oracle VM Server for SPARC has two different formats:
A format for sending commands into the Logical Domains Manager
A format for Logical Domains Manager to respond on the status of the incoming message and the actions requested within that message.
The two formats share many common XML structures, but they are separated in this discussion for a better understanding of the differences between them.
An incoming XML request to the Logical Domains Manager at its most basic level includes a description of a single command operating on a single object. More complicated requests can handle multiple commands and multiple objects per command. The following example shows the structure of a basic XML command.
Example 5 Format of a Single Command Operating on a Single Object<LDM_interface version="1.7"> <cmd> <action>Place command here</action> <options>Place options for certain commands here</options> <arguments>Place arguments for certain commands here</arguments> <data version="3.0"> <Envelope> <References/> <!-- Note a <Section> section can be here instead of <Content> <Content xsi:type="ovf:VirtualSystem_Type" id="Domain name"> <Section xsi:type="ovf:ResourceAllocationSection_type"> <Item> <rasd:OtherResourceType>LDom Resource Type</rasd:OtherResourceType> <gprop:GenericProperty key="Property name">Property Value</gprop:GenericProperty> </Item> </Section> </Content> </Envelope> </data> </cmd> </LDM_interface>
All commands sent to the Logical Domains Manager must start with the <LDM_interface> tag. Any document sent into the Logical Domains Manager must have only one <LDM_interface> tag contained within it. The <LDM_interface> tag must include a version attribute as shown in Example 5, Format of a Single Command Operating on a Single Object.
Within the <LDM_interface> tag, the document must include at least one <cmd> tag. Each <cmd> section must have only one <action> tag. Use the <action> tag to describe the command to run. Each <cmd> tag must include at least one <data> tag to describe the objects on which the command is to operate.
The <cmd> tag can also have an <options> tag, which is used for options and flags that are associated with some commands. The following commands use options:
The ldm add-spconfig command can use the –r autosave-name option.
The ldm add-vdsdev command can use the –f option.
The ldm bind-domain command can use the –f option.
The ldm cancel-operation command can use the migration or reconf option.
The ldm list-bindings command can use the –e option.
The ldm list-dependencies command can use the –r option.
The ldm list-devices command can use the –B option.
The ldm list-domain command can use the –e option.
The ldm list-io command can use the –l option.
The ldm list-netdev command can use the –b option and the –l option.
The ldm list-rsrc-group command can use the –a option.
The ldm list-spconfig command can use the –r [autosave-name] option.
The ldm remove-domain command can use the –a option.
The ldm remove-spconfig command can use the –r option.
The ldm stop-domain command can use the following tags to set the command arguments:
<force> represents the –f option.
<halt> represents the –h option.
<message> represents the –m option.
<quick> represents the –q option.
<reboot> represents the –r option.
<timeout> represents the –t option.
Note that the tags must not have any content value. However, the –t and –m options must have a non-null value, for example, <timeout>10</timeout> or <message>Shutting down now</message>.
The following XML example fragment shows how to use the <options> tag to pass the –l option to the ldm list-io command to generate a long listing:
<cmd>
<action>list-io</action>
<options>-l</options>
<data version="3.0">
</data>
</cmd>
The following XML example fragment shows how to use the <arguments> tag to pass a reboot request with a reboot message to the ldm stop-domain command:
<action>stop-domain</action>
<arguments>
<reboot/>
<message>my reboot message</message>
</arguments>
Each <data> section contains a description of an object pertinent to the command specified. The format of the <data> section is based on the XML schema portion of the Open Virtualization Format (OVF) draft specification. That schema defines an <Envelope> section which contains a <References> tag (unused by Oracle VM Server for SPARC) and <Content> and <Section> sections.
For Oracle VM Server for SPARC, the <Content> section is used to identify and describe a particular domain. The domain name in the id= attribute of the <Content> node identifies the domain. Within the <Content> section are one or more <Section> sections describing resources of the domain as needed by the particular command.
If you need to identify only a domain name, then you do not need to use any <Section> tags. Conversely, if no domain identifier is needed for the command, then you need to provide a <Section> section describing the resources needed for the command, placed outside a <Content> section but still within the <Envelope> section.
A <data> section does not need to contain an <Envelope> tag in cases where the object information can be inferred. This situation mainly applies to requests for monitoring all objects applicable to an action, and event registration and unregistration requests.
Two additional OVF types enable the use of the OVF specification's schema to properly define all types of objects:
<gprop:GenericProperty> tag
<Binding> tag
The <gprop:GenericProperty> tag handles any object's property for which the OVF specification does not have a definition. The property name is defined in the key= attribute of the node and the value of the property is the contents of the node. The <binding> tag is used in the ldm list-bindings command output to define resources that are bound to other resources.
An outgoing XML response closely matches the structure of the incoming request in terms of the commands and objects included, with the addition of a <Response> section for each object and command specified, as well as an overall <Response> section for the request. The <Response> sections provide status and message information. The following example shows the structure of a response to a basic XML request.
Example 6 Format of a Response to a Single Command Operating on a Single Object<LDM_interface version="1.7"> <cmd> <action>Place command here</action> <data version="3.0"> <Envelope> <References/> <!-- Note a <Section> section can be here instead of <Content> <Content xsi:type="ovf:VirtualSystem_Type" id="Domain name"> <Section xsi:type="ovf:ResourceAllocationSection_type"> <Item> <rasd:OtherResourceType> LDom Resource Type </rasd:OtherResourceType> <gprop:GenericProperty key="Property name"> Property Value </gprop:GenericProperty> </Item> </Section> <!-- Note: More <Section> </Content> </Envelope> <response> <status>success or failure</status> <resp_msg>Reason for failure</resp_msg> </response> </data> <response> <status>success or failure</status> <resp_msg>Reason for failure</resp_msg> </response> </cmd> <response> <status>success or failure</status> <resp_msg>Reason for failure</resp_msg> </response> </LDM_interface>
This <response> section, which is the direct child of the <LDM_interface> section, indicates overall success or failure of the entire request. Unless the incoming XML document is malformed, the <response> section includes only a <status> tag. If this response status indicates success, all commands on all objects have succeeded. If this response status is a failure and there is no <resp_msg> tag, then one of the commands included in the original request failed. The <resp_msg> tag is used only to describe some problem with the XML document itself.
The <response> section under the <cmd> section alerts the user to success or failure of that particular command. The <status> tag shows whether that command succeeds or fails. As with the overall response, if the command fails, the <response> section includes only a <resp_msg> tag if the contents of the <cmd> section of the request is malformed. Otherwise, the failed status means one of the objects that the command ran against caused a failure.
Finally, each <data> section in a <cmd> section also has a <response> section. This section shows whether the command being run on this particular object passes or fails. If the status of the response is SUCCESS, there is no <resp_msg> tag in the <response> section. If the status is FAILURE, there are one or more <resp_msg> tags in the <response> field depending on the errors encountered when running the command against that object. Object errors can result from problems found when running the command, or a malformed or unknown object.
In addition to the <response> section, the <data> section can contain other information. This information is in the same format as an incoming <data> field, describing the object that caused a failure. See The <data> Tag. This additional information is especially useful in the following cases:
When a command fails against a particular <data> section but passes for any additional <data> sections
When an empty <data> section is passed into a command and fails for some domains but passes for others