Hide Forgot
Description of problem: Glusterd doesn't have means of creating a volume exclusively for storing information that may be used in maintaining the cluster outside the scope of glusterd. Motivation: This feature is brought in to facilitate clustering solutions like CTDB to be used in conjunction glusterd. Version-Release number of selected component (if applicable): How reproducible: N/A Steps to Reproduce: 1. N/A 2. 3. Actual results: Expected results: Additional info:
Creating a special kind of automatically created volume seems like a pretty significant change, and since it's only for such a specific purpose I think there needs to be a lot more discussion about requirements and alternatives. How *exactly* would CTDB use this, what characteristics must it have, why can't CTDB use a standard manually created volume, how else might CTDB solve those problems, and what other things might benefit from this feature if it were defined a bit differently?
Currently we are planning to fix the issue by having the proper hooks itself, instead of creating a 'meta' volume.