To set configuration options, copy the config.cfg.example
file to config.cfg
and insert correct values.
You will need the python-heatclient
installed to use the stack
subcommand.
To launch a stack execute:
openstack stack create --template /path/to/the/tester/billable_stack.yaml --parameter flavor=<flavor> --parameter key=<your-key> --parameter public_network=<external-network> <your-stack-name>
Note
|
Only key is a required parameter - the remaining ones have default values working on our platform.
Instead of writing passing the parameters from the command line, you can put them in a file and use the --environment flag.
|
This will create a Heat stack with all the billable resources.
Place the names of meters you want to check in the required_meters.txt
- one in each line and run the main script passing the name or the ID of the stack you’ve created in the previous step:
python show_billable_resources.py <your-stack-name> [--verbose]
You will see a list of meters retrieved for all the billable resources in your stack and the timestamp of the latest meter. Compare this output with you list of meters to see whether there are any missing entries.
A module for checking consistency of data retrieved from the database and through the Ceilometer’s meters
APIs is available. The module also extracts event-based samples.
To run the check, execute:
python consistency_check_compute.py <instance-id> [--verbose]
The argument is the UUID of the instance one wants to check consistency of data for. This works for currently existing instances as well as for recently removed ones.
Note
|
This module requires credentials for Mongo DB and they need to be provided in the config.cfg file.
|