Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

PTP/designs/3.x/rm proxy

< PTP‎ | designs
Revision as of 18:00, 2 January 2007 by Crasmussen.lanl.gov (Talk | contribs) (Proxy Events)

Overview

This is a preliminary design for the PTP Resource Management events and proxy communication system. This probably should be folded back into the Resource Management Design once everything is fleshed out.

Resource Manager Proxy

The Resource Manager (RM) communicates with proxy agents to gather information about the state of machines, nodes, queues, jobs, and processes. The proxy may be located remotely.

The RM first starts a proxy and then sends commands to it.

Resource Manager Commands

RM commands are fully asynchronous. They are send from the RM to the proxy. The proxy is expected to respond to commands, but any returned data must be send back asynchronously as separate events.

Protocol for commands
1. The RM creates a transaction id for the command.
2. The RM sends the command plus the transaction id to the proxy.
(A version number should be maintained for the protocol.)
Wire protocol for a command
Commands are currently sent as transformed (tohex) ascii strings.
They contain (this needs more thought): COMMAND, TRANSACTION_ID, DATA.
Initialize ("INIT")
Command to initialize the proxy. After this command has been received, the proxy is ready to receive and process other commands from the RM. Initialization data may be passed on the command line when the proxy is run.
Start events ("SEND_EVENTS")
Command to start sending events back to the RM. Initially the proxy sends back the full machine state, but sends only state changes as diffs thereafter.
Stop events ("HALT_EVENTS")
Command to halt the event stream to the RM.
Finish ("FINISH")
Command for the proxy to cleanup and exit.
Attribute definition ("DEF_ATTRS")
Command requesting that proxy send a list of attributes. Attributes (see below) are meta-data describing data from the proxy that the RM is expected to receive and possibly display in the UI.
Submit job ("SUBMIT")
Command to submit a job.
Others
Kill job, ...


Proxy Events

The proxy responds to commands from the RM by sending events back to the RM.

Protocol for events
1. The proxy completes (or at least initiates) the command.
2. The proxy sends an event containing the transaction id back to the RM. Any data are returned with the event after the transaction id.
Wire protocol for an event
Events are currently sent as transformed (tohex) ascii strings.
They contain: LENGTH(8 hex digits) TRANSACTION_ID(8 hex digits) CODE(4 hex digits) " " DATA.
FAILURE_EVENT
Sent if a failure occurs while processing a command.
ATTR_DEF_EVENT
A list of attributes that the proxy may send as data.
LAUNCH_CONFIG_EVENT
A list of attributes needed to launch a job, e.g., every queue needs to send a list of attribute ids needed to submitted a job
JOB_SUBMISSION_EVENT
Notification that a job has been submitted for execution. The job id will be returned as part of the event.
Others
Machine change, host change, queue change, job status change, ...

Attributes

Attributes are used so that data sent to the RM is self describing. Attributes are meta-data describing actual data. Attribute ids must be unique (who generates them then?). An attribute has a:

   id:
   type:
   min_value:
   max_value:
   default_value:
   optional:

Back to the top