<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="-webkit-text-size-adjust: auto;"><span></span></div><div><span style="-webkit-text-size-adjust: auto;"></span><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Hi All,</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">In the current design, <i>gluster peer probe</i> 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<i>peer detach </i>command<i>. </i></span></div><div><i style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></i></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Wondering if it makes sense to bring in <i>gluster peer attach</i> 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. </span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Thoughts?</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Thanks</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Naga</span></div></div></body></html>