Hi, I wasn't thinking of an interface to mark sockets directly (didn't know one existed at the socket interface), rather something we might maintain, perhaps a query interface on the server, or perhaps DBUS, etc.
Matt ----- "Sage Weil" <sw...@redhat.com> wrote: > On Wed, 27 Aug 2014, Matt W. Benjamin wrote: > > > > ----- "Sage Weil" <sw...@redhat.com> wrote: > > > > > > What would be best way for us to mark which sockets are heartbeat > > > related? > > > Is there some setsockopt() type call we should be using, or should > we > > > > > > perhaps use a different port range for heartbeat traffic? > > > > Would be be plausible to have hb messengers identify themselves to a > bus as such, > > that external tools (here, the ts scripts) could introspect? > > What do you mean by bus in this case? > > I seem to remember someone telling me there were hooks/hints you could > > call that would tag either a socket or possibly data on that socket > with a > label for use by iptables and such.. but I forget what it was. > > sage > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
