oak: Aggregator example should not create new nodes from existing nodes
Once we start labelling created nodes with more sensible labels, the main programming pattern will be for all nodes and channels to be created directly by the initial node of an application, while “worker” nodes just receive handles to pre-existing objects.
For the aggregator example, this means creating the gRPC client pseudo-node as part of the oak_main entrypoint:
and then pass its handle to the gRPC worker.
The complication is that the gRPC worker currently only accepts gRPC invocation messages as input, so it needs to be modified so that it can accept a new type of message which is essentially an enum of either an “init” message (containing the initial handles and any other configuration), or the actual gRPC message to process.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- Change aggregator creation (#1546) This change makes Aggregator create gRPC client Node before receiving invocations. Fixes #1246 — committed to project-oak/oak by ipetr0v 4 years ago
And started receiving the following errors:
Looks like I need to update the generator code.