Hi, I guess, the splitting point is defined by the hypervisor, so I guess that's a +1 for the config option. Does any other hypervisor have such a limit? If so, it would make sense to set it to the minimum of all those limits.
Mate On Thu, Jun 20, 2013 at 06:02:44PM +0100, John Garbutt wrote: > Hi, > > I have had some discussions about if I should add a config flag in this > change: > https://review.openstack.org/#/c/32760/ > > I am looking to support adding a large amount of ephemeral disk space > to a VM, but the VHD format has a limit of around 2TB per disk. To > work around this in XenServer, I plan to add several smaller disks to > make up the full ephemeral disk space. > > To me it seems worth adding a configuration flag (in this case), > because there is no easy way to guess the correct value, and there > doesn't seem to be a great value to hardcode it to. Having said that, > I suspect the default value will be all most people need, whether or > not they have very large ephemeral disk space in their flavors. > > I am curious about what people think (in general, and in this case) > about the tradeoff between: hardcode, magic heuristic calculation, add > config > > John > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mate Lakat _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev