...
...
| Expand | ||
|---|---|---|
| ||
Possibly send heartbeats but not accept node property updates or changes Possibly allow geofencing information updates? Where the edge node is located might be important to know. Aha "The car is on the driveway, geofenced at home" is an important clue that might allow the agent to trigger changes to workloads. If the car is at the supermarket, not a good idea. Governance should restart the agreement, if it dies unexpectedly - tricky? node health state ? HA node groups need to skip over nodes that are in ChangeFreeze state. This is orthogonal to the reason for a HA group. Unsupported configuration. Let the external change "The car is in park and the GPS knows that the car is "home" - Call the API to change out of ChangeFreeze state". The agent never decides for itself that it out of ChangeFreeze state Build a "Agent Config State" API If a secret changes, the agbot sends a message of a change, if the agent doesn't see or handle that message, what happens? Max? Would the agreement get cancelled if the agent doesn't reply? MMS handling of agents in ChangeFreeze status - ESS should also go into ChangeFreeze state as well. It should not look for model updates while the edge node is in changefreeze state. Node Management- behavior? |
As a node owner, I want to want to "freeze" the services of the node until i decide they can be changed again / after a defined timeout expires.
As a service deployer, I want to have feedback about this "frozen" state of the node.
As an admin, I want to be able to unfreeze the node remotely via cli.
...