📦
CHI-in-a-box
  • What is CHI-in-a-Box?
  • Before You Begin
    • Assumed Knowledge
    • Hosts and Services
    • Network Overview
    • CC-Ansible
    • The site configuration
      • inventory
      • defaults.yml
      • passwords.yml
      • certificates/
      • node_custom_config/ (optional)
      • post-deploy.yml (optional)
    • How Deployment Works
    • Security considerations
  • Setup Guides
    • Evaluation Site
      • Bring up the Control Plane
    • Production Baremetal
      • Baremetal QuickStart
      • Host Networking Configuration
    • Troubleshooting
      • Networking
    • Verification Checklist
    • Dev-in-a-Box
    • Edge-in-a-Box
  • Reference
    • Chameleon Identity Federation
    • Ironic Flat Networking
    • Ironic Multi-Tenant Networking
    • Glance Image Storage
    • Resource Reservation
      • Default Resource Properties
    • Monitoring
      • IPMI Metrics
      • SNMP Metrics
  • Example Deployments
    • ARM/x86 mixed architecture
    • Edge computing/container testbed
  • Operations
    • Hardware management
    • Certificate management
    • Chameleon tools
      • Hammers 🔨
        • maintenance_reservation
      • Disk image subscription
      • Usage reporting
    • Troubleshooting
      • Known issues
        • Neutron (networking)
        • Nova (KVM)
        • Ironic (bare metal)
      • Instance networking diagnostics
      • Security incident triage
      • Troublesome Hardware
    • Alert runbooks
      • Cron Job No Recent Success
      • Instance Failure
      • Image Cache Space
      • Ironic Node Error State
      • Jupyter Server Launch Failure
      • MySQL Host Down
      • MySQL Replication Error
      • Node Exporter Down
      • Node Network Bridge Down
      • Node Network Bridge Low Traffic
      • Nova Ironic Instance Launch Failure
      • OpenStack API Down
      • PeriodicTask No Recent Success
      • Portal Down
      • Precis Parsed Events Low
      • Provider Conflict
      • Runbook Template
    • User support guide
    • Upgrading to a new Release
  • Development
    • Developing OpenStack Services
    • Dev-in-a-box
Powered by GitBook
On this page
  • MariaDB backup
  • Configuration
  • Troubleshooting
  • Grafana and KPI report
Edit on GitHub
  1. Operations
  2. Chameleon tools

Usage reporting

PreviousDisk image subscriptionNextTroubleshooting

Last updated 2 years ago

This feature can only be enabled by the .

The usage reporting is used to monitor the daily bare metal node usage of an associate site. The tool will read data from the backups of the OpenStack databases, process the data, and store the usage data into a database named chameleon_usage (co-located with the OpenStack databases). The tool will also upload the usage data to a centralized location at TACC, so that the Chameleon Team can monitor the node usage from all Chameleon sites.

MariaDB backup

The usage reporting reads data from the OpenStack database backups. Currently, two backup types are supported - and . If the MariaDB is deployed by kolla-ansible (default in CHI-in-a-Box), kolla-ansible MariaDB backup is enabled by default. The backups will be stored in a docker volume named mariadb_backup. Please also check that mariadb_backup_database_password is set in the passwords.yml. If you are using the , your OpenStack database will be backed up using the mysqldump and the default backup location is /var/db/backup. To set a different backup location, overwrite backup_location in the site defaults.yml.

The MariaDB backup configuration is included in the post-deploy. You can also manually configure the MariaDB backup by running the backups playbook.

cc-ansible reconfigure --tags mariadb # if mariadb is deployed by kolla-ansible
cc-ansible --playbook playbooks/backups.yml

For kolla-ansible MariaDB backup, you should see a mariadb_backup_<basename of site_config_dir> systemd on the deployment node.

systemctl list-timers 'mariadb_backup_*'

For both backup types, you should see a mariadb_backup systemd on the control node.

systemctl list-timers 'mariadb_backup'

By default, the backup rotation is 29 days, but you can turn this number by overwriting mariadb_backup_file_age in the site defaults.yml.

Configuration

The MariaDB backup is required for the usage reporting. The usage reporting is by default installed onto the control node in the site configuration Ansible inventory.

The usage reporting is disabled by default. To enable, set enable_usage_reporting: yes in the site defaults.yml. Two passwords are required in the passwords.yml - chameleon_usage_mysql_password and chameleon_usage_site_password. The chameleon_usage_site_password is an authentication password from the Chameleon Team: once contact and resource registration are complete, you will get this password from the Chameleon Team.

The usage reporting configuration is included in the post-deploy. You can also manually configure by running the chameleon_usage playbook.

cc-ansible --playbook playbooks/chameleon_usage.yml
systemctl list-timers 'usage_node'

Troubleshooting

The usage reporting logs are captured by the systemd journal.

journalctl -u usage_node

Grafana and KPI report

We currently have a Grafana dashboard and a weekly KPI report email set up for the node usage of all Chameleon sites. Please let us know if you are interested in getting access to the dashboard and email.

You can check the scheduled task via the systemd .

Chameleon associate sites
kolla-ansible MariaDB backup
mysqldump
external MariaDB
timer
timer
timers