
In a cloud that has multiple private networks and that requires floating IPs for public access, it's not possible to know which private network the floating IP should NAT to without the user providing some configuration. os-client-config added support for expressing such a thing in 1.17.0, so start consuming that. Change-Id: Iee634bcdc933a4c8d793ab9b25b27d9ecd77cdcc
24 lines
431 B
Plaintext
24 lines
431 B
Plaintext
pbr>=0.11,<2.0
|
|
|
|
munch
|
|
decorator
|
|
jsonpatch
|
|
ipaddress
|
|
os-client-config>=1.17.0
|
|
requestsexceptions>=1.1.1
|
|
six
|
|
|
|
keystoneauth1>=1.0.0
|
|
netifaces>=0.10.4
|
|
python-novaclient>=2.21.0,!=2.27.0,!=2.32.0
|
|
python-keystoneclient>=0.11.0
|
|
python-glanceclient>=1.0.0
|
|
python-cinderclient>=1.3.1
|
|
python-neutronclient>=2.3.10
|
|
python-troveclient>=1.2.0
|
|
python-ironicclient>=0.10.0
|
|
python-swiftclient>=2.5.0
|
|
python-heatclient>=0.3.0
|
|
|
|
dogpile.cache>=0.5.3
|