On Tue, Dec 4, 2018 at 3:19 PM Matthew Pounsett <matt@xxxxxxxxxxxxx> wrote:
On Tue, 4 Dec 2018 at 18:12, Vasu Kulkarni <vakulkar@xxxxxxxxxx> wrote:As explained above, we can't just create smaller raw devices. Yes, these are VMs but they're meant to replicate physical servers that will be used in production, where no such volumes are available.In that case you will have to use the same version of ceph-deploy you have used to deploy the original systems. you cannot do this now with newer version.So.. we're trying to figure out how to replicate the configuration we've been using where the ceph data is stored on the OS filesystem.That's irritating, but understood. :)Is there a way we can easily set that up without trying to use outdated tools? Presumably if ceph still supports this as the docs claim, there's a way to get it done without using ceph-deploy?
It might be more involved if you are trying to setup manually, you can give 1.5.38 a try(not that old) and see if it works https://pypi.org/project/ceph-deploy/1.5.38/
If not.. I guess worst case we can revisit having the hardware group to repartition the drives with separate, tiny, data and journal partitions... that is assuming it's not required that those functions have access to whole disks. We would rather avoid that if at all possible, though.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
