Hello Folks,
When zeromq is use as rpc-backend, "nova-rpc-zmq-receiver" service needs to
be run on every node.
zmq-receiver receives messages on tcp://*:9501 with socket type PULL and
based on topic-name (which is extracted from received data), it forwards
data to respective local services, over IPC protocol.
While, openstack services, listen/bind on "IPC" socket with socket-type
PULL.
I see, zmq-receiver as a bottleneck and overhead as per the current design.
1. if this service crashes: communication lost.
2. overhead of running this extra service on every nodes, which just
forward messages as is.
I'm looking forward to, remove zmq-receiver service and enable direct
communication (nova-* and cinder-*) across and within node.
I believe, this will create, zmq experience more seamless.
the communication will change from IPC to zmq TCP socket type for each
service.
like: rpc.cast from scheduler -to - compute would be direct rpc message
passing. no routing through zmq-receiver.
Now, TCP protocol, all services will bind to unique port (port-range could
be, 9501-9510)
from nova.conf, rpc_zmq_matchmaker =
nova.openstack.common.rpc.matchmaker_ring.MatchMakerRing.
I have put arbitrary ports numbers after the service name.
file:///etc/oslo/matchmaker_ring.json
{
"cert:9507": [
"controller"
],
"cinder-scheduler:9508": [
"controller"
],
"cinder-volume:9509": [
"controller"
],
"compute:9501": [
"controller","computenodex"
],
"conductor:9502": [
"controller"
],
"consoleauth:9503": [
"controller"
],
"network:9504": [
"controller","computenodex"
],
"scheduler:9506": [
"controller"
],
"zmq_replies:9510": [
"controller","computenodex"
]
}
Here, the json file would keep track of ports for each services.
Looking forward to seek community feedback on this idea.
Regards,
Yatin
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
