-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API call to trigger ExpandClusterWithDetectedPeers flow #385
Comments
Fixes: Tendrl#385 tendrl-bug-id: Tendrl#385
There is also another existing (undocumented?) API '/:cluster_id/ExpandCluster`, which I'm assuming is in the old format. |
Tendrl/ui/issues/848 depends on this |
Fixes: Tendrl#385 tendrl-bug-id: Tendrl#385
@shirshendu The flow "ExpandCluster" was coded as a day 0 flow. Where it would actually install gluster on the new nodes using gdeploy and adds them to the Gluster trusted storage pool The current "ExpandClusterWithDetectedPeers" simply detects new nodes which are recently added to the Gluster trusted storage pool by the user, it does not install gluster on the new nodes and assumes it is done by the user. The old "ExpandCluster" flow is already disabled via definitions, the API can use that to decide if it is a valid flow or not |
Fixes: Tendrl#385 tendrl-bug-id: Tendrl#385
As per Tendrl/commons#805 (comment) , we need an API call that can enqueue a job that triggers the
ExpandClusterWithDetectedPeers
flow.https://github.com/Tendrl/commons/pull/831/files#diff-1a5320aa0fd1eea178e6ed255509c9c4 holds definitions required for the spec.
The text was updated successfully, but these errors were encountered: