access-network | string

The IP address and netmask of the 'access' network (e.g. 192.168.0.0/24) . This network will be used for access to database services.

binlogs-expire-days | int

Default: 10

Sets the expire_logs_days mysql configuration option, which will make mysql server automatically remove logs older than configured number of days.

binlogs-max-size | string

Default: 100M

Sets the max_binlog_size mysql configuration option, which will limit the size of the binary log files. The server will automatically rotate binlgos after they grow to be bigger than this value. Keep in mind that transactions are never split between binary logs, so therefore binary logs might get larger than configured value.

binlogs-path | string

Default: /var/log/mysql/mysql-bin.log

Location on the filesystem where binlogs are going to be placed. Default mimics what mysql-common package would do for mysql. Make sure you do not put binlogs inside mysql datadir (/var/lib/mysql/)!

cluster-network | string

The IP address and netmask of the cluster (replication) network (e.g. 192.168.0.0/24) . This network will be used for wsrep_cluster replication.

dataset-size | string

(DEPRECATED - use innodb-buffer-pool-size) How much data should be kept in memory in the DB. This will be used to tune settings in the database server appropriately. Supported suffixes include K/M/G/T. If suffixed with %, one will get that percentage of RAM allocated to the dataset.

dns-ha | boolean

Use DNS HA with MAAS 2.0. Note if this is set do not set vip settings below.

enable-binlogs | boolean

Turns on MySQL binary logs. The placement of the logs is controlled with the binlogs_path config option.

ha-bindiface | string

Default: eth0

Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.

ha-mcastport | int

Default: 5490

Default multicast port number that will be used to communicate between HA Cluster nodes.

harden | string

Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.

innodb-buffer-pool-size | string

By default this value will be set according to 50% of system total memory or 512MB (whichever is lowest) but also can be set to any specific value for the system. Supported suffixes include K/M/G/T. If suffixed with %, one will get that percentage of system total memory allocated.

innodb-change-buffering | string

Configure whether InnoDB performs change buffering, an optimization that delays write operations to secondary indexes so that the I/O operations can be performed sequentially. Permitted values include none Do not buffer any operations. inserts Buffer insert operations. deletes Buffer delete marking operations; strictly speaking, the writes that mark index records for later deletion during a purge operation. changes Buffer inserts and delete-marking operations. purges Buffer the physical deletion operations that happen in the background. all The default. Buffer inserts, delete-marking operations, and purges. For more details https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_change_bufferring

innodb-file-per-table | boolean

Default: True

Turns on innodb_file_per_table option, which will make MySQL put each InnoDB table into separate .idb file. Existing InnoDB tables will remain in ibdata1 file - full dump/import is needed to get rid of large ibdata1 file

innodb-io-capacity | int

Configure the InnoDB IO capacity which sets an upper limit on I/O activity performed by InnoDB background tasks, such as flushing pages from the buffer pool and merging data from the change buffer. This value typically defaults to 200 but can be increased on systems with fast bus-attached SSD based storage to help the server handle the background maintenance work associated with a high rate of row changes. Alternatively it can be decreased to a minimum of 100 on systems with low speed 5400 or 7200 rpm spindles, to reduce the proportion of IO operations being used for background maintenance work. For more details https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_io_capacity

key | string

Key ID to import to the apt keyring to support use with arbitary source configuration from outside of Launchpad archives or PPA's.

lp1366997-workaround | boolean

Adds two config options (wsrep_drupal_282555_workaround and wsrep_retry_autocommit) as a workaround for Percona Primary Key bug (see LP 1366997).

max-connections | int

Default: 600

Maximum connections to allow. A value of -1 means use the server's compiled-in default. This is not typically that useful so the charm will configure PXC with a default max-connections value of 600. Note: Connections take up memory resources. Either at startup time with performance-schema=True or during run time with performance-schema=False. This value is a balance between connection exhaustion and memory exhaustion. Consult a MySQL memory calculator like http://www.mysqlcalculator.com/ to understand memory resources consumed by connections. See also performance-schema.

min-cluster-size | int

Minimum number of units expected to exist before charm will attempt to bootstrap percona cluster. If no value is provided this setting is ignored.

nagios_context | string

Default: juju

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.

nagios_servicegroups | string

A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup.

os-access-hostname | string

The hostname or address of the access endpoint for percona-cluster.

performance-schema | boolean

The performance schema attempts to automatically size the values of several of its parameters at server startup if they are not set explicitly. When set to on (True) memory is allocated at startup time. The implications of this is any memory related charm config options such as max-connections and innodb-buffer-pool-size must be explicitly set for the environment percona is running in or percona may fail to start. Default to off (False) at startup time giving 5.5 like behavior. The implication of this is one can set configuration values that could lead to memory exhaustion during run time as memory is not allocated at startup time.

prefer-ipv6 | boolean

If True enables IPv6 support. The charm will expect network interfaces to be configured with an IPv6 address. If set to False (default) IPv4 is expected. . NOTE: these charms do not currently support IPv6 privacy extension. In order for this charm to function correctly, the privacy extension must be disabled and a non-temporary address must be configured/available on your network interface.

root-password | string

Root account password for new cluster nodes. Overrides the automatic generation of a password for the root user, but must be set prior to deployment time to have any effect.

source | string

Package install location for Percona XtraDB Cluster (defaults to distro for >= 14.04)

sst-method | string

Default: xtrabackup-v2

Percona method for taking the State Snapshot Transfer (SST), can be: 'rsync', 'xtrabackup', 'xtrabackup-v2', 'mysqldump', 'skip' - see https://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_sst_method

sst-password | string

SST account password for new cluster nodes. Overrides the automatic generation of a password for the sst user, but must be set prior to deployment time to have any effect.

table-open-cache | int

Default: 2048

Sets table_open_cache (formerly known as table_cache) to mysql.

tuning-level | string

Default: safest

Valid values are 'safest', 'fast', and 'unsafe'. If set to 'safest', all settings are tuned to have maximum safety at the cost of performance. 'fast' will turn off most controls, but may lose data on crashes. 'unsafe' will turn off all protections but this may be OK in clustered deployments.

vip | string

Virtual IP to use to front Percona XtraDB Cluster in active/active HA configuration

vip_cidr | int

Default: 24

Netmask that will be used for the Virtual IP.

vip_iface | string

Default: eth0

Network interface on which to place the Virtual IP.

wait-timeout | int

Default: -1

The number of seconds the server waits for activity on a noninteractive connection before closing it. -1 means use the server's compiled in default.

Alai Mysql