python-cyborgclient
python-cyborgclient is a python bindings to the OpenStack Cyborg API. There’s a command-line interface via the OpenStack client plugin. The client implements the OpenStack Cyborg v2 API.
See the OpenStack CLI Reference for information on how to use the OpenStack client with the accelerator plugin. You may also want to look at the OpenStack API documentation.
The project is hosted on Launchpad, where bugs can be filed. The code is hosted on OpenStack. Patches must be submitted using Gerrit.
This code is a fork of Jacobian’s python-cloudservers. If you need API support for the Rackspace API solely or the BSD license, you should use that repository. python-cyborgclient is licensed under the Apache License like the rest of OpenStack.
License: Apache License, Version 2.0
PyPi - package installation
Blueprints - feature specifications
Bugs - issue tracking
Command-line API
Installing this package gets you a plugin for the openstack command-line tool that you can use to interact with the OpenStack Cyborg API.
You’ll need to provide your OpenStack username and password. You can do this with the --os-username, --os-password and --os-project-name params, but it’s easier to just set them as environment variables:
export OS_USERNAME=openstack export OS_PASSWORD=yadayada export OS_PROJECT_NAME=myproject
You will also need to define the authentication url with --os-auth-url. If you are using Keystone, you need to set the OS_AUTH_URL to the keystone endpoint:
export OS_AUTH_URL=http://controller:5000/v3
Since Keystone can return multiple regions in the Service Catalog, you can specify the one you want with --os-region-name (or export OS_REGION_NAME). It defaults to the first in the list returned.
You’ll find complete documentation on the accelerator commands by running openstack accelerator --help
Python API
The Python API is provided through the OpenStack SDK.
See release notes and more at https://docs.openstack.org/python-cyborgclient/latest/.
Metadata
Release files for python-cyborgclient 3.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| python_cyborgclient-3.0.0.tar.gz | 34.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_cyborgclient-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.4 kB
Release files / python_cyborgclient-3.0.0.tar.gz
| Download URL | python_cyborgclient-3.0.0.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dbfc403a1ef5fba511c8793c2df1f40efcaeb2de75740619b568f2905259232
|
|
BLAKE2b-256 checksum How to use checksums |
631872e4b601be82819a8d75c8c2dbf157c3fcdbb9dc255ccd62dc74f6eb4ac7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / python_cyborgclient-3.0.0-py3-none-any.whl
| Download URL | python_cyborgclient-3.0.0-py3-none-any.whl |
|---|---|
| Size | 35.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb26bc0d2327958e47d9552c222450389258edd06ca62720e492e5a80f4cbc7b
|
|
BLAKE2b-256 checksum How to use checksums |
21d96c3b735e83763620b9ce588e93edcfa6c94177b3e9d40b6659396bf7789e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for python-cyborgclient 3.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.