[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13929775#comment-13929775
 ] 

Marcus Sorensen commented on CLOUDSTACK-6181:
---------------------------------------------

I've added some integration tests, so I think we're fairly close to requesting 
merge. Let me know your findings.

1. Nux testing ...IN PROGRESS
2. tests ...DONE (could add a few more tests but the basic ones are there)
3. tests ...DONE 
4. Wido buyoff ...DONE
5. Mike buyoff ...DONE 
6. Other hypervisor support ... queried but seemingly no response. This isn't 
necessary to move forward because the parameter is rejected if hypervisor != 
KVM. They can support it in the future if they like. ...DONE
7. Still discussing parameter format ... IN PROGRESS
8. Finally, get UI support added in (not necessary, but would be nice). Have 
not heard on this. Generally UI support comes after features, though, so it's 
not a big deal.

> Root resize
> -----------
>
>                 Key: CLOUDSTACK-6181
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller, Storage Controller, UI
>    Affects Versions: 4.4.0
>         Environment: KVM/libvirt/CentOS, Xenserver
>            Reporter: Nux
>              Labels: disk, resize, template
>             Fix For: 4.4.0
>
>
> Rationale:
> Currently the root size of an instance is locked to that of the template. 
> This creates unnecessary template duplicates, prevents the creation of a 
> market place, wastes time and disk space and generally makes work more 
> complicated.
> Real life example - a small VPS provider might want to offer the following 
> sizes (in GB):
> 10,20,40,80,160,240,320,480,620
> That's 9 offerings.
> The template selection could look like this, including real disk space used:
> Windows 2008 ~10GB
> Windows 2008+Plesk ~15GB
> Windows 2008+MSSQL ~15GB
> Windows 2012 ~10GB
> Windows 2012+Plesk ~15GB
> Windows 2012+MSSQL ~15GB
> CentOS ~1GB
> CentOS+CPanel ~3GB
> CentOS+Virtualmin ~3GB
> CentOS+Zimbra ~3GB
> CentOS+Docker ~2GB
> Debian ~1GB
> Ubuntu LTS ~1GB
> In this case the total disk space used by templates will be 828 GB, that's 
> almost 1 TB. If your storage is expensive and limited SSD this can get 
> painful!
> If the root resize feature is enabled we can reduce this to under 100 GB.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to