Actions
Feature #2554
closedchef: open question: How do we discover what disks we should use as Ceph data disks?
Status:
Rejected
Priority:
High
Assignee:
-
Category:
chef
Target version:
-
% Done:
0%
Source:
Tags:
CY2012
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
For Crowbar, see #2574.
- This is somewhat a dangerous operation, run accidentally it will clobber a lot of data. I'd like to be as explicit as possible, and not just overwrite all block devices I find. Any thoughts?
Updated by Anonymous almost 12 years ago
- Subject changed from chef/crowbar: open question: How do we discover what disks we should use as Ceph data disks? to chef: open question: How do we discover what disks we should use as Ceph data disks?
- Description updated (diff)
- Category set to chef
Updated by Sage Weil almost 12 years ago
- Project changed from Ceph to devops
- Category deleted (
chef)
Updated by Anonymous over 11 years ago
- Translation missing: en.field_story_points set to 7
- Translation missing: en.field_position set to 200
Updated by Anonymous over 11 years ago
What DH does: each Chef node has an attribute that's a list of block device pairs (data, journal).
Actions