This currently doesn't work due to beta running on the labs network, which blocks the use of more interesting network routing used by LVS as a security feature.
I always assumed that was nova-network itself, but according to @chasemp: libvirt's native security group handling (that nova-network offloads to) prevents it.
However, when main labs runs on neutron instead of nova-network (neutron doesn't use libvirt's native handling of this stuff), we should be able to do http://superuser.openstack.org/articles/managing-port-level-security-openstack/ and open up the rules enough such that our backend hosts can impersonate the LVS host, and the LVS host can impersonate external traffic. (obviously haven't tested it but I believe those are the allowances that would need to be made).
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
deployment-prep: Make LVS config compatible with new requirements | operations/puppet | production | +37 -1 |
Event Timeline
Comment Actions
Change 316512 had a related patch set uploaded (by Alex Monk; owner: Alex Monk):
[operations/puppet@production] deployment-prep: Make LVS config compatible with new requirements
Comment Actions
Change 316512 merged by Tim Starling:
[operations/puppet@production] deployment-prep: Make LVS config compatible with new requirements
Comment Actions
So the testlabs project has access to eqiad1-r (the new neutron region) and I have projectadmin there. I'm going to open a task to figure out what the process should be to disable port security somewhere.