PTP/designs/3.x/rm proxy

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. The proxy is expected to respond to commands but any returned data must be send back asynchronously as separate events.

Initialize

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.

StartEvents

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.

StopEvents

Command to halt the event stream to the RM.

Finish

Command for the proxy to cleanup and exit.

Protocol for commands

1. The RM first creates a transaction id for the command.
@. Then the command plus the transaction id is sent to the proxy.
(A version number should be maintained for the protocol.)

Protocol for events

1. The proxy first completes (or at least initiates) the command.
2. Then the proxy sends an event containing the transaction id back to the RM.

   - create a transaction id
   - command plus transaction id forwarded to remote side
   - need version number of protocol