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
erDiagram
WASMCLOUD_HOST ||--|| State : has
State }|..o{ Actor : has
State }|..o{ Provider : has
State }|..o{ Link_Definiton : has
LATTICE_OBSERVER }|--|| Lattice : has
Lattice ||--|| State: contains
WADM ||--o| Deployment_State : has
Deployment_State }|..o{ Actor : has
Deployment_State }|..o{ Provider : has
Deployment_State }|..o{ Link_Definiton : has
graph TD
A[Updated OAM Spec] -->|Apply| B(HOST_CORE)
B -->|Spin Up| C(Actor/Provider/Link)
C --> |Reconcile| D{Diff}
D -->|Yes/Apply/Backoff| B
D -->|No| E[Done]
F[WASHBOARD]-->|manual entry| B
How is the contention between the UI and OAM spec going to be handled - who wins? Last in?
Incomplete thoughts - Since Horde is involved WADM is a singleton? Haven't processed that. Redis will maintain....
The text was updated successfully, but these errors were encountered:
https://mermaid.live
https://mermaid-js.github.io/mermaid/#/entityRelationshipDiagram
Looking through the code that has been written up this is my mental picture
How is the contention between the UI and OAM spec going to be handled - who wins? Last in?
Incomplete thoughts - Since Horde is involved WADM is a singleton? Haven't processed that. Redis will maintain....
The text was updated successfully, but these errors were encountered: