Configure keystonemiddleware to deal with memcached pods failures

Whenever one of the mecached pods disappears, because of a rolling
restart during a minor update or as result of a failure, APIs can
take a long time to detect that the pod went away and keep trying
to reconnect.

From a quick round of tests we saw downtimes up to ~150s.

By tuning memcache_pool_dead_retry and memcache_pool_conn_get_timeout
the behavior seems much more acceptable.

Jira: https://issues.redhat.com/browse/OSPRH-11935

Author: lmiccini

templates/manila/config/00-config.conf

@@ -29,6 +29,8 @@ db_max_retries = -1
 www_authenticate_uri={{ .KeystonePublicURL }}
 auth_url = {{ .KeystoneInternalURL }}
 memcached_servers = {{ .MemcachedServersWithInet }}
+memcache_pool_dead_retry = 10
+memcache_pool_conn_get_timeout = 2
 auth_type = password
 project_domain_name = Default
 user_domain_name = Default