Client library for OpenStack containing Infra business logic
Go to file
Monty Taylor 0a1c7c84a3 Support private address override in inventory
ansible inventory supports a command line switch --private which
overrides the clouds.yaml setting. Support passing it in.

Change-Id: I74bf98be26b605a5e9ac74ab478f421c39616d74
2015-10-21 08:34:39 +09:00
doc/source Add a developer coding standards doc 2015-08-12 16:25:05 -04:00
extras Add script to document deleting private networks 2015-10-12 09:50:15 -04:00
shade Support private address override in inventory 2015-10-21 08:34:39 +09:00
.coveragerc Start using keystoneauth for keystone sessions 2015-09-21 11:12:21 -05:00
.gitignore Tell git to ignore .eggs directory 2015-10-12 12:54:39 -04: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 Add initial compute functional tests to Shade 2015-03-13 13:40:46 +00:00
CONTRIBUTING.rst Add minor OperatorCloud documentation 2015-04-30 15:12:59 -04: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 Clarify future changes in docs 2015-08-04 09:11:01 -04:00
requirements.txt Merge "Update python-troveclient requirement" 2015-10-06 19:13:18 +00:00
setup.cfg Add inventory command to shade 2015-06-05 13:46:59 -04:00
setup.py Initial cookiecutter repo 2014-08-30 17:05:28 -07:00
test-requirements.txt Update pbr version pins 2015-05-28 10:52:59 -04:00
tox.ini Return IPv6 address for interface_ip on request 2015-10-02 11:07:28 -04:00

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
import time

# Initialize cloud
# Cloud configs are read with os-client-config
cloud = shade.openstack_cloud(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
# This will go away at some point in time and should be considered only
# usable for temporary poking
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