94e4dbd733
In order for us to notice config changes in clouds.yaml, rather than consuming it indirectly via shade, create the cloud config directly and pass it in to the shade factory function. There would not be a huge win in teaching shade to notice and update itself at the moment, as the update processing happens in a different place and there isn't really a great way to have the check ask the old provider manager to see if its cloud config has changed. Change-Id: Ie4cf44adefda637b5987dd9d39ec398786086720 Depends-On: Icdd9acede81bc5fba60d877194048e24a62c9e5d
24 lines
425 B
Plaintext
24 lines
425 B
Plaintext
pbr>=0.6,!=0.7,<1.0
|
|
|
|
gear
|
|
PyYAML
|
|
python-jenkins
|
|
paramiko>1.9.0
|
|
python-daemon>=2.0.4
|
|
extras
|
|
statsd>=1.0.0,<3.0
|
|
apscheduler>=2.1.1,<3.0
|
|
sqlalchemy>=0.8.2,<0.9.0
|
|
pyzmq>=13.1.0,<14.0.0
|
|
python-glanceclient
|
|
python-keystoneclient
|
|
python-novaclient>=2.21.0
|
|
PyMySQL
|
|
PrettyTable>=0.6,<0.8
|
|
# shade has a looser requirement on six than nodepool, so install six first
|
|
six>=1.7.0
|
|
os-client-config>=1.2.0
|
|
shade
|
|
diskimage-builder
|
|
voluptuous
|