Feature #3011
closed
Remove "pool" terminology from CRUSH
Added by Greg Farnum over 11 years ago.
Updated almost 7 years ago.
Description
Users get confused and conflate RADOS pools and CRUSH pools. I don't think we actually use that term in many places in CRUSH, and the ones that do probably won't confuse current users by being changed. I think it'll make us happier.
You're talking about 'pool=default', right? I agree. What term should be use instead for the root of the tree?
'root=default'? 'tree=default'?
I think this is only a matter of the default types, so it should be easy to fix.. just updating docs, basically..
Since it's a hierarchy of nodes, I'd vote for "root." Also, the term "bucket" is confusing, because we use that term with the S3 API. CRUSH hierarchies, as I understand them, are nodes and leaves, and so I prefer those terms to "bucket."
- Tracker changed from Support to Feature
agreed.
i'll stick this in the backlog!
- Target version deleted (
v0.51)
- Translation missing: en.field_position set to 1
- Status changed from New to Fix Under Review
- Translation missing: en.field_position deleted (
2)
- Translation missing: en.field_position set to 1
- Priority changed from Normal to High
- Tags set to CY2012
- Translation missing: en.field_story_points set to 2
- Target version set to v0.52a
- Translation missing: en.field_position deleted (
3)
- Translation missing: en.field_position set to 2
- Target version changed from v0.52a to v0.53a
- Translation missing: en.field_position deleted (
9)
- Translation missing: en.field_position set to 2
- Target version changed from v0.53a to v0.53b
- Translation missing: en.field_position deleted (
5)
- Translation missing: en.field_position set to 2
- Status changed from Fix Under Review to Resolved
- Project changed from Ceph to RADOS
- Category deleted (
10)
- Target version deleted (
v0.53b)
Also available in: Atom
PDF