14b84a79db
For effective cache use all endpoints should be specified explicitly as memcache client use specific algorithm to identify on which cache server key is stored based on servers availability and key name. If memcached deployed behind the service unless same key is stored on all memcached instances clients will always got cache misses and will require to use heavy calls to database. So in the end all keys will be stored on all memcached instances. Furthermore delete operations such as revoke token or remove keystone group call logic in service to remove data from cache if Loadbalancer is used this functionality can't work as we can't remove keys from all backends behind LB with single call. Change-Id: I253cfa2740fed5e1c70ced7308a489568e0f10b9
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on oftc
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on oftc
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.