Clusters are first-class citizens in Senlin service design. A cluster is defined as a collection of homogeneous objects. The “homogeneous” here means that the objects managed (aka. Nodes) have to be instantiated from the same “profile type”.
To examine the list of receivers:
When listing clusters, you can specify the sorting option using the sort
parameter and you can do pagination using the limit
and marker
parameters.
Full example: manage cluster
When creating a cluster, you will provide a dictionary with keys and values according to the cluster type referenced.
Optionally, you can specify a metadata
keyword argument that contains some
key-value pairs to be associated with the cluster.
Full example: manage cluster
After a cluster is created, most of its properties are immutable. Still, you
can update a cluster’s name
and/or params
.
Full example: manage cluster
A cluster can be deleted after creation, When there are nodes in the cluster, the Senlin engine will launch a process to delete all nodes from the cluster and destroy them before deleting the cluster object itself.
Add some existing nodes into the specified cluster.
Remove nodes from specified cluster.
Replace some existing nodes in the specified cluster.
Inflate the size of a cluster.
Shrink the size of a cluster.
Resize of cluster.
Once a policy is attached (bound) to a cluster, it will be enforced when related actions are performed on that cluster, unless the policy is (temporarily) disabled on the cluster
Once a policy is attached to a cluster, it can be detached from the cluster at user’s request.
Check cluster health status, Cluster members can be check.
To restore a specified cluster, members in the cluster will be checked.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.