aboutsummaryrefslogtreecommitdiffstats
path: root/manifests/profile/base/docker_registry.pp
diff options
context:
space:
mode:
authorDamien Ciabrini <dciabrin@redhat.com>2016-12-07 19:09:06 +0100
committerTim Rozet <trozet@redhat.com>2017-02-27 11:40:51 -0500
commit09665170f6d0f4536a48dd4d1444e07aa064bed7 (patch)
tree17d4697ec036328be00377337e4753eeee763ea8 /manifests/profile/base/docker_registry.pp
parent77c1ca1243fbc38210e9f6264c5c36b546d1a95a (diff)
mariadb: Move generation of systemd drop-in to puppet-tripleo
Systemd starts mariadb as user mysql, so in order to allow a large number of connections (e.g. max_connections=4096) it is necessary to raise the file descriptor limit via a system drop-in file. When installing an undercloud, such drop-in file is currently generated by instack-undercloud (in file puppet-stack-config.pp). But non-HA overcloud also need such drop-in to be generated. In order to avoid duplicating code, the drop-in creation code should be provided by puppet-tripleo. By default, no drop-in is generated; it has to be enabled by instack-undercloud or tripleo-heat-template once they will use it (resp. to create undercloud or non-HA overcloud). This patch does not aim at generating a dynamic file limit based on the number of connections, this should land in another dedicated patch. Instead, it just reuses the limit currently set for undercloud and HA-overclouds. Also, the generation of the drop-in does not force a mysql restart like it currently does in instack-undercloud, to avoid unexpected service disruption on a non-HA overcloud after a minor update. Co-Authored-By: Tim Rozet <trozet@redhat.com> Depends-On: I7ca7b5f7614971455cae2bf7c4bf8264b642b0dc Change-Id: Ia0907b2ab6062a93fb9363e39c86535a490fbaf6 Partial-Bug: #1648181 Related-Bug: #1524809
Diffstat (limited to 'manifests/profile/base/docker_registry.pp')
0 files changed, 0 insertions, 0 deletions