...
hzn exchange node hagroup create --nodeId node1 --nodeId node2 --nodeId node3 --force
hzn exchange node hagroup remove --nodeId node1
hzn exchange node hagroup list
hzn deploycheck --checkHA
None
Agent - Awareness of HAGroup membership for agent upgrade procedure
Agbot - Awareness of a node's HAGroup membership for making agreements
CLI - To list, add, remove nodes from an HA Group
Exchange - To hold the new HAGroup membership APIs
None
The HAGroup object schema
members: [
{
"node":"node1234"
},
]
Exchange APIs:
Create a new node group. The caller must have permission to modify all the nodes listed in the body (shown above). The Exchange will set this same object onto all the nodes listed in the body. The Exchange will return an error (409) if one of the nodes is already in an hagroup. If force=true is specified, the Exchange will set this membership onto all listed nodes and will remove listed nodes from any group they are already in.
POST /org/<org>/node/<node-id>/hagroup?force=true
Modify the group membership of an existing group. All the desired members of the group MUST be listed in the body. This API behaves like a full replace. The force=true parameter has the same behavior as on POST.
PUT /org/<org>/node/<node-id>/hagroup?force=true
List all the members in an hagroup. This API returns the exact same results when called on any member in an ha group.
GET /org/<org>/node/<node-id>/hagroup
None
Need an Overview of how HA Groups work on the OH doc site.
Need a new article describing how to use HA Groups, this would be focused toward the administrator and node owners. It could be the same article for both roles (but we might change our mind on this AFTER we have tried to write it).
Update/remove HA doc in the anax repo for the HA /attribute API. This is being removed.
CLI commands
- Edge Clusters are out of scope for this support. Edge clusters already natively support HA and CA, and therefore don't need any special assistance from OpenHorizon.
- Test service lifecycles with services deployed to HA groups that are homogeneous (all members have the same services) and heterogeneous (there is at least 1 service common to all members, but some services are only running on a subset of members).
- Performance test of service upgrades with and without HA groups in the system.