Client library for OpenStack containing Infra business logic
Go to file
Monty Taylor 4e5a7d160a Support uploading swift objects
In addition to just needing to be able to upload swift objects into
containers, we should be able to sanely interact with swift on general
principle.

Change-Id: I844ea7a26005e72ab037fe733681058944e847fa
2015-01-12 17:19:18 -08:00
doc/source Fix up copyright headers 2015-01-07 12:31:15 -05:00
shade Support uploading swift objects 2015-01-12 17:19:18 -08:00
.coveragerc Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
.gitignore Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
.gitreview Change meta info to be an Infra project 2015-01-07 13:06:42 -05:00
.mailmap Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
.testr.conf Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
CONTRIBUTING.rst Change meta info to be an Infra project 2015-01-07 13:06:42 -05:00
HACKING.rst Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
LICENSE Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
MANIFEST.in Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
README.rst Add example code to README 2014-09-07 17:55:48 -07:00
requirements.txt Support uploading swift objects 2015-01-12 17:19:18 -08:00
setup.cfg Change meta info to be an Infra project 2015-01-07 13:06:42 -05:00
setup.py Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
test-requirements.txt Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
tox.ini Change meta info to be an Infra project 2015-01-07 13:06:42 -05:00

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

cloud = openstack_cloud('mordred')

nova = cloud.nova_client
print nova.servers.list()
s = nova.servers.list()[0]

cinder = cloud.cinder_client
volumes = cinder.volumes.list()
print volumes
volume_id = [v for v in volumes if v.status == 'available'][0].id
nova.volumes.create_server_volume(s.id, volume_id, None)
attachments = []
while not attachments:
    print "Waiting for attach to finish"
    time.sleep(1)
    attachments = cinder.volumes.get(volume_id).attachments
print attachments