Openstack Charmers Next Mysql Router

Learn about configurations >

• auth_cache_refresh_interval | int

  Default: 2

  Time (in seconds) between the auth-cache refresh attempts. Defaults to 2. The value must be smaller than auth_cache_ttl and ttl else Router won't start.

• auth_cache_ttl | int

  Default: -1

  Time (in seconds) until the cache becomes invalid if not refreshed. Defaults to -1 (infinite). The value must be larger than auth_cache_refresh_interval else Router won't start.

• base-port | int

  Default: 3306

  Base port number for RW interface. RO, xRW and xRO will increment from base_port.

• max_connections | int

  Default: 512

  Maximum number of connections to allow in direction to each MySQL routing sessions, with one for the RW unit and another one for the RO units of the MySQL innodb cluster. Defaults to 512. A valid range is between 1 and 65535.

• source | string

  Default: distro

  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 e.g. . cloud:<series>-<openstack-release> cloud:<series>-<openstack-release>/updates cloud:<series>-<openstack-release>/staging cloud:<series>-<openstack-release>/proposed . See https://wiki.ubuntu.com/OpenStack/CloudArchive for info on which cloud archives are available and supported.

• 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.

• ttl | float

  Default: 0.5

  Time to live (in seconds) of information in the metadata cache. Accepts either an integer or a floating point value. The granularity is limited to milliseconds, where 0.001 equates to one millisecond. Precision is truncated to the supported range; for example ttl=0.0119 is treated as 11 milliseconds. The value 0 means that the metadata cache module queries the metadata continuously in a tight loop.

• use-syslog | boolean

  Setting this to True will allow supporting services to log to syslog.