-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Implement a (Pseudo-Protocol) Service - used to connect an Executors to CATs' Data Mesh using IPFS
Service maintains separation Mechanisms (Action) & Policies (Control) [Planes] by translating Order into CATs' Data Service Planes as the following members:
- Action Plane: CATs' Data Plane exposing the Kubernetes Control & Data Planes
- Content-Addressed communication between services
- Control Plane: Management of the configuration and policies of communication
- Asynchronous Inter-Process Communication with Action from Actor in the Action Plane w/ Acknowledgements
AC:
- Service exists and transfers data between IPFS, CAT BOM, and local storage & memory
- Implement Service as IPFS Client connection #57
- BOM Composer #152
- Service Configures Structure
- Service Class Diagram #150
Metadata
Metadata
Assignees
Labels
epicAgile epicAgile epic