Skip to content

galera-agent job from pxc/1.0.15

Github source: 3d6c608b or master branch

Properties

db_password

Password used by the sidecar to connect to the database

endpoint_password

Password used by the sidecar endpoints for Basic Auth

endpoint_tls

ca

PEM-encoded certificate authority (CA) for securing TLS communication over the galera-agent endpoint

Default
""

certificate

PEM-encoded certificate for securing TLS communication over the galera-agent endpoint

enabled

Enable TLS for galera-agent endpoints. This requires the endpoint_tls.certificate and endpoint_tls.private_key options are configured.

Default
false

private_key

PEM-encoded key for securing TLS communication over the galera-agent endpoint

server_name

The host name a client should accept on the endpoint_tls.certificate when communicating with galera-agent

Default
""

endpoint_username

Username used by the sidecar endpoints for Basic Auth

Default
galera-agent

logging

format

timestamp

Format for timestamp in component logs. Valid values are ‘rfc3339’, ‘unix-epoch’. ‘rfc3339’ is the recommended format. It will result in all timestamps controlled by this job to be in RFC3339 format, which is human readable. This includes stdout, pre-start, and post-start logs. This does not include stderr logs from golang libraries. ‘unix-epoch’ will result in all timestamps being in the format they were before the rfc3339 flag was introduced. This format is different for different logs. We do not recommend using this flag unless you have scripts that expect a particular timestamp format.

Default
rfc3339

port

Port used by sidecar process to listen on

Default
9200

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/galera-agent/ directory (learn more).

  • bin/drain (from drain.sh.erb)
  • config/bpm.yml (from bpm.yml.erb)
  • config/galera-agent-config.yml (from galera-agent-config.yml.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.