Sahid pointed out that the swift-init will traverse a search path and start a daemon for every config file it finds so no change to the init script is needed. Initial tests suggest this completely covers my use case. I will continue testing and report back. I will mark the bug as invalid for the moment. Thanks Sahid !
** Changed in: cloud-archive/mitaka Status: Triaged => Invalid ** Changed in: cloud-archive/ocata Status: Triaged => Invalid ** Changed in: cloud-archive/queens Status: Triaged => Invalid ** Changed in: cloud-archive/rocky Status: Triaged => Invalid ** Changed in: cloud-archive/stein Status: Triaged => Invalid ** Changed in: cloud-archive/train Status: Triaged => Invalid ** Changed in: cloud-archive/ussuri Status: Triaged => Invalid ** Changed in: swift (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: swift (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: swift (Ubuntu Disco) Status: Triaged => Invalid ** Changed in: swift (Ubuntu Eoan) Status: Triaged => Invalid ** Changed in: swift (Ubuntu Focal) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1854718 Title: Groups of swift daemons are all forced to use the same config Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Invalid Status in Ubuntu Cloud Archive ocata series: Invalid Status in Ubuntu Cloud Archive queens series: Invalid Status in Ubuntu Cloud Archive rocky series: Invalid Status in Ubuntu Cloud Archive stein series: Invalid Status in Ubuntu Cloud Archive train series: Invalid Status in Ubuntu Cloud Archive ussuri series: Invalid Status in swift package in Ubuntu: Invalid Status in swift source package in Xenial: Invalid Status in swift source package in Bionic: Invalid Status in swift source package in Disco: Invalid Status in swift source package in Eoan: Invalid Status in swift source package in Focal: Invalid 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-auditor, swift-account-reaper & swift-account-replicator all use /etc/swift/account-server.conf. 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" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1854718/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp