On 12/05/2014 11:47 AM, David Champion wrote:
* On 05 Dec 2014, Sage Weil wrote:
adding that fall into this category. Having them in the tree is great
because it streamlines QA and testing, but I want to make sure that
users are not able to enable the features without being aware of the
risks.
A few possible suggestions:
- scarier option names, like
- a separate config option that allows any experimental option
- enumerate experiemntal options we want to enable
Other ideas?
A separate config file for experimental options:
/etc/ceph/danger-danger.conf
One of the questions I have in this is once you've enabled experimental
features, should the cluster be considered experimental forever, even
after the feature has become stable? Maybe some kind of subtle
corruption has worked it's way in it will take a while to manifest. It
seems to me like if you've enabled experimental features on a cluster
that all bets are off.
It seems to me like having the features in a separate ceph.conf file
would imply that you just get rid of the danger.conf file and things are
back to normal, but that's not really how it is imho.
Mark
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
