Ceilometer project aims to become the infrastructure to collect measurements
within OpenStack so that no two agents would need to be written to collect
the same data. It's primary targets are monitoring and metering, but the
framework should be easily expandable to collect for other needs. To that
effect, Ceilometer should be able to share collected data with a variety
This charm provides the Ceilometer service for OpenStack. It is intended to
be used alongside the other OpenStack components, starting with the Folsom
Ceilometer is made up of 2 separate services: an API service, and a collector
service. This charm allows them to be deployed in different combination,
depending on user preference and requirements.
This charm was developed to support deploying Folsom on both Ubuntu Quantal
and Ubuntu Precise. Since Ceilometer is only available for Ubuntu 12.04 via
the Ubuntu Cloud Archive, deploying this charm to a Precise machine will by
default install Ceilometer and its dependencies from the Cloud Archive.
In order to deploy Ceilometer service, the MongoDB service is required:
juju deploy mongodb juju deploy ceilometer juju add-relation ceilometer mongodb
then Keystone and Rabbit relationships need to be established:
juju add-relation ceilometer rabbitmq juju add-relation ceilometer keystone:identity-service juju add-relation ceilometer keystone:identity-notifications
In order to capture the calculations, a Ceilometer compute agent needs to be
installed in each nova node, and be related with Ceilometer service:
juju deploy ceilometer-agent juju add-relation ceilometer-agent nova-compute juju add-relation ceilometer:ceilometer-service ceilometer-agent:ceilometer-service
Ceilometer provides an API service that can be used to retrieve
- (boolean) If True enables openstack upgrades for this charm via juju actions. You will still need to set openstack-origin to the new repository but instead of an upgrade running automatically across all units, it will wait for you to execute the openstack-upgrade action for this charm on each unit. If False it will revert to existing behavior of upgrading all units on config change.
- (int) Number of workers for Ceilometer API server. (>= Kilo).
- (boolean) Enable debug logging.
- (string) Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.
- (int) Default multicast port number that will be used to communicate between HA Cluster nodes.
- (int) Client timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 30000ms is used.
- (int) Connect timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 5000ms is used.
- (int) Queue timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 5000ms is used.
- (int) Server timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 30000ms is used.
- (string) Used by the nrpe-external-master subordinate charm. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
- (string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
- (string) Repository from which to install. May be one of the following: distro (default), ppa:somecustom/ppa, a deb url sources entry, or a supported Cloud Archive release pocket. Supported Cloud Archive sources include: cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed For series=Precise we support cloud archives for openstack-release: * icehouse For series=Trusty we support cloud archives for openstack-release: * juno * kilo * ... NOTE: updating this setting to a source that is known to provide a later version of OpenStack will trigger a software upgrade. NOTE: when openstack-origin-git is specified, openstack specific packages will be installed from source rather than from the openstack-origin repository.
- (string) The IP address and netmask of the OpenStack Admin network (e.g. 192.168.0.0/24) This network will be used for admin endpoints.
- (string) The IP address and netmask of the OpenStack Internal network (e.g. 192.168.0.0/24) This network will be used for internal endpoints.
- (string) The hostname or address of the public endpoints created for ceilometer in the keystone identity provider. This value will be used for public endpoints. For example, an os-public-hostname set to 'ceilometer.example.com' with ssl enabled will create the following public endpoints for ceilometer: https://ceilometer.example.com:8777/
- (string) The IP address and netmask of the OpenStack Public network (e.g. 192.168.0.0/24) This network will be used for public endpoints.
- (string) Username to request access on rabbitmq-server.
- (string) RabbitMQ virtual host to request access on rabbitmq-server.
- (string) OpenStack Region
- (string) SSL CA to use with the certificate and key provided - this is only required if you are providing a privately signed ssl_cert and ssl_key.
- (string) SSL certificate to install and use for API ports. Setting this value and ssl_key will enable reverse proxying, point Ceilometer's entry in the Keystone catalog to use https, and override any certficiate and key issued by Keystone (if it is configured to do so).
- (string) SSL key to use with certificate specified as ssl_cert.
- (boolean) Setting this to True will allow supporting services to log to syslog.
- (boolean) Enable verbose logging.
- (string) Virtual IP(s) to use to front API services in HA configuration. If multiple networks are being used, a VIP should be provided for each network, separated by spaces.