Feature #1531
radosgw init.d script stop/restart
| Status: | Resolved | Start date: | 09/09/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Sage Weil | % Done: | 0% | |
| Category: | radosgw | Spent time: | - | |
| Target version: | v0.37 | |||
| Source: | Reviewed: | |||
| Tags: | User Impact: | |||
| Story points | 3.0 | |||
| Velocity based estimate | - |
History
#1 Updated by Sage Weil over 1 year ago
- Target version set to v0.37
#2 Updated by Sage Weil over 1 year ago
- Category set to radosgw
We need to make the init script somehow know whether radosgw is configured in daemon mode or not. It also needs to know which instances of it to set up.
I could iterate over instances of client.[rgw-]* in ceph.conf, see if rgw_socket_path is set, and if so start. That's consistent with how the other daemon types behave at least.
Or we could rely on something else to indicate which instances exist and should be started...
#3 Updated by Sage Weil over 1 year ago
- Position set to 54
#4 Updated by Sage Weil over 1 year ago
- Story points set to 3
- Position deleted (
56) - Position set to 55
#5 Updated by Sage Weil over 1 year ago
- Assignee set to Sage Weil
#6 Updated by Sage Weil over 1 year ago
- Status changed from New to Resolved