<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Yup - I guess it depends upon what we want it to return.<br></div><div><br></div><div>If the process is a simple "are you alive"... 'ping' works.<br></div><div><br></div><div>However, if we want more info returned - maybe detect is more self-explanatory.<br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Giuseppe Ragusa" <giuseppe.ragusa@hotmail.com><br><b>To: </b>"Paul Cuzner" <pcuzner@redhat.com>, "Jay Vyas" <jayunit100@gmail.com><br><b>Cc: </b>"Gluster Devel" <gluster-devel@nongnu.org><br><b>Sent: </b>Monday, 7 April, 2014 8:04:07 AM<br><b>Subject: </b>RE: [Gluster-devel] Introducing a new option to gluster peer command.<br><div><br></div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Well, "peer ping" since we are giving way to imagination... :)<br><div><br></div><div><hr id="stopSpelling">Date: Sun, 6 Apr 2014 15:42:03 -0400<br>From: pcuzner@redhat.com<br>To: jayunit100@gmail.com<br>CC: gluster-devel@nongnu.org<br>Subject: Re: [Gluster-devel] Introducing a new option to gluster peer command.<br><div><br></div><div style="font-family:lucida console,sans-serif;font-size:12pt;color:#000000;"><div><br></div><div>Sounds like a great idea.<br></div><div><br></div><div>Although, peer sniff .... Really :)<br></div><div><br></div><div>What about "peer detect"?<br></div><div><br></div><div><br></div><div><br></div><hr id="ecxzwchr"><blockquote style="border-left:2px solid #1010FF;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jay Vyas" <jayunit100@gmail.com><br><b>To: </b>"Harshavardhana" <harsha@harshavardhana.net><br><b>Cc: </b>"Paul Cuzner" <pcuzner@redhat.com>, "Gluster Devel" <gluster-devel@nongnu.org><br><b>Sent: </b>Friday, 4 April, 2014 3:58:32 PM<br><b>Subject: </b>Re: [Gluster-devel] Introducing a new option to gluster peer command.<br><div><br></div><div dir="ltr"><div><div><div>can i suggest that instead, we keep peer probe as is, and rewrite it to call two subcommands <br></div></div><br></div>- peer sniff<br><div>- peer attach<br><div><br></div></div><div>That way users that want advanced peer sniffing can do so, without breaking backwards compatibility<br></div><div><br><div><br></div></div></div><div class="ecxgmail_extra"><br><div><br></div><div class="ecxgmail_quote">On Thu, Apr 3, 2014 at 9:22 PM, Harshavardhana <span dir="ltr"><<a href="mailto:harsha@harshavardhana.net" target="_blank">harsha@harshavardhana.net</a>></span> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">+1 to Paul's idea - it sounds more friendly from Admin point of view -<br> also provides consistency with naming schemes.<br><div class="ecxHOEnZb"><div class="h5"><br> On Thu, Apr 3, 2014 at 4:57 PM, Paul Cuzner <<a href="mailto:pcuzner@redhat.com" target="_blank">pcuzner@redhat.com</a>> wrote:<br> ><br> > I like the idea of making the CLI more semantically correct. ie to drop a<br> > node from a cluster we use the term detach, so to add a node it should be<br> > attach.<br> ><br> > Would a peer probe then be more of a diagnostic command ?<br> > - ie return whether 24007 is open, perform initial handshake - determine<br> > gluster version and report back to the admin?<br> ><br> > This would mean that you could make intelligent decisions about bringing<br> > nodes into the cluster from the automation platform.<br> ><br> ><br> > ________________________________<br> ><br> > From: "Nagaprasad Sathyanarayana" <<a href="mailto:nsathyan@redhat.com" target="_blank">nsathyan@redhat.com</a>><br> > To: "James" <<a href="mailto:purpleidea@gmail.com" target="_blank">purpleidea@gmail.com</a>><br> > Cc: <a href="mailto:gluster-devel@nongnu.org" target="_blank">gluster-devel@nongnu.org</a><br> > Sent: Tuesday, 1 April, 2014 6:01:42 PM<br> > Subject: Re: [Gluster-devel] Introducing a new option to gluster peer<br> > command.<br> ><br> ><br> > On 04/01/2014 08:23 AM, James wrote:<br> ><br> > On Mon, Mar 31, 2014 at 10:29 PM, Nagaprasad Sathyanarayana<br> > <<a href="mailto:nsathyan@redhat.com" target="_blank">nsathyan@redhat.com</a>> wrote:<br> ><br> > In the current design, gluster peer probe does the job of both probing the<br> > server and adding it to trusted pool. Once the server is added to trusted<br> > pool, it can be detached usingpeer detach command.<br> ><br> > Wondering if it makes sense to bring in gluster peer attach command to add<br> > the server to trusted pool. The peer probe command will only prove the<br> > server mentioned and tells if it is reachable. It can also be enhanced to do<br> > some diagnostics such as probing specific ports.<br> ><br> > Do I understand correctly:<br> ><br> > gluster peer attach would attach the probing server into the pool it<br> > is probing, correct?<br> > If so, and if it is already a member of a pool, could you join two<br> > different pools together?<br> > I don't know what the gluster internals implications are, but as long<br> > as I understand this correctly, then I think it would benefit the<br> > management side of glusterfs.<br> ><br> > It would certainly make peering more decentralized, as long as double<br> > peering or running a simultaneous peer attach and peer probe don't<br> > cause issues. This last point is very important :)<br> ><br> ><br> > Cheers,<br> > James<br> ><br> > The "gluster peer attach" should work the same way as existing "gluster peer<br> > probe". The new "gluster peer probe" shall only probe the peer and not add<br> > it to the trusted pool. When we give peer detach option, I think it would<br> > be natural to expect a peer attach command.<br> ><br> > Thanks<br> > Naga<br> ><br> > _______________________________________________<br> > Gluster-devel mailing list<br> > <a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br> > <a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> ><br> ><br> ><br> > _______________________________________________<br> > Gluster-devel mailing list<br> > <a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br> > <a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br> ><br> <br> <br> <br></div></div><span class="ecxHOEnZb"><span style="color:#888888;">--<br> Religious confuse piety with mere ritual, the virtuous confuse<br> regulation with outcomes<br> </span></span><div class="ecxHOEnZb"><div class="h5"><br> _______________________________________________<br> Gluster-devel mailing list<br> <a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br> <a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Jay Vyas<br><a href="http://jayunit100.blogspot.com" target="_blank">http://jayunit100.blogspot.com</a><br></div></blockquote><div><br></div></div><br>_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel</div>                                            </div>
</blockquote><div><br></div></div></body></html>