On 04/01/2014 07:59 AM, Nagaprasad Sathyanarayana wrote:
Hi All,
In the current design, /gluster peer probe/ does the job of both
probing the server and adding it to trusted pool. Once the server is
added to trusted pool, it can be detached using/peer detach /command/. /
/
/
Wondering if it makes sense to bring in /gluster peer attach/ command
to add the server to trusted pool. The peer probe command will only
prove the server mentioned and tells if it is reachable. It can also
be enhanced to do some diagnostics such as probing specific ports.
Thoughts?
Hey Naga,
If we implement peer probe and attach commands as you suggested, does it
mean the new peer probe command will be an optional command? if yes, IMO
we can just add another optional argument to the peer probe/attach
command e.g. "--dryrun" to do all diagnostics rather adding a new
command line.
Thanks,
Lala
Thanks
Naga
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
