8d9cab2eb9
When we assign a floating ip to a server, we re-fetch it from the cloud so that the metadata is all correct. However, we weren't doing obj_to_dict on it like all of the other code paths that return out of create_server - which means that it bombs out on get_hostvars_from_server if subsequently passed to it. Change-Id: I3f69f525b7d57ec91f70b77cdbd62aed9816f17d |
||
|---|---|---|
| doc/source | ||
| shade | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
shade
shade is a simple client library for operating OpenStack clouds. The key word here is simple. Clouds can do many many many things - but there are probably only about 10 of them that most people care about with any regularity. If you want to do complicated things, you should probably use the lower level client libraries - or even the REST API directly. However, if what you want is to be able to write an application that talks to clouds no matter what crazy choices the deployer has made in an attempt to be more hipster than their self-entitled narcissist peers, then shade is for you.
shade started its life as some code inside of ansible. ansible has a bunch of different OpenStack related modules, and there was a ton of duplicated code. Eventually, between refactoring that duplication into an internal library, and adding logic and features that the OpenStack Infra team had developed to run client applications at scale, it turned out that we'd written nine-tenths of what we'd need to have a standalone library.
example
Sometimes an example is nice. :
from shade import *
import time
# Initialize cloud
# Cloud configs are read with os-client-config
cloud = openstack_cloud('mordred')
# OpenStackCloud object has an interface exposing OpenStack services methods
print cloud.list_servers()
s = cloud.list_servers()[0]
# But you can also access the underlying python-*client objects
cinder = cloud.cinder_client
volumes = cinder.volumes.list()
volume_id = [v for v in volumes if v['status'] == 'available'][0]['id']
nova = cloud.nova_client
print nova.volumes.create_server_volume(s['id'], volume_id, None)
attachments = []
print volume_id
while not attachments:
print "Waiting for attach to finish"
time.sleep(1)
attachments = cinder.volumes.get(volume_id).attachments
print attachments