@Daniele and Vitaily, the limit is **ONLY** 1TB for _Magnetic_ storage.  If 
you use SSD / PIOPS, then the limit is 16TB.  This is still a bug.


AS per the announcement here 

https://aws.amazon.com/blogs/aws/larger-faster-ebs-ssd-volumes/


and the details here:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html



And since Scalr lets me choose the storage type (magnetic, ssd, pIOPS) i'd 
expect that the limit changes accordingly, too!


<https://lh3.googleusercontent.com/-j0FpubQFOZA/Ve9MbzC7QtI/AAAAAAAAADg/qBvqsPdVQ4M/s1600/Screen%2BShot%2B2015-09-08%2Bat%2B13.58.24.png>
I have attached a screenshot highlighting the 16TiB limit and the 
appropriate storage classes it applies to.




On Wednesday, August 26, 2015 at 6:59:50 AM UTC-7, Daniele Testa wrote:
>
> Seems the limit is still 1TB:
> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html
>
> Regards,
> Daniele
>
>
> On Wednesday, August 26, 2015 at 6:24:29 PM UTC+8, Daniele Testa wrote:
>>
>> Thanks for the bug report. This will be fixed in future versions. Thanks!
>>
>> Regards,
>> Daniele
>>
>> On Wednesday, August 26, 2015 at 1:50:16 AM UTC+8, 
>> [email protected] wrote:
>>>
>>> Here's what you can do to re-create this.
>>>
>>>
>>> 1) build a 3TB volume.
>>> 2) snapshot this volume.
>>> 3) attempt to have scalr mount this snapshot in the farm role editor.  
>>>
>>>
>>> Since the UI still prompts for a vol. size even though the snapshot is 
>>> chosen, my gut instinct was to set the size to the size of the snapshot 
>>> (3TB).  This is when scalr threw the error on attempt to save farm.
>>>
>>> However, it looks like the error that i've screenshotted here is only a 
>>> *warning*, as i can still save this farm role, refresh the page, and see my 
>>> settings appear to stick.
>>>
>>>
>>> -K
>>>
>>>
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to