Project

General

Profile

Feature #7770

"ceph osd crush set" should handle ingestion of non-compiled crush maps

Added by Brian Andrus about 10 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
Reviewed:
Affected Versions:
Component(RADOS):
CRUSH, ceph cli
Pull request ID:

Description

"ceph osd crush dump" will output a decompiled version of the crush map in a format of choice. It would be nice to be able to modify that using off-the shelf libraries of choice, and reinject it in the same format.

"ceph osd crush set" should validate, process, and ingest non-compiled versions of the crush map if a format is specified.

History

#1 Updated by Samuel Just about 10 years ago

We probably want a better idea of what they are trying to accomplish.

#2 Updated by Brian Andrus about 10 years ago

Stating the obvious: If a user is going to manually modify the crush map, there is always a chance of botching it and causing the cluster to go unrecoverable. Crushtool allows the testing of maps before insertion, which offers a safeguard against accidental FUBARs.

The use-case: Some users might choose to script the modification of the crush map. While this could inherently be a bad idea, scripting the modification of a JSON or XML map would at least a lot more accessible than scripting the modification of a plain text map. If someone wants to do it, they will find a way. We could at least make it easier for them by allowing a JSON or XML insertion.

Additional ideas: perhaps an --i-know-this-is-a-bad-idea flag would accompany it. Perhaps the insertion would compile, then also perform a basic simulation or sanity check against the map to catch any horribly obvious mistakes before applying.

#3 Updated by Patrick Donnelly almost 5 years ago

  • Project changed from Ceph to RADOS
  • Component(RADOS) CRUSH, ceph cli added

Also available in: Atom PDF