Shireesh Anjal has posted comments on this change.

Change subject: engine: Added new canDoAction check for gluster
......................................................................


Patch Set 1:

Alon, I understand your point. However, we need to prevent the user from trying 
to add a server to a cluster if it already is part of a different gluster 
cluster. The only way to check this is by executing the "gluster peer status" 
command on that server via ssh.

Can you suggest any other way to address this?

Currently, in absence of this canDoAction check, we allow the server to be 
added, it gets bootstrapped, and finally the gluster peer probe fails, making 
the server non-operational. This flow is extremely non-user-friendly and 
confusing.

Note that the check is being added only in case of a gluster-only server.

--
To view, visit http://gerrit.ovirt.org/13980
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I81427fa940bf1edabf316acebc428becac0171f8
Gerrit-PatchSet: 1
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Shireesh Anjal <san...@redhat.com>
Gerrit-Reviewer: Alon Bar-Lev <alo...@redhat.com>
Gerrit-Reviewer: Omer Frenkel <ofren...@redhat.com>
Gerrit-Reviewer: Sahina Bose <sab...@redhat.com>
Gerrit-Reviewer: Shireesh Anjal <san...@redhat.com>
Gerrit-Reviewer: Yair Zaslavsky <yzasl...@redhat.com>
_______________________________________________
Engine-patches mailing list
Engine-patches@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-patches

Reply via email to