swift start/stop high level upstart configurations
Bug #1238701 reported by
James Page
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| swift (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Trusty |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
On a swift storage node, there are a large number of upstart configurations that need to be bounced for software upgrades etc..
Having a top-level swift job which the others start/stop off would help manage this using the following stanza in all configs:
start on runlevel [2345] or starting swift
stop on runlevel [!2345] or stopping swift
this would result in :
sudo swift restart
restarting all swift upstart configurations on the server.
(not 100% my idea - pinched from ceph)
| summary: |
- swift start/stop high level control configurations + swift start/stop high level upstart configurations |
| Changed in swift (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
