-
Notifications
You must be signed in to change notification settings - Fork 20
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
Invoke update dashboard flow from monitoring integration while addition of volume/brick/peer #385
Comments
tendrl-bug-id: Tendrl#385 Signed-off-by: Shubhendu <[email protected]>
tendrl-bug-id: Tendrl/gluster-integration#385 Signed-off-by: Shubhendu <[email protected]>
tendrl-bug-id: Tendrl/gluster-integration#385 Signed-off-by: Shubhendu <[email protected]>
tendrl-bug-id: Tendrl#385 Signed-off-by: Shubhendu <[email protected]>
tendrl-bug-id: Tendrl#385 Signed-off-by: Shubhendu <[email protected]>
tendrl-bug-id: Tendrl#385 Signed-off-by: Shubhendu <[email protected]>
@shtripat I guess we are waiting for gluster to provide brick related info as part of volume create event right. Once we have that, we can fully address this issue right ? |
Currently all the events taken care for peer/volume and brick for add/delete through events and update dashboard gets invoked. even while volume create, we find out the bricks and invoke the update dashboard as a workaround till the gluster event provides the bricks details as well as part of volume create event. This ideally can be closed as changes are merged. I am closing this now and would create another when gluster event has brick details to accomodate the changes in gluster-integration. |
This should be done to update the dashboard immediately while adding a fresh volume / brick / peer while sds sync.
The text was updated successfully, but these errors were encountered: