2c753699ac
We're creating an error message string that contains the shade message and the underlying message AND we're passing the underlying message in so that we append it as part of the Inner Exception string. So we wind up with something like: Error in creating volume: Invalid input received: 'size' parameter must be between 75 and 1024 (HTTP 400) (Request-ID: req-ae3f3489-997b-4038-8c9f-efbe7dd73a70) (Inner Exception: Invalid input received: 'size' parameter must be between 75 and 1024) Which is a bit insane. With this change, the above becomes: Error in creating volume (Inner Exception: Invalid input received: 'size' parameter must be between 75 and 1024 (HTTP 400) (Request-ID: req-d4da66b2-41eb-44c8-85f1-064454af5a1c)) And if the shade_exceptions context manager is invoked with no message, the output will be: Invalid input received: 'size' parameter must be between 75 and 1024 (HTTP 400) (Request-ID: req-d4da66b2-41eb-44c8-85f1-064454af5a1c)) Change-Id: I6bd70b70585722d2266ef08496b6860aeeab1824 |
||
|---|---|---|
| doc/source | ||
| extras | ||
| 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 | ||
Introduction
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. :
import shade
# Initialize and turn on debug loggin
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)