Chaos Toolkit Extension for Google Cloud Engine
THIS PACKAGE IS NOW DEPRECATED. Please use the google-cloud-platform extension instead.
This project is a collection of actions and probes, gathered as an extension to the Chaos Toolkit. It targets the Google Cloud Engine platform.
Install
This package requires Python 3.5+
To be used from your experiment, this package must be installed in the Python environment where chaostoolkit already lives.
$ pip install -U chaostoolkit-google-cloud
Usage
To use the probes and actions from this package, add the following to your experiment file:
{
"type": "action",
"name": "swap-nodepool-for-a-new-one",
"provider": {
"type": "python",
"module": "chaosgce.nodepool.actions",
"func": "swap_nodepool",
"secrets": ["gce"],
"arguments": {
"body": {
"nodePool": {
"config": {
"oauthScopes": [
"gke-version-default",
"https://www.googleapis.com/auth/devstorage.read_only",
"https://www.googleapis.com/auth/logging.write",
"https://www.googleapis.com/auth/monitoring",
"https://www.googleapis.com/auth/service.management.readonly",
"https://www.googleapis.com/auth/servicecontrol",
"https://www.googleapis.com/auth/trace.append"
]
},
"initialNodeCount": 3,
"name": "new-default-pool"
}
}
}
}
}
That's it!
Please explore the code to see existing probes and actions.
Configuration
Project and Cluster Information
You can pass the context via the configuration section of your experiment:
{
"configuration": {
"gce_project_id": "...",
"gce_cluster_name": "...",
"gce_region": "...",
"gce_zone": "..."
}
}
Note that most functions exposed in this package also take those values directly when you want specific values for them.
Credentials
This extension expects a service account with enough permissions to perform its operations. Please create such a service account manually (do not use the default one for your cluster if you can, so you'll be able to delete that service account if need be).
Once you have created your service account, either keep the file on the same
machine where you will be running the experiment from. Or, pass its content
as part of the secrets section, although this is not recommended because your
sensitive data will be quite visible.
Here is the first way:
{
"secrets": {
"gce": {
"service_account_file": "/path/to/sa.json"
}
}
}
While the embedded way looks like this:
{
"secrets": {
"gce": {
"service_account_info": {
"type": "service_account",
"project_id": "...",
"private_key_id": "...",
"private_key": "...",
"client_email": "...",
"client_id": "...",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/...."
}
}
}
}
Putting it all together
Here is a full example:
{
"version": "1.0.0",
"title": "...",
"description": "...",
"configuration": {
"gce_project_id": "...",
"gce_cluster_name": "...",
"gce_region": "...",
"gce_zone": "..."
},
"secrets": {
"gce": {
"service_account_file": "/path/to/sa.json"
}
},
"method": [
{
"type": "action",
"name": "swap-nodepool-for-a-new-one",
"provider": {
"type": "python",
"module": "chaosgce.nodepool.actions",
"func": "swap_nodepool",
"secrets": ["gce"],
"arguments": {
"body": {
"nodePool": {
"config": {
"oauthScopes": [
"gke-version-default",
"https://www.googleapis.com/auth/devstorage.read_only",
"https://www.googleapis.com/auth/logging.write",
"https://www.googleapis.com/auth/monitoring",
"https://www.googleapis.com/auth/service.management.readonly",
"https://www.googleapis.com/auth/servicecontrol",
"https://www.googleapis.com/auth/trace.append"
]
},
"initialNodeCount": 3,
"name": "new-default-pool"
}
}
}
}
}
]
}
Contribute
If you wish to contribute more functions to this package, you are more than welcome to do so. Please, fork this project, make your changes following the usual PEP 8 code style, sprinkling with tests and submit a PR for review.
The Chaos Toolkit projects require all contributors must sign a Developer Certificate of Origin on each commit they would like to merge into the master branch of the repository. Please, make sure you can abide by the rules of the DCO before submitting a PR.
Develop
If you wish to develop on this project, make sure to install the development dependencies. But first, create a virtual environment and then install those dependencies.
$ pip install -r requirements-dev.txt -r requirements.txt
Then, point your environment to this directory:
$ python setup.py develop
Now, you can edit the files and they will be automatically be seen by your
environment, even when running from the chaos command locally.
Test
To run the tests for the project execute the following:
$ pytest
Metadata
Release files for chaostoolkit-google-cloud 0.2.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 | |
|---|---|---|---|
| chaostoolkit-google-cloud-0.2.3.tar.gz | 11.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chaostoolkit_google_cloud-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.8 kB
Release files / chaostoolkit-google-cloud-0.2.3.tar.gz
| Download URL | chaostoolkit-google-cloud-0.2.3.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
183b5e6face05eff6a9af3eb0713dca37cd21f9dbc65af32a98f04df94d0c768
|
|
BLAKE2b-256 checksum How to use checksums |
551bdbb1254161475e6332acfafd769fbd9ea8a34f4a545fb1668f8e630803c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.6.3 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.5.6
|
Release files / chaostoolkit_google_cloud-0.2.3-py3-none-any.whl
| Download URL | chaostoolkit_google_cloud-0.2.3-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
996b4bab76dabc082e9d167dde730bdd231b18056613ba2adbf670ed7276587d
|
|
BLAKE2b-256 checksum How to use checksums |
3e41fb503a2e419c8dc75fd07bea084c69d5b5bb5253bc327c73d80ed3af70ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.6.3 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.5.6
|