A simple, yet powerful CloudStack API client for python and the command-line.
- Async support.
- All present and future CloudStack API calls and parameters are supported.
- Syntax highlight in the command-line client if Pygments is installed.
- BSD license.
pip install cs # with the colored output pip install cs[highlight] # with the async support pip install cs[async] # with both pip install cs[async,highlight]
In Python:
from cs import CloudStack
cs = CloudStack(endpoint='https://cloudstack.example.com/client/api',
key='cloudstack api key',
secret='cloudstack api secret')
vms = cs.listVirtualMachines()
cs.createSecurityGroup(name='web', description='HTTP traffic')The key and secret are optional. Leave them out to send
unauthenticated requests, for example against the CloudStack integration
port, which rejects requests carrying an API key or signature:
cs = CloudStack(endpoint='http://localhost:8096/client/api')From the command-line, this requires some configuration:
cat $HOME/.cloudstack.ini[cloudstack]
endpoint = https://cloudstack.example.com/client/api
key = cloudstack api key
secret = cloudstack api secret
# Optional ca authority certificate
verify = /path/to/certs/ca.crt
# Optional client PEM certificate
cert = /path/to/client.pem
# If you need to pass the certificate and key as separate files
cert_key = /path/to/client_key.pemThen:
$ cs listVirtualMachines{
"count": 1,
"virtualmachine": [
{
"account": "...",
...
}
]
}$ cs authorizeSecurityGroupIngress \
cidrlist="0.0.0.0/0" endport=443 startport=443 \
securitygroupname="blah blah" protocol=tcpThe command-line client polls when async results are returned. To disable
polling, use the --async flag.
To find the list CloudStack API calls go to http://cloudstack.apache.org/api.html
Configuration is read from several locations, in the following order:
- The
CLOUDSTACK_ENDPOINT,CLOUDSTACK_KEY,CLOUDSTACK_SECRETandCLOUDSTACK_METHODenvironment variables, (CLOUDSTACK_KEYandCLOUDSTACK_SECRETare optional: leave them unset for unauthenticated requests, e.g. against the integration port) - A
CLOUDSTACK_CONFIGenvironment variable pointing to an.inifile, - A
CLOUDSTACK_VERIFY(optional) environment variable pointing to a CA authority cert file, - A
CLOUDSTACK_CERT(optional) environment variable pointing to a client PEM cert file, - A
CLOUDSTACK_CERT_KEY(optional) environment variable pointing to a client PEM certificate key file, - A
cloudstack.inifile in the current working directory, - A
.cloudstack.inifile in the home directory.
To use that configuration scheme from your Python code:
from cs import CloudStack, read_config
cs = CloudStack(**read_config())Note that read_config() can raise SystemExit if no configuration is
found.
CLOUDSTACK_METHOD or the method entry in the configuration file can be
used to change the HTTP verb used to make CloudStack requests. By default,
requests are made with the GET method but CloudStack supports POST requests.
POST can be useful to overcome some length limits in the CloudStack API.
CLOUDSTACK_TIMEOUT or the timeout entry in the configuration file can
be used to change the HTTP timeout when making CloudStack requests (in
seconds). The default value is 10.
CLOUDSTACK_RETRY or the retry entry in the configuration file
(integer) can be used to retry list and queryAsync requests on
connection errors. The default value is 0, meaning no retry.
CLOUDSTACK_RETRY_BACKOFF or the retry_backoff entry in the configuration
file (number of seconds, float) sets how long to wait before the first retry.
The delay doubles for every further retry, up to 30 seconds. The default value
is 0.5.
CLOUDSTACK_JOB_TIMEOUT or the job_timeout entry in the configuration file
(integer, seconds) can be used to set how long an async call is polled, assuming
fetch_result is set to true. The default value is None, it waits forever.
CLOUDSTACK_POLL_INTERVAL or the poll_interval entry in the configuration file (number of seconds, float) can be used to set how frequently polling an async job result is done. The default value is 2.
CLOUDSTACK_EXPIRATION or the expiration entry in the configuration file
(integer) can be used to set how long a signature is valid. By default, it picks
10 minutes but may be deactivated using any negative value, e.g. -1.
CLOUDSTACK_DANGEROUS_NO_TLS_VERIFY or the dangerous_no_tls_verify entry
in the configuration file (boolean) can be used to deactivate the TLS verification
made when using the HTTPS protocol.
Boolean settings, such as dangerous_no_tls_verify and trace, accept
true/false, yes/no, on/off and 1/0.
TLS verification is always on, unless dangerous_no_tls_verify is set. The
verify setting only selects a CA bundle: in Python, verify=False is the
same as leaving it out and does not turn the verification off:
CloudStack(endpoint=..., verify='/path/to/ca.crt') # custom CA bundle
CloudStack(endpoint=..., dangerous_no_tls_verify=True) # no verificationMultiple credentials can be set in .cloudstack.ini. This allows selecting
the credentials or endpoint to use with a command-line flag.
[cloudstack]
endpoint = https://some-host/api/v1
key = api key
secret = api secret
[region-example]
endpoint = https://cloudstack.example.com/client/api
key = api key
secret = api secretUsage:
$ cs listVirtualMachines --region=region-example
Optionally CLOUDSTACK_REGION can be used to overwrite the default region cloudstack.
For the power users that don't want to put any secrets on disk,
CLOUDSTACK_OVERRIDES let you pick which key will be set from the
environment even if present in the ini file.
CloudStack paginates requests. cs is able to abstract away the pagination
logic to allow fetching large result sets in one go. This is done with the
fetch_list parameter:
$ cs listVirtualMachines fetch_list=true
Or in Python:
cs.listVirtualMachines(fetch_list=True)
Once in a while, it could be useful to understand, see what HTTP calls are made
under the hood. The trace flag (or CLOUDSTACK_TRACE) does just that:
$ cs --trace listVirtualMachines $ cs -t listZones
cs provides the AIOCloudStack class for async/await calls. It supports
the same options as CloudStack.
import asyncio
from cs import AIOCloudStack, read_config
async def main():
async with AIOCloudStack(**read_config()) as cs:
vms = await cs.listVirtualMachines(fetch_list=True)
print(vms)
asyncio.run(main())Used with async with, all calls share one HTTP session and its connection
pool. Without it, every call opens and closes its own session. An existing
aiohttp.ClientSession can be passed as session=. It is left open, and
its own connector settings apply instead of verify and cert.
import asyncio
from cs import AIOCloudStack, read_config
machine = {"zoneid": ..., "serviceofferingid": ..., "templateid": ...}
async def main():
async with AIOCloudStack(**read_config()) as cs:
results = await asyncio.gather(*(
cs.deployVirtualMachine(name=f"vm-{i}", **machine, fetch_result=True)
for i in range(5)
))
# Destroy all of them, but skip waiting on the job results
await asyncio.gather(*(
cs.destroyVirtualMachine(id=result["virtualmachine"]["id"])
for result in results
))
asyncio.run(main())This project uses uv for dependency management and ruff for linting and formatting.
# Create the virtualenv and install all dependencies
uv sync --all-extras
# Run the test suite (with a coverage report)
uv run pytest
# Run a subset of the tests, without the coverage threshold
uv run pytest --no-cov tests/test_client.py -k signature
# Run the test suite against another Python version
uv run --python 3.10 pytest
# Lint and format
uvx ruff check .
uvx ruff format .
Bump the version in cs/version.py, then create a GitHub release: the
Upload Python Package workflow builds and publishes to PyPI. To build
and publish manually:
rm -rf dist
uv build
uv publish
- CloudStack API: http://cloudstack.apache.org/api.html