Project

General

Profile

Actions

Feature #1531

closed

radosgw init.d script stop/restart

Added by Yehuda Sadeh over 12 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Actions #1

Updated by Sage Weil over 12 years ago

  • Target version set to v0.37
Actions #2

Updated by Sage Weil over 12 years ago

  • Category set to 22

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...

Actions #3

Updated by Sage Weil over 12 years ago

  • Translation missing: en.field_position set to 54
Actions #4

Updated by Sage Weil over 12 years ago

  • Translation missing: en.field_story_points set to 3
  • Translation missing: en.field_position deleted (56)
  • Translation missing: en.field_position set to 55
Actions #5

Updated by Sage Weil over 12 years ago

  • Assignee set to Sage Weil
Actions #6

Updated by Sage Weil over 12 years ago

  • Status changed from New to Resolved
Actions #7

Updated by John Spray over 6 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)
  • Target version deleted (v0.37)

Bulk reassign of radosgw category to RGW project.

Actions

Also available in: Atom PDF