On 10/24/2017 03:36 PM, Ricardo Dias wrote:
Hi list, I was wondering if it makes sense to support multiple binds with a single messenger instance. The use case I have in mind is when there are multiple public/cluster networks specified in ceph.conf and we want to listen for connections in one interface of each network. With the support for multiple binds, we could use a single messenger instance to listen to all interfaces. Do you think it is worth to implement such support or is the above use case easily handled by having multiple messenger instances?
I would think multiple binds would make sense, but how would this affect setting the policies? Would we be sharing a single policy across multiple binds, or would we be allowed different policies for different binds?
Regardless, and not knowing the code, wouldn't this make sense for multiplexing multiple daemons on a single messenger? Making the messenger sort of a blackbox, that everyone could just use seamlessly without having to figure too many things out?
E.g., instead of multiplexing several osds on a messenger for the public network, and then the same set of osds on a messenger for the cluster network, we could simply have one messenger (bound to public and cluster) and have just that one messenger for all the osds.
Anyway, from an abstraction point-of-view it makes sense to me; no idea how feasible that would be though.
-Joao -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
