Gregory Thiemonge 0119358280 Set octavia services' stop grace period to 300sec ... Octavia worker, house-keeping and health-monitor serivices may use some long taskflow's flows to handle load balancers and amphorae (launch VMs, etc...). Those flows should not be interrupted when restarting those services (i.e when updating an overcloud, or restarting services because of certificates rotation), it might cause resource leaks that cannot be fixed by an admin. As default container stop timeout is defined to 10 seconds, this timeout value needs to be increased for octavia services (except octavia api) to ensure a graceful shutdown. This new value has been set to 300 seconds according to the octavia worker default configuration introduced in https://review.opendev.org/#/c/684201/ Closes-Bug: #1855684 Change-Id: I8911a79328769c910d03168cfa5a421d0dd0f9b6 (cherry picked from commit c595835776)		2020-01-23 08:38:45 +00:00
..
octavia-api-container-puppet.yaml	Add Octavia driver agent service	2019-12-09 11:35:23 +00:00
octavia-base.yaml	Fix Octavia to use correct Puppet class	2020-01-02 15:56:39 +00:00
octavia-deployment-config.j2.yaml	Only generate Octavia certs on stack create	2019-08-27 15:07:25 -02:30
octavia-health-manager-container-puppet.yaml	Set octavia services' stop grace period to 300sec	2020-01-23 08:38:45 +00:00
octavia-housekeeping-container-puppet.yaml	Set octavia services' stop grace period to 300sec	2020-01-23 08:38:45 +00:00
octavia-worker-container-puppet.yaml	Set octavia services' stop grace period to 300sec	2020-01-23 08:38:45 +00:00