The root element of any Message. Everything starts here. The body of a Message itself. Can contain several classes of information directed to different Operators by specifying several "target"s. Packet header Operator is a part of VZAgent functionality, which serves a set of related requests grouped by some common principle like User-Group Management operations. Usually, it should be deived by instanced Operator and there should be realized here two sequences or choices of elements: one for "input" requests and one for "output" responces. Operator, which serves as a statistics collector and provides information on a periodic basis. Operator, allowing OK and Error in its body. Packet header type ***INTERNAL*** Authorization information. For now it contains only veid of VE, permitted to access. For superuser with login vzagent0 veid is omitted and he has full access. User-defined information, used to hold some data, describing the packet. User will receive it back unchanged in response from VZAgent. Target, specifying name of an Operator to process a request, class of subscription or name of a Client in a response to him. When target is absent it's considered to be a system message ( see "system" in group "on_demands" ). Message sender's name. It can be Operator's name or Client's name, generated by VZAgent, when the Client logged in. Source routing information. This is filled in with a corresponding Directors on a route out of the Operator, sending the request. Also, it is being duplicated into "dst" when reply is generated. Destination routing information. This is set by the Operator, sending the remote request. Session ID, used for SOAP connections and SOAP user authentication. The string contains name of the user and session ID separated by a dot. Version of VZAgent protocol. Since the first release, where version 0.5 of the protocol was used for Virtuozzo 2.0.2, version of Virtuozzo is used. Current implementation is 2.5.0. ID of the packet. Used to identify the packet and its response, which will contain the same ID. Usually integer, but can be a string. The field is necessary to set if you need to see progress of your request processing and be notified in case of failure because of timeout or some other reason. Normal error message will be reported even for packets without ID. ID should be unique per connection. Priority of the packet. Used to specify the importance of it, when it's placed into a message queue or when some packet should be dropped in case of queue overflow. The higher priority value the less important is the packet. Zero is the default priority. Priorities range from -3000 to 3000. -3000 to -1000 for heavy messages. -999 to 999 for normal messages. 1000 to 3000 for urgent messages. Time, when the packet was sent by it's creator. When present the automatic progress reporting is invoked for this request being processed. When present the automatic progress reporting is logged for the operations supporting it, so-called “logged operations”. Possible values are “on” or “off”. Default is “off”. *** INTERNAL *** Bitfield for the internal type of the Message. #define UNFINISHED 0x00000001 #define RESPONSE 0x00000002 #define RESCHEDULE 0x00000004 #define TIMEOUT 0x00000008 *** INTERNAL *** Timeout, which will be used for handling of this request. Might be specified in incoming packet or might be sent back from Operator, notifying its Director about the time he is going to handle it. *** INTERNAL *** Timeout limit for message processing. Used by an operator in determining the validity of it's timeout. *** INTERNAL *** UID of the user, which sent this packet. Basic Operator type. Declares some Input commands, some Output responses and its Configuration if present. Should be inherited and reworked for specific Operators declaration. Basic Operator type. Declares some Input commands, some Output responses and its Configuration if present. Should be inherited and reworked for specific Operators declaration. Ok is used when no other valid data is requested to send and the request was successfully completed. Error is used in any case when function call was not successful. Depending on an operator behaviour, message can stop further function calls parsing or continue. Error code. Error Message Basic Periodic Operator type. Derived from operatorType it adds some common Input, allowing to configure periods of statistics processing. Input ***INTERNAL*** Sets periods of collecting, logging and reporting information for logs ( in seconds ). Used by DBM operator only. Might not be implemented and used for strictly monitoring Periodic Operators. ***INTERNAL*** Request to send all of the collected data right away, instead of waiting for the "report" period to end. Used by DBM operator only. Might not be implemented and used for strictly monitoring Periodic Operators. Starts another monitoring facility. Messages will be sent to the requesting client with "period" intervals. Target should be the name of the client requested monitoring. Stops the monitoring facility, started previously by the same client. Common configuration of Periodic collectors. Can be present in both input and output packets. Periodic Operators type, used for logging setup. Period with which a new data is collected and processed for staticstics. Period with which the collected data is summarized and added to a report, preparing for sending. Period with which the compiled by log period message is sent to DBM. Reporting period. VE ID (only for VE-related periodic operators). VE ID (only for VE-related periodic operators). ***INTERNAL*** Authorization information. For now it contains only veid of VE, permitted to access. For superuser with login vzagent0 veid is omitted and he has full access. Either of VE list VE ID Event configuration structure Priority of the Event Messages. Period of checking. Priority of log packets. Priority of monitor packets. Minimum monitoring period available for a USER client. Minimum monitoring period available for a ROOT client. The Director, Operator belongs to. VZAgent ID of the host, by which the host address will be taken. Should be either contained in VZAgent configuration (global mapping) or be a result of exclusive connect. For on-demands and other multiple accessors it specifies the particular target. Real origin is saved here, when packet is sent remotely. File Transfer. Target tag should contain file_transfer. Input Reads a block from file. Returns "read" or Error. The block itself is sent right after the binary zero, delimiting the response and contain exactly the "size" of bytes, specified in response. Path to file in uploads directory. Offset in file. Size of the block. Writes a block to file. Returns "write" or Error. The block itself should be sent right after this message and contain exactly the "size" of bytes, specified in the parameters. Path to file in uploads directory. Offset in file. Size of the block. Gets size of the file. Returns "size" or Error Path to file in uploads directory. Create a special local socket in client directory. This socket is used by exec in special mode. Output Size of bytes read. Size of bytes written. Size of file. Signals switching to raw mode. Signals switching back to vza mode. Packet version string.