The instances of CAOS are hosted on cld-caos and the dashboards are reachable on:

• Cloud Area Padovana: https://cld-caos.cloud.pd.infn.it
• Cloud Veneto: https://cld-caos.cloud.pd.infn.it/CloudVeneto
• EGI Fed-Cloud: https://cld-caos.cloud.pd.infn.it/EgiCloud

The links are reachable only from inside the Padova LAN. To connect from outside a SSH tunnel must be opened, e.g:

$ ssh -v -o TCPKeepAlive=yes -N -L 4000:cld-caos.cloud.pd.infn.it:443 gate.pd.infn.it

and then go to:

• Cloud Area Padovana: https://localhost:4000
• Cloud Veneto: https://localhost:4000/CloudVeneto/
• EGI Fed-Cloud: https://localhost:4000/EgiCloud/

The instances are managed by docker (through docker-compose).

The templates are located in the following directories:

• Cloud Area Padovana: /root/caos/cap-prod
• Cloud Veneto: /root/caos/cedc-prod
• EGI Fed-Cloud: /root/caos/egi-prod

Inside each directory a docker-compose.yml file contains the configuration for the particular instance.

The instances store data in the following MySQL databases:

• Cloud Area Padovana: 192.168.60.10:6306/caos_prod
• Cloud Veneto: 192.168.60.180:5306/caos_prod
• EGI Fed-Cloud: 192.168.114.10:3306/caos_prod

Instances can be started by docker-compose up, for example:

# cd /root/caos/cap-prod
# docker-compose up -d

Instances can be stopped by docker-compose down, for example:

# cd /root/caos/cap-prod
# docker-compose down

To update an instance, e.g. after changing the version of an image or changing configuration variables, issue the following command

docker-compose up -d

In the collector section of the docker-compose.yml file, set the environment variable

CAOS_COLLECTOR_OPENSTACK_VERSION=ocata

This enables the correct collection of the wall clock time.

Create a database, for example:

CREATE DATABASE caos;
 
GRANT ALL ON caos.* TO 'caos'@'192.168.60.%' IDENTIFIED BY '***';
GRANT ALL ON caos.* TO 'caos'@'localhost' IDENTIFIED BY '***';

openstack user create --password=*** caos
openstack role add --project admin --user caos admin

Then check connectivity to the DB and eventually migrate the schema with

docker-compose run --rm tsdb dbcheck
docker-compose run --rm tsdb migrate

use ceilometer

db.createUser({
  user: "caos",
  pwd: "***",
  roles: [
    { role: "read", db: "ceilometer" }
  ]
})

HTTPS/SSL communication is managed by the nginx proxy. The certificates (self-signed) are located at:

• certificate: /root/caos/nginx/certificate.crt
• private key: /root/caos/nginx/privateKey.key

After changing the above files, remember to restart the proxy:

# cd /root/caos/nginx
# docker-compose restart

The TSDB, collector and dashboard can be easily configured through environment variables, whose meaning is explained below.

The following variables are used if CAOS_COLLECTOR_CEILOMETER_BACKEND is set to mongodb:

The following variables are used if CAOS_COLLECTOR_CEILOMETER_BACKEND is set to gnocchi:

CPU and RAM allocation ratio can be set in the file caos-collector.conf.yaml. For example for cap-prod the file /root/caos/cap-prod/caos-collector.conf.yaml include a section like:

schedulers:
  ...
 
  hypervisors:
    misfire_grace_time: 300
    minute: '*/30'
    jobs:
      - 'hypervisors_state --allocation-ratio="{cpu: {default: 4, cld-np-09.cloud.pd.infn.it: 1 }, ram: {default: 1.5, cld-np-09.cloud.pd.infn.it: 1 } }"'

The default allocation ratios (4 for cpu and 1.5 for ram) are set within the default key of cpu and/or ram. Compute nodes specific values can be set by specifying the node name, like in the example above, where the node cld-np-09.cloud.pd.infn.it has both the cpu and ram allocation ratios set to 1.

If changes are made to the configuration file, remember to restart the collector:

# cd /root/caos/cap-prod
# docker-compose restart collector

Notes for Ocata: starting with Ocata the collector will read the allocation ratios using the nova placement api. Therefore the above configuration is not required anymore, but it can be used to override the values.

CPU related data

• CPU Time: CPU time consumed over the specified granularity
• TOTAL CPUs: Total CPU time available (number of cores in HT times the granularity)
• Wall Clock Time: VCPU time consumed over the specified granularity
• TOTAL VCPUs: Total VCPU time available (taking overcommitment into account)
• Quota: Total VCPU time available as given by quota.

Ratio between CPU Time and Wall Clock Time

• Used VCPUs: Number of used VCPUs
• TOTAL VCPUs: Total VCPUs available (taking overcommitment into account).
• Quota: Total VCPUs available as given by quota.

• VRAM usage
• Quota

• Active VMs: Number of active VMs
• Deleted VMs: Number of deleted VMs
• Quota: Total VMs available as set by quota

Resource usages in percent with respect of their quota.

• CPU efficiency: ratio between CPU Time and Wall Clock Time
• VCPU: ratio between Used VCPUs and VCPUs quota
• VRAM: ratio between Used VRAM and VRAM quota
• Instances: ratio between Active VMs and VMs quota