Yeah, that's an option too. It's sometimes very inconvenient, but
that's what was intended. At any rate I don't think we want to
automatically create multiple templates of different sizes after
upload, I'd rather see the root resize.

On Thu, Feb 20, 2014 at 7:08 PM, Chiradeep Vittal
<[email protected]> wrote:
> Heh, AWS seems to manage fine without it. But that is AWS.
> Service offerings are only for compute, there is a separate disk offering
> for the data volumes. Presumably the data volumes can be used for
> persistent storage (e.g., db files). What is the difference between a 40G
> Drupal template and an 80G Drupal template? Surely that extra 40G could be
> on a data volume?
>
> On 2/20/14 3:11 PM, "Nux!" <[email protected]> wrote:
>
>>On 20.02.2014 23:04, Chiradeep Vittal wrote:
>>> Nux, that's an entirely different problem. Care to raise a feature
>>> request?
>>
>>It's been here for a while:
>>https://issues.apache.org/jira/browse/CLOUDSTACK-5305
>>
>>It's a major PITA for me (and I imagine for anyone else who wants to
>>sell cloud publicly).
>>
>>--
>>Sent from the Delta quadrant using Borg technology!
>>
>>Nux!
>>www.nux.ro
>

Reply via email to