rbc-tools are command line tools for managing RedBridge Cloud <https://cloud.redbridge.se/>.
Using rbc-tools you can manage instances, networks and othe compute resources in RBC.
The tools are tested on MacOS X and Linux only at the moment, but should also work on Windows in a cygwin environment.
The tools are in a early beta stage so please report any bugs to support@redbridge.se or as issues on github <https://github.com/redbridge/rbc-tools/issues>
Getting started
Register for an account on RedBridge Portal <https://portal.redbridge.se/account/signup/>
Get your access key and secret key from your account page in the portal.
Create a ~/.rbc/rbc.cfg file (in a terminal):
mkdir -p ~/.rbc cat > ~/.rbc/rbc.cfg <<EOF [main] apikey = <your api key as found in the Portal> secretkey = <your secret key as found in the Portal> endpoint = api.rbcloud.net EOF
Install rbc-tools using pip (or easy_install)
Now you should have access to a number of command line scripts, prefixed with rbc-*
Note that you can also set api key and secret key by using environment variables:
export RBC_APIKEY=XXXXX; export RBC_SECRETKEY=XXXX
Examples
Create a ssh key pair:
rbc-sshkeys generate my-keypair > ~/.ssh/my-keypair_id_rsa
To deploy 3 small instances in the RedBridge Cloud, using a ssh key:
rbc-instances deploy -i 3 -g test -t rbc/ubuntu-14.04-server-cloudimg-amd64-20GB-201461111 -o small -w default -s my-keypair my-instances
Development
Development of rbc-tools takes place on github (https://github.com/redbridge/rbc-tools).
History
0.3.4 (2015-05-07)
Fix issue when tags are not used
0.3.3 (2015-05-04)
Add an ansible inventory to rbc-tools
0.3.2 (2015-04-02)
Do not fail on network create if the command timeouts.
0.3.0 (2015-02-10)
Use post for instances, this makes it possible to use up to 32K of user data
0.1.18 (2014-08-07)
Fix broken network list when using VPC’s
0.1.17 (2014-07-31)
First pypi release
0.1.0 (2014-07-31)
Initial release.
Credits
“rbc-tools” is written and maintained by RedBridge AB.
Contributors
cldmnky <https://github.com/cldmnky>
eal <https://github.com/eal>
Please add yourself here alphabetically when you submit your first pull request.
1 maintainer
Metadata
1 maintainer
Release files for rbc-tools 0.3.4
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 | |
|---|---|---|---|---|
| rbc-tools-0.3.4.tar.gz | 17.6 kB | Without provenance | Details |
Release files / rbc-tools-0.3.4.tar.gz
| Download URL | rbc-tools-0.3.4.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c6a370a88f82a13e26ca76b0749efcb7c0630caa1eb5a8b11ef3bdd69316cc7
|
|
BLAKE2b-256 checksum How to use checksums |
06b61f2c8d41824ffd77f44120b767c6d02a1b04cc404d4cf1b3ff0a6fc26bf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rbc-tools 0.3.4
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.
