-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EE] Discuss how libres and ERT should communicate #1061
Comments
Doing a quick survey, it seems that https://cloudevents.io/ is a potential winner. They have also done a survey of existing event formats, for reference. It's protocol agnostic, the events are JSON and have the following required attributes:
Example: {
"specversion" : "1.x-wip",
"type" : "com.github.pull_request.opened",
"source" : "https://github.com/cloudevents/spec/pull",
"subject" : "123",
"id" : "A234-1234-1234",
"time" : "2018-04-05T17:31:00Z",
"comexampleextension1" : "value",
"comexampleothervalue" : 5,
"datacontenttype" : "text/xml",
"data" : "<much wow=\"xml\"/>"
} There's a Python SDK https://github.com/cloudevents/sdk-python Is well on its way of being blessed by the CNFC… They provide a vocabulary with which we can talk about events https://github.com/cloudevents/spec/blob/master/spec.md#notations-and-terminology |
https://github.com/cloudevents/spec/blob/master/spec.md
Following events are definedForward Model Job
Forward Model Step (Job dispatch)(Local queue for executing job_dispatch, aka meta job_dispatch)
Forward Model Stage (Queue Manager)
Ensemble Evaluator (TBD)
|
We need to find a suitable protocol for ERT and libres to communicate over. This should preferably not be something we invent ourselves. We should also make sure we solve this without creating a circular dependency between ERT and libres!
The text was updated successfully, but these errors were encountered: