RM8615

Implements a redis client for publishing security group rules for ports
connected to briged networks.
So it looks like the set operations are simply True or False. I suppose we could consider the idea that there's overhead on that! Let's try to investigate this shortly and see if there are any trade-offs. One of the goals for quark going forward is to switch to gunicorn AND pymysql, effectively removing things that lock the entire process. Pymysql itself is slower, but under test, it had a tendency to be a lot more consistent. I'm concerned about adding back in something that would (maybe) lock the GIL after we're going to spend time to make neutron/quark more parallelizable