Open Stack

Its just that the limit you want to set varies depending on the
flavor. So flavor = 10TB, limit = 2000GB, the final disk is a bit of
an odd size, maybe 1024GB would be a better split.

Although you make a good point, maybe we should set the "splitting
point" in extra specs in the flavor, rather than a config value.

John

On 20 June 2013 18:21, Russell Bryant <rbryant at redhat.com> wrote:
> On 06/20/2013 01:02 PM, 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
>
> Is it really worth adding a config option for this when you effectively
> set the limit already by configuring flavors?  Or am I missing something?
>
> --
> Russell Bryant
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev