Swift¶
This page is the starting point for Swift, the swift role: swift_proxy_server, swift_rsyncd and the account,
container and object containers (18 in all; the three *_replication_server containers start only when
swift_replication_interface differs from swift_storage_interface, which it does not by default, so 15 by default:
roles/swift/tasks/start.yml:97,176,256, roles/swift/defaults/main.yml:65, group_vars/all.yml:240-241), on the
control and storage nodes of the example inventory, selected by the tag swift. The rings are operator-built
(Component dependencies §3), and deploy does not apply swift config or
ring changes to running containers: no task of the role notifies a handler, and its only handler, Restart
swift-proxy-server container, is a debug no-op (roles/swift/handlers/main.yml:2-4) (fact sheet D
§3.4). 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¶
No operation page gives a command line for the swift tag, and the tag has no row of its own in Tags
§3 or in the Tag index. What the
study says about running it is in fact sheet D: the plays the tag selects
(§3.1) and the task flow per action
(§3.4). Its reconfigure is
not deploy: swift and bifrost have their own reconfigure logic (Repository architecture
§4.2).
Dependencies¶
- Dependencies: Component dependencies §3
Evidence¶
- Fact sheet: fact sheet D §3
- Image side: Kolla images §5 (rows
swift-*)
Before and after a run¶
- fact sheet D §3.3, ring
files: Kolla does not build rings; the precheck fails unless
account|container|object.builderand.ring.gzexist under{{node_custom_config}}/swift/(roles/swift/tasks/precheck.yml:115-120). - fact sheet D §3.4,
deploy: it does not apply swift config or ring changes to running containers. - fact sheet D §3.4,
reconfigure: it fails if any listed container is not running, so it cannot repair a crashed container; under COPY_ALWAYS (the default) it restarts a container whenkolla_set_configs --checkreturns rc 1, and with the defaultkolla_serial=0every changed proxy, on every proxy host, restarts in that one task (roles/swift/tasks/reconfigure.yml:32-54,88-101,site.yml:470-481,group_vars/all.yml:43) CODE. NOT AVAILABLE: whether this opens an outage window. - fact sheet D §3.4,
upgrade: by default it stops all storage containers on all storage hosts at once, restarts them, then stops and starts the proxies (swift_enable_rolling_upgrade: "yes",roles/swift/defaults/main.yml:72;roles/swift/tasks/rolling_upgrade.yml:31-40,48-66) CODE. - R21, precautions for enabling Swift (or
glance_backend_ceph) on a running cloud: setglance_backend_*explicitly before enabling Swift.
Known limits and open points¶
- Known bugs and limitations, row
swift: no handlers are notified (deploy does not apply config/ring changes);stop.ymlwrong container name; precheck probes rsync port 873 vs 10873. Status: CODE, all three still in 2023.1 (roles/swift/tasks/stop.yml:23-31,roles/swift/tasks/precheck.yml:89,group_vars/all.yml:544); runtime effects NOT AVAILABLE. - What is not known: the sources do not establish the runtime effects of the swift limitations.
- Q12: "Glance backend switch on enabling Swift". Status: NOT AVAILABLE.
- F5, "
reconfigure=deploy" (Ussuri: 70 of the 72 roles that have atasks/reconfigure.yml). In 2023.1, 59 roles have atasks/reconfigure.yml: 57 rundeploy.yml(skyline throughinclude_tasks), and only swift and bifrost have their own logic (Repository architecture §4.2) CODE. - fact sheet D §3.8, "Oddities":
enable_swift_reconis tested without| bool(NOT AVAILABLE: whether the template treats that string as true and so always enables the recon middleware); theproxy-loggingandversioned_writesfilters are defined but not in the proxy pipeline. Both still in 2023.1:enable_swift_recon: "no"(group_vars/all.yml:750) is tested as{% if enable_swift_recon %}(roles/swift/templates/account.conf.j2:15,17,container.conf.j2:15,17,object.conf.j2:19,22);roles/swift/templates/proxy-server.conf.j2:13,33,92CODE. - fact sheet D
§3.5:
NOT AVAILABLE: what changing
swift_hash_path_suffix/prefixafter data is written does. - fact sheet D
§7, items
1 to 4: the account-auditor guard of
stop.ymlchecksswift_object_auditor; the precheck checks rsync port 873, but rsyncd uses 10873;{% if enable_swift_recon %}without| boolagainst the string"no"; deploy never restarts on config or ring change, reconfigure fails if any swift container is down, and the "rolling" upgrade stops all storage at once. - fact sheet D §8:
NOT AVAILABLE: whether the swift containers serve the new rings once
reconfigurehas restarted them; the effective value ofenable_swift_reconin the renderedobject-server.conf. - What is not known: fact sheet D has its own NOT AVAILABLE list, and its §3.4, §3.5 and §3.8 are among the sections that contain NOT AVAILABLE marks.
Service card¶
The rows of the card are explained on the Components page.
| Item | Value |
|---|---|
| Play | site.yml:470 |
| Tags | swift |
| Play host patterns | swift-account-server, swift-container-server, swift-object-server, swift-proxy-server |
| Node types in play (example inventory) | control, storage |
| Node types running its containers | control, storage |
| Containers | swift_proxy_server, swift_rsyncd, swift_account_server, swift_account_auditor, swift_account_replication_server, swift_account_replicator, swift_account_reaper, swift_container_server, swift_container_auditor, swift_container_replication_server, swift_container_replicator, swift_container_updater, swift_object_server, swift_object_auditor, swift_object_replication_server, swift_object_replicator, swift_object_updater, swift_object_expirer |
deploy/reconfigure flow (tasks/) |
register → config → start → check |
| Task files | check.yml, config.yml, config_validate.yml, copy-certs.yml, deploy-containers.yml, deploy.yml, legacy_upgrade.yml, loadbalancer.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, register.yml, rolling_upgrade.yml, start.yml, stop.yml, upgrade.yml |
| Templates | account.conf.j2, container.conf.j2, object.conf.j2, proxy-server.conf.j2, rsyncd.conf.j2, swift-account-auditor.json.j2, swift-account-reaper.json.j2, swift-account-replication-server.json.j2, swift-account-replicator.json.j2, swift-account-server.json.j2, swift-container-auditor.json.j2, swift-container-replication-server.json.j2, swift-container-replicator.json.j2, swift-container-server.json.j2, swift-container-updater.json.j2, swift-object-auditor.json.j2, swift-object-expirer.json.j2, swift-object-replication-server.json.j2, swift-object-replicator.json.j2, swift-object-server.json.j2, swift-object-updater.json.j2, swift-proxy-server.json.j2, swift-rsyncd.json.j2, swift.conf.j2 |
| Handlers (definition order) | Restart swift-proxy-server container |
| Key variables | enable_swift, swift_devices_*, swift_*_server ports |
| Role dependencies | none |
Related¶
- fact sheet D §3 — the per-role evidence: plays, services, ring files, task flow, config files, networks and ports
- Glance — enabling Swift changes Glance's default backend
- Repository architecture §4.2 — swift is one of the two roles with their own reconfigure logic
- Kolla images §5 — swift config and rings are copied only at container start
- Predict and inspect a run —
kolla_set_configs --check, which the swift reconfigure runs - Components — the other component pages