openstack
/
dragonflow
Code Issues Proposed changes
dragonflow/dragonflow/db/pubsub_drivers
History
Shachar Snapiri bbe1347e4e Refactoring of ZMQ pubsub 
To work around the ZMQ issues (publisher binds to a port, thus only one
publisher can work on a given IP), we had a lot of junk code in our
repo.
Removed all redundant mechanisms (use_multiproc, is_neutron_server) and
modified to have 2 types of configurable ZMQ drivers:
1. zmq_remote_pubsub_driver - Has TCP publisher and IPC subscriber, This
   should be used in the publisher service.
2. zmq_pubsub_driver - Has IPC publisher and TCP subscriberi, This
   should be used in all other uses.

The way to set the one to use is via configuration, thus it is up to the
deployment to make sure this is configured correctly.

Change-Id: Ibf7894e608187e87bdeb7774749bfa0cc15eae56
 		2018-06-12 13:01:49 +00:00
..
__init__.py [Trivial] Remove unnecessary executable privilege 2016-04-29 19:44:00 +08:00
etcd_pubsub_driver.py Add is_running property to the subscriber api in pubsub 2018-05-01 13:41:21 +03:00
nb_api_neutron_notifier.py use neutron notifier correctly 2017-09-07 09:14:37 +00:00
redis_db_pubsub_driver.py Fix typos in dragonflow 2018-02-14 08:36:08 +00:00
zmq_pubsub_driver.py Refactoring of ZMQ pubsub 2018-06-12 13:01:49 +00:00