Uses the rackspace APIs to allow for scaling based on aggregate metrics
across a cluster.
Can be used and installed on the auto-scale group members or on a
dedicated management instance.
- GitHub repository
- PyPI package
[Stories in Ready] [Documentation Status] [Travis CI status]
[Coverage Status]
Installation
pip install rax-autoscaler
Configuration
Read the Docs
What's New
V0.4 is here with a brand new plugin raxmon-autoscale, check it out in
the documentation above. Along for the ride are a host of improvements,
and fixes. Read the commit log if you have any questions and please
create an issue if you see any regressions.
Upgrading from 0.2
V0.3 is a major change from 0.2 and as such there are many breaking
changes in the configuration file.
Here is what you need to fix to upgrade successfully.
The monitoring information is now a plugin and needs to be moved to the
plugin section. The only monitoring plugin available in 0.2 was raxmon
so you should specify the raxmon plugin and just move the check_type,
check_config, metric_name, thresholds down.
Old Config
"autoscale_groups": {
"group0": {
"group_id": "group id",
"scale_up_policy": "scale up policy id",
"scale_down_policy": "scale down policy id",
"check_type": "agent.load_average",
"check_config": {},
"metric_name": "1m",
"scale_up_threshold": 0.6,
"scale_down_threshold": 0.4,
"webhooks": {
"scale_up": {
"pre": [
"url",
"url"
],
"post": [
"url"
]
},
"scale_down": {
"pre": [
"url",
"url"
],
"post": [
"url"
]
}
}
}
}
New Config
"autoscale_groups": {
"group0": {
"group_id": "704a2260-f4b9-46a9-be83-dbfb19919ee0",
"scale_up_policy": "74588ebe-7ca7-4950-9b86-e622a11295b6",
"scale_down_policy": "b22f4fce-132f-40af-b8c6-0e22704b1241",
"webhooks": {
"scale_up": {
"pre": [
"url",
"url"
],
"post": [
"url"
]
},
"scale_down": {
"pre": [
"url",
"url"
],
"post": [
"url"
]
}
},
"plugins":{
"raxmon":{
"scale_up_threshold": 0.6,
"scale_down_threshold": 0.4,
"check_type": "agent.load_average",
"load_balancers": [17443]
}
}
}
}
Contributing
- Fork rax-autoscaler repository, and clone it on your laptop
- Create _your feature_ branch from _devel_ branch:
git checkout -b my-new-feature origin/devel
- Commit, comment, push to your fork on GitHub, and create new _Pull
Request_
Requirements
You might want to install pip packages in your Python virtualenv:
pip install -r requirements-dev.txt
License
Copyright 2014 Rackspace US, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Metadata
Release files for rax-autoscaler 0.4.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 | Actions |
|---|---|---|---|---|
| rax-autoscaler-0.4.0.tar.gz | 26.8 kB | Without provenance | Details for rax-autoscaler-0.4.0.tar.gz |
Release files / rax-autoscaler-0.4.0.tar.gz
| Download URL | rax-autoscaler-0.4.0.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7addf8afbd2a9f81217c15b8504f7dd569ef9e02230a6aad8bca9379c08206f4
|
|
BLAKE2b-256 checksum How to use checksums |
a9ff7e6ff830163517392a2355d948a5a098eacf6176fc67bc0a0ce66bd1fc1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rax-autoscaler 0.4.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.