Unified SDK for OpenStack
Go to file
Monty Taylor 3ee25df9e7 Drop python3.5 support
Now that we released ussuri, we have a stable release that supports
3.5. That means if needed we can backport changes needed for
zuul and nodepool, so it should be safe to go ahead and drop 3.5
support.

Change-Id: Iaa761cb6f6ab30fa26f6587ac29f11274702e1a3
2020-06-25 07:36:36 -05:00
devstack Finish updating links to point to opendev 2019-04-21 12:31:44 +00:00
doc Drop python3.5 support 2020-06-25 07:36:36 -05:00
examples Merge "Stop subclassing object" 2020-05-13 11:35:51 +00:00
extras Add ansible stable-2.9 job and run 2.8 and 2.9 2020-03-24 08:43:10 -05:00
openstack Add query parameter 'id' for security_groups 2020-06-15 17:44:21 +02:00
playbooks/devstack [tests] Improve devstack/post playbook efficiency 2020-03-25 20:06:51 +00:00
releasenotes Drop python3.5 support 2020-06-25 07:36:36 -05:00
tools Stop subclassing object 2020-05-10 08:29:41 -05:00
.coveragerc Fix coverage configuration and execution 2016-03-14 07:34:53 +00:00
.gitignore Merge tox, tests and other support files 2017-10-04 14:51:08 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:47:46 +00:00
.mailmap Merge tox, tests and other support files 2017-10-04 14:51:08 -05:00
.stestr.conf Merge shade and os-client-config into the tree 2017-11-15 09:03:23 -06:00
.zuul.yaml Drop python3.5 support 2020-06-25 07:36:36 -05:00
babel.cfg setting up the initial layout; move the api proposals to api_strawman 2014-01-24 22:58:25 -06:00
bindep.txt pypy is not checked at gate 2018-04-27 08:56:58 -05:00
CONTRIBUTING.rst fix "How To Contribute" url 2019-09-18 14:34:22 +08:00
create_yaml.sh Fix the network quota tests 2017-02-19 09:46:52 -07:00
docs-requirements.txt Add requirements.txt file for readthedocs 2015-05-21 08:16:44 -07:00
HACKING.rst Fix some typos 2019-03-09 17:25:16 +01:00
LICENSE setting up the initial layout; move the api proposals to api_strawman 2014-01-24 22:58:25 -06:00
lower-constraints.txt Refresh python versions 2020-05-26 10:36:06 +02:00
MANIFEST.in setting up the initial layout; move the api proposals to api_strawman 2014-01-24 22:58:25 -06:00
post_test_hook.sh Update load_balancer for v2 API 2017-07-18 18:05:29 -07:00
README.rst Move the history lesson into the docs 2019-08-01 10:14:21 -04:00
requirements.txt Remove use of six 2020-05-10 08:29:40 -05:00
setup.cfg Drop python3.5 support 2020-06-25 07:36:36 -05:00
setup.py Small cleanups after Python2 drop 2020-03-27 23:49:45 +00:00
SHADE-MERGE-TODO.rst Use discovery instead of config to create proxies 2018-10-06 07:44:29 -05:00
test-requirements.txt Refresh python versions 2020-05-26 10:36:06 +02:00
tox.ini Drop python3.5 support 2020-06-25 07:36:36 -05:00

openstacksdk

openstacksdk is a client library for building applications to work with OpenStack clouds. The project aims to provide a consistent and complete set of interactions with OpenStack's many services, along with complete documentation, examples, and tools.

It also contains an abstraction interface layer. Clouds can do 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, the per-service oriented portions of the SDK are for you. 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 the Cloud Abstraction layer is for you.

More information about its history can be found at https://docs.openstack.org/openstacksdk/latest/contributor/history.html

openstack

List servers using objects configured with the clouds.yaml file:

import openstack

# Initialize and turn on debug logging
openstack.enable_logging(debug=True)

# Initialize cloud
conn = openstack.connect(cloud='mordred')

for server in conn.compute.servers():
    print(server.to_dict())

Cloud Layer

openstacksdk contains a higher-level layer based on logical operations.

import openstack

# Initialize and turn on debug logging
openstack.enable_logging(debug=True)

for server in conn.list_servers():
    print(server.to_dict())

The benefit is mostly seen in more complicated operations that take multiple steps and where the steps vary across providers:

import openstack

# Initialize and turn on debug logging
openstack.enable_logging(debug=True)

# Initialize connection
# Cloud configs are read with openstack.config
conn = openstack.connect(cloud='mordred')

# Upload an image to the cloud
image = conn.create_image(
    'ubuntu-trusty', filename='ubuntu-trusty.qcow2', wait=True)

# Find a flavor with at least 512M of RAM
flavor = conn.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.
conn.create_server(
    'my-server', image=image, flavor=flavor, wait=True, auto_ip=True)

openstack.config

openstack.config will find cloud configuration for as few as 1 clouds and as many as you want to put in a config file. It will read environment variables and config files, and it also contains some vendor specific default values so that you don't have to know extra info to use OpenStack

  • If you have a config file, you will get the clouds listed in it
  • If you have environment variables, you will get a cloud named envvars
  • If you have neither, you will get a cloud named defaults with base defaults

Sometimes an example is nice.

Create a clouds.yaml file:

clouds:
 mordred:
   region_name: Dallas
   auth:
     username: 'mordred'
     password: XXXXXXX
     project_name: 'shade'
     auth_url: 'https://identity.example.com'

Please note: openstack.config will look for a file called clouds.yaml in the following locations:

  • Current Directory
  • ~/.config/openstack
  • /etc/openstack

More information at https://docs.openstack.org/openstacksdk/latest/user/config/configuration.html

Links