Hi Sage, I added a proposal[1] to the next CDM[2] to be able to store and use multiple weights for each item in the crushmap. I'm not sure about the naming (probabilities is a long word...) but it would be good to not have a third variable named weight with yet another meaning. Although we could modify the builder functions, I'm not sure this is a good idea. They are not complete enough to hide the crush data structures and it is probably enough to document the new data members. And the caller can allocate it and fill it after creating a bucket. In practice that is going to be used by CrushWrapper or python-crush which will define an API. It is probably best if the crush modification is the bare minimum: - allowing the choose function to pick a probability from a table indexed by the round instead of relying on a single weight - storing the probability table in each item Feel free to modify the pad if you have other ideas, this is a first draft done today and I won't be offended if it is discarded ;-) Cheers [1] http://pad.ceph.com/p/crush-multiweight [2] http://tracker.ceph.com/projects/ceph/wiki/CDM_05-APR-2017 -- Loïc Dachary, Artisan Logiciel Libre -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
