Description of problem:

When the Galera resource agent starts nodes of a galera cluster, it currently relies on the resource's attribute to pass the "open files limit" to mysqld.

Splitting the mysql configuration in two distinct locations (mariadb configuration files and pacemaker cib) is not ideal as it can cause all sort of bad behaviours:

  . increasing "max_connection" in galera config may not work if one forgot to change "open files limit" accordingly in pacemaker resource.

  . starting galera manually while resource is unmanaged in pacemaker will have a different limit.

  . specifying "open files limit" in galera config file and in pacemaker will cause on setting to be overriden, which can be unexpected.

We should have cleaner "open files limit" policy and make sure the resource agent works as expected without relying on resource attribute.