trilio dm api #25
Description
TrilioVault provides a backup and recovery solution that natively integrates with OpenStack Clouds. . This charm provides the TrilioVault Data Mover API which forms part of the TrilioVault solution.
- Tags:
- openstack ›
- storage ›
- backup ›
Overview
This charm provides the TrilioVault Data Mover API service which forms part of the TrilioVault Cloud Backup solution.
Usage
TrilioVault Data Mover API relies on services from mysql, rabbitmq-server and keystone charms. Steps to deploy the charm:
juju deploy trilio-dm-api
juju deploy keystone
juju deploy mysql
juju deploy rabbitmq-server
juju add-relation trilio-dm-api rabbitmq-server
juju add-relation trilio-dm-api mysql
juju add-relation trilio-dm-api keystone
Bugs
Please report bugs on Launchpad.
Configuration
- action-managed-upgrade
- (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.
- admin-port
- (int) DataMover API admin endpoint port
- 8784
- debug
- (boolean) Enable debug logging
- dns-ha
- (boolean) Use DNS HA with MAAS 2.0. Note if this is set do not set vip settings below.
- haproxy-client-timeout
- (int) Client timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 90000ms is used.
- haproxy-connect-timeout
- (int) Connect timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 9000ms is used.
- haproxy-queue-timeout
- (int) Queue timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 9000ms is used.
- haproxy-server-timeout
- (int) Server timeout configuration in ms for haproxy, used in HA configurations. If not provided, default value of 90000ms is used.
- internal-port
- (int) DataMover API internal endpoint port
- 8784
- openstack-origin
- (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 Ubuntu Cloud Archive (UCA) release pocket. . Supported UCA 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 UCA for openstack-release= * icehouse . For series=Trusty we support UCA 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.
- cloud:bionic-train
- os-admin-hostname
- (string) The hostname or address of the admin endpoints created in the keystone identity provider. . This value will be used for admin endpoints. For example, an os-admin-hostname set to 'api-admin.example.com' with ssl enabled will create the following endpoint for neutron-api: . https://api-admin.example.com:9696/
- os-admin-network
- (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.
- os-internal-hostname
- (string) The hostname or address of the internal endpoints created in the keystone identity provider. . This value will be used for internal endpoints. For example, an os-internal-hostname set to 'api-internal.example.com' with ssl enabled will create the following endpoint for neutron-api: . https://api-internal.example.com:9696/
- os-internal-network
- (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.
- os-public-hostname
- (string) The hostname or address of the public endpoints created in the keystone identity provider. . This value will be used for public endpoints. For example, an os-public-hostname set to 'api-public.example.com' with ssl enabled will create the following endpoint for neutron-api: . https://api-public.example.com:9696/
- os-public-network
- (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.
- public-port
- (int) DataMover API public endpoint port
- 8784
- python-version
- (int) THIS OPTION IS DEPRECATED AND HAS NO EFFECT
- 3
- region
- (string) OpenStack Region
- RegionOne
- ssl_ca
- (string) TLS CA to use to communicate with other components in a deployment. . __NOTE__: This configuration option will take precedence over any certificates received over the ``certificates`` relation.
- ssl_cert
- (string) TLS certificate to install and use for any listening services. . __NOTE__: This configuration option will take precedence over any certificates received over the ``certificates`` relation.
- ssl_key
- (string) TLS key to use with certificate specified as ``ssl_cert``. . __NOTE__: This configuration option will take precedence over any certificates received over the ``certificates`` relation.
- triliovault-pkg-source
- (string) Repository address of triliovault packages
- deb [trusted=yes] https://apt.fury.io/triliodata-4-0/ /
- use-internal-endpoints
- (boolean) Openstack mostly defaults to using public endpoints for internal communication between services. If set to True this option will configure services to use internal endpoints where possible.
- use-syslog
- (boolean) Setting this to True will allow supporting services to log to syslog.
- verbose
- (boolean) Enable verbose logging
- vip
- (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.
- vip_cidr
- (int) Default CIDR netmask to use for HA vip when it cannot be automatically determined.
- 24
- vip_iface
- (string) Default network interface to use for HA vip when it cannot be automatically determined.
- eth0
- worker-multiplier
- (float) The CPU core multiplier to use when configuring worker processes. By default, the number of workers for each daemon is set to twice the number of CPU cores a service unit has. This default value will be capped to 4 workers unless this configuration option is set.