Groups of swift daemons are all forced to use the same config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
High
|
Unassigned | ||
Mitaka |
Invalid
|
High
|
Unassigned | ||
Ocata |
Invalid
|
High
|
Unassigned | ||
Queens |
Invalid
|
High
|
Unassigned | ||
Rocky |
Invalid
|
High
|
Unassigned | ||
Stein |
Invalid
|
High
|
Unassigned | ||
Train |
Invalid
|
High
|
Unassigned | ||
Ussuri |
Invalid
|
High
|
Unassigned | ||
swift (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Xenial |
Invalid
|
High
|
Unassigned | ||
Bionic |
Invalid
|
High
|
Unassigned | ||
Disco |
Invalid
|
High
|
Unassigned | ||
Eoan |
Invalid
|
High
|
Unassigned | ||
Focal |
Invalid
|
High
|
Unassigned |
Bug Description
On swift storage servers there are three groups of services: account, container and object.
Each of these groups is comprised of a number of services, for instance: server, auditor, replicator etc
Each service has its own init script but all the services in a group are configured to use the same group config file eg swift-account, swift-account-
Obviously this causes a problem when different services need different config. In the case of a swift cluster performing global replication the replication server need "
replication_server = true" where as the auditor needs "replication_server = false"
We may want to fix this along with https:/ /bugs.launchpad .net/bugs/ 1800676. Sahid already took a stab at it a while back but that got delayed by me.
Liam, do you need this prior to ussuri?