The switch to systemd unit files is a big change (LP: #1800676) which we
can do at this point in the ussuri cycle, but I think we'll need to
figure out how to adapt the existing sysvinit approach for SRUs.

** Also affects: swift (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: swift (Ubuntu Focal)
   Importance: High
       Status: Triaged

** Also affects: swift (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: swift (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Also affects: swift (Ubuntu Disco)
   Importance: Undecided
       Status: New

** Changed in: swift (Ubuntu Eoan)
       Status: New => Triaged

** Changed in: swift (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: swift (Ubuntu Disco)
       Status: New => Triaged

** Changed in: swift (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: swift (Ubuntu Bionic)
       Status: New => Triaged

** Changed in: swift (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: swift (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: swift (Ubuntu Xenial)
   Importance: Undecided => High

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/queens
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/ussuri
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/train
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/rocky
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/stein
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/ussuri
   Importance: Undecided => High

** Changed in: cloud-archive/ussuri
       Status: New => Triaged

** Changed in: cloud-archive/train
   Importance: Undecided => High

** Changed in: cloud-archive/train
       Status: New => Triaged

** Changed in: cloud-archive/stein
   Importance: Undecided => High

** Changed in: cloud-archive/stein
       Status: New => Triaged

** Changed in: cloud-archive/rocky
   Importance: Undecided => High

** Changed in: cloud-archive/rocky
       Status: New => Triaged

** Changed in: cloud-archive/queens
   Importance: Undecided => High

** Changed in: cloud-archive/queens
       Status: New => Triaged

** Changed in: cloud-archive/ocata
   Importance: Undecided => High

** Changed in: cloud-archive/ocata
       Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: cloud-archive/mitaka
       Status: New => Triaged

-- 
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:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Triaged
Status in Ubuntu Cloud Archive stein series:
  Triaged
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in swift package in Ubuntu:
  Triaged
Status in swift source package in Xenial:
  Triaged
Status in swift source package in Bionic:
  Triaged
Status in swift source package in Disco:
  Triaged
Status in swift source package in Eoan:
  Triaged
Status in swift source package in Focal:
  Triaged

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

Reply via email to