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
..
agent	Add E128 to pep8 check list	2017-02-13 18:17:21 +08:00
common	Remove unused constant	2017-10-29 09:46:31 +00:00
db	BGP service - take logical port info from Neutron DB	2018-02-23 08:22:08 +02:00
ml2	Refactoring of ZMQ pubsub	2018-06-12 13:01:49 +00:00
services	use rpc Connection rather than create_connection	2018-04-17 06:29:21 -06:00
__init__.py	Set Up the neutron l3 sdn addon using neutron as library	2015-03-01 18:16:07 +02:00