# OpenSink: All the OpenStack APIs in one place
Do you sometimes need to write scripts that interact with the OpenStack API? Do you always find yourself spending more time trying to remember how to get a valid Nova client than actually writing your scripts?
This is for you.
## Usage
Assuming that you have the standard suite of OS_* environment variable available, then using opensink is as simple as:
>>> import opensink.openstack >>> clients = opensink.openstack.OpenStack()
Need a list of users?
>>> c.keystone.users.find(name='lars')
<User {u'username': u'lars', u'name': u'lars', u'enabled': True,
u'tenantId': u'f4e7e158cb154de5ab503bd7096b8981', u'id':
u'065e9427a1f14f9398082e5bed3d3fb7', u'email': u'lars@oddbit.com'}>
Or a list of servers?
>>> clients.nova.servers.list() [<Server: larstest-server-23dwogjbq3ux>, <Server: cirros>]
Want to create a Cinder volume?
>>> clients.cinder.volumes.create(1) <Volume: e61ffb18-7d97-4dde-ba70-b256df7b709f>
How about a list of resources in your heat stack?
>>> [ r.to_dict()['resource_name'] ... for r in clients.heat.resources.list(id)] [u'server_floating', u'secgroup_all_open', u'server_eth0', u'server']
Metadata
Release files for opensink 0.3
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 | |
|---|---|---|---|---|
| opensink-0.3.tar.gz | 3.2 kB | Without provenance | Details |
Release files / opensink-0.3.tar.gz
| Download URL | opensink-0.3.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e18b6f0d1597bd0818d419ccfab5f1e3fc801fc6179d01f82a232bc2d0f2101
|
|
BLAKE2b-256 checksum How to use checksums |
86dd4f5328a7ad83143d59b5b53de74bc7f03cd582b808e0fcc8dc6fcd6897da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for opensink 0.3
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.