Memcached¶
This page is the starting point for memcached, the memcached role: one container, memcached, on the control nodes of
the example inventory, selected by the tags memcached and memcache. Unlike most roles, it has no common dependency
(fact sheet A §3.8). The lists below say where the
study covers how to operate it, its impact, its dependencies and the evidence, what to check around a run and what stays
open; the service card follows them.
Where to look¶
Operate¶
- Scenario: Change control-plane membership §2, Reconfigure Neutron §3
- Command: Change control-plane membership §1.1
Impact and risk¶
- What the tag executes (
memcached/memcache): Tags §3 and Tags §3.1, rowsmemcached/memcache - Risks: R4
Dependencies¶
- Dependencies: Component dependencies §1, Component dependencies §2
Evidence¶
- Fact sheet: fact sheet A §3
- Image side: Kolla images §5 (row
memcached)
Before and after a run¶
- Tags §3.1, row
memcached/memcache: safe on its own "yes, off-peak"; prerequisites: none. - R4, precautions for a change of memcached membership: plan as a dataplane change, like
R3/R5: batch with
--limitorANSIBLE_SERIAL, network nodes one at a time; low-traffic window. - Predict and inspect a run, row "See what will restart":
command,permissions, removed entries and stale optional files are not compared, so memcached ("config_files": []) always returns 0. - Kolla images §6, item 1: a normal deploy or reconfigure applies a
config.json-only change; after a separategenconfig,deploy-containerssees no drift and later runs do not restart for it either. Memcached is the extreme case. The change applies at the next restart for another reason CODE.
Known limits and open points¶
- Known bugs and limitations, row
kolla images:kolla_set_configs --checkcompares onlyconfig_filesentries (F14): changes confined toconfig.json(command,permissions; all of memcached's settings) are never detected. Status: CODE. - F6, "Global inputs are rendered into per-host files":
enable_*flags, RabbitMQ/memcached membership, service passwords and the external FQDN end up in compute-side files CODE. - What is not known, row "memcached": the sources do not establish whether cached tokens are lost when the membership changes or the container restarts, and the effect on auth latency and Horizon sessions.
- fact sheet A §3.8, "Operationally notable", four
items: all memcached instances restart at once; adding or removing a memcached host is expensive; tag aliases differ
(
-t memcachereconfigures the container but not its haproxy file, only-t memcacheddoes both); memcached has nocommondependency. - Kolla images §6, item 14: memcached has no data volume and no persistence option CODE; whether every restart therefore empties the cache is NOT AVAILABLE (memcached semantics).
Service card¶
The rows of the card are explained in How to read a service card.
| Item | Value |
|---|---|
| Play | site.yml:481 |
| Tags | memcache, memcached |
| Play host patterns | memcached |
| Node types in play (example inventory) | control |
| Node types running its containers | control |
| Containers | memcached |
deploy/reconfigure flow (tasks/) |
config → check-containers |
| Task files | check-containers.yml, check.yml, config.yml, deploy-containers.yml, deploy.yml, loadbalancer.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, stop.yml, upgrade.yml |
| Templates | memcached.json.j2 |
| Handlers (definition order) | Restart memcached container |
| Key variables | enable_memcached, memcached_port |
| Role dependencies | none |
Related¶
- Change control-plane membership — a
memcached-only change does not touch nova-compute but still restarts the neutron agents on computes - Component dependencies §1 — the templates
of 37 roles loop over
groups['memcached'] - Keystone — memcached is its token cache
- Horizon — it keeps its sessions in memcached when
horizon_backend_databaseis false - Predict and inspect a run —
kolla_set_configs --checkand its exit codes - Components — the other component pages