0ecbb22547
I was trying to bring up a host on vexxhost using the image name "Ubuntu 16.04.1 LTS [2017-03-02]". As described in the change, because this gets run through fnmatch() directly it makes everything barf as "[2017-03-02]" gets matched as an incorrect glob character class. This is a little tricky because all the external list_*, search_*, get_* API functions basically pass name_or_id through directly. None of them have ever explicitly said that you could use globbing, although it probably would have worked. Any such use would have been relying on implementation details of the _util functions, and I feel like the fact it's _underscore_utils means that you probably had fair warning not to do that. And obviously the "filters" argument is meant for this type of filtering. Additionally, fnmatch() says that it normalises case depending on OS filename case-sensitivity, which seems like incorrect behaviour for these functions which are not actually related to filenames. Thus I believe the matching should be just be a straight string comparison. I have added a test for this, but we also have to remove the tests for globbing behaviour as they are incorrect now. Change-Id: Id89bbf6306adebe96c1db417a4b8b5ae51023af0
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)