68a8d513dd
The default glance image list pagination seems to be about 20, which means for v2 you really need to deal with pagination every time. It also seems that the limit parameter does _not_ allow you to get more items than the server default, so you can't just say "limit 100000" and be done with it. In order to accomplish this, we need to have the adapter stop trying to return only the image list when there are other top level keys (so the code can read the next link) and then do a loop requesting the next link. To make us even happier, glance returns the next link as '/v2/images' but we have already set the adapter to 'https://example.com/v2' due to version discovery. Since we're setting the endpoint_override on the adapater, it treats that as the root, leaving us with https://example.com/v2/v2/images. To deal with that, introduce a 'raw' adapter which is bound to whatever is in the catalog, rather than whatever we found through version discovery. Change-Id: I030147e0275d0c4ee89588e21b5970f7d81800d3 Story: 2000837 |
||
|---|---|---|
| devstack | ||
| doc/source | ||
| extras | ||
| releasenotes/notes | ||
| shade | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Introduction
shade is a simple client library for interacting with 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. :
import shade
# Initialize and turn on debug logging
shade.simple_logging(debug=True)
# Initialize cloud
# Cloud configs are read with os-client-config
cloud = shade.openstack_cloud(cloud='mordred')
# Upload an image to the cloud
image = cloud.create_image(
'ubuntu-trusty', filename='ubuntu-trusty.qcow2', wait=True)
# Find a flavor with at least 512M of RAM
flavor = cloud.get_flavor_by_ram(512)
# Boot a server, wait for it to boot, and then do whatever is needed
# to get a public ip for it.
cloud.create_server(
'my-server', image=image, flavor=flavor, wait=True, auto_ip=True)