Go to file
Ghanshyam Mann 2b366d693b Remove retired project Senlin job
Senlin project has been retired[1] so removing
its ref and job from sdk gate otherwise it will fail.

Also removing os-client-config-tox-tips job template from check and
gate queue, as the job was redefined [2] to use py311 instead of py38
and py311 is not yet supported on yoga and older branches and the job
started to block the gate.

Changes:
  .zuul.yaml

Centos Stream 8 nodeset is dropped so it's time to drop the
dib-nodepool-functional-openstack-centos-8-stream-src job as well.

[1] https://review.opendev.org/c/openstack/governance/+/919347
[2] I10c1ae5173f2156211a8c7e03c79d4769be605cf

Change-Id: I7e25e30b95ebb8df7984a706ece432813554a395
(cherry picked from commit 8091075e3b)
(cherry picked from commit 8e9e4cc974)
(cherry picked from commit eee309c588)
(cherry picked from commit a3c6499ab8)
(cherry picked from commit 28a207ae6e)
(cherry picked from commit 1cc0a16bd1)
(cherry picked from commit 654915eda7)
2024-08-08 11:07:21 +02:00
2020-08-11 10:50:57 +02:00
2020-05-13 11:35:51 +00:00
2020-05-10 08:29:41 -05:00
2024-08-08 11:07:21 +02:00
2018-04-27 08:56:58 -05:00
2019-09-18 14:34:22 +08:00
2017-02-19 09:46:52 -07:00
2019-03-09 17:25:16 +01:00
2020-06-25 07:36:36 -05:00
2020-03-27 23:49:45 +00:00
2023-07-21 15:41:16 +02: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

Description
Unified SDK for OpenStack
Readme 83 MiB
Languages
Python 99.9%