You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 17, 2020. It is now read-only.
The O² Control executor supports both FairMQ and Direct control modes, so it can be configured to send either:
FairMQ-specific state machine events to the OCC plugin of a running FairMQ device, or
"uncooked" Control state machine events with no FairMQ-specific handling to any other process with a compatible gRPC server.
No such process-side implementation exists yet (we only have FairMQPlugin_OCC) so this Direct non-FairMQ code path in O² Control is untested, and fer can be a candidate. Alternatively it could also make sense to keep fer's interface completely FairMQ compatible, use the FairMQ control mode and rather reimplement the equivalent to FairMQPlugin_OCC in fer.
In one way or another, the fer device should implement a gRPC server for this or a similar protofile, including a mechanism for defining channels and setting properties during (re)configuration.
Following up on alisw/alidist#1230 (comment)
The O² Control executor supports both
FairMQandDirectcontrol modes, so it can be configured to send either:No such process-side implementation exists yet (we only have
FairMQPlugin_OCC) so thisDirectnon-FairMQ code path in O² Control is untested, and fer can be a candidate. Alternatively it could also make sense to keep fer's interface completely FairMQ compatible, use the FairMQ control mode and rather reimplement the equivalent toFairMQPlugin_OCCin fer.In one way or another, the fer device should implement a gRPC server for this or a similar protofile, including a mechanism for defining channels and setting properties during (re)configuration.
See controlmode and occplugin.