Name: rackspace_cloudmonitoring_migration_tool
Owner: racker
Description: null
Created: 2012-09-10 22:52:32.0
Updated: 2013-11-08 17:01:30.0
Pushed: 2013-04-09 21:15:23.0
Homepage: null
Size: 1091
Language: Python
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Copy config.json.dist to config.json and set these configation settings:
To run the migration script in manual mode (you are asked to confirm every action), run:
./migrate.py -c /path/to/config.json migrate
To run the migration script in automatic mode (You are only prompted if a check or alarm test fails), run:
./migrate.py -c /path/to/config.json --auto migrate
To migrate all Entities, Checks, Notification Endpoints, and Alarms automatically and without testing, run:
./migrate.py -c /path/to/config.json --auto --no-test migrate
To delete ALL Rackspace cloud monitoring resources, run:
./migrate.py -c /path/to/config.json clean
Nodes in Cloudkick are assigned a primary IPv4 address, which is the forced target of all external checks (HTTP, SSH, etc).
There are no such limitation in Rackspace Cloud Monitoring. IPv4 and IPv6 addresses can be assigned to entities and targeted by any combination of checks.
This tool will copy Cloudkick behavior, and target all external checks to the node's primary IPv4 address.
Rackspace Cloud Monitoring agents are explicity associated with an entity via the agent_id attribute. It does not automatically happen as it did with Cloudkick agents.
If you want to be able to test migrated agent Checks with this tool, you'll need to set the agent up beforehand.
By default, this script will assume that the agent_id is the name of the node in Cloudkick.
The Cloudkick custom plugin output format is compatible with the Rackspace Cloud Monitoring Agent.
You may simply copy your Cloudkick agent custom plugins directory to the Rackspace Cloud Monitoring agent plugins directory and this tool will properly migrate the check and set up an alarm.
The following check types are migrated automatically by this tool:
The following check types are supported in Rackspace Cloud Monitoring, but could not be automatically migrated:
The following check types are not supported in Rackspace Cloud Monitoring and will not be migrated and should be replaced with a custom plugin: