[
https://issues.apache.org/jira/browse/CLOUDSTACK-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556201#comment-13556201
]
Hari Kannan commented on CLOUDSTACK-670:
----------------------------------------
Hi Tamas,
The way I envision this is as follows - when a compute service offering is
created, admin can force this offering to be linked clone (or force this to be
full clone). If he does this, the end user has no choice - he will get what the
admin decided. Alternatively, the admin can leave the choice open - the end
user has to make one choice, whichever he chooses is OK.
This method is very similar to the storage offering we have today. The admin
decides the storage size - if he does, end user doesnt get to pick.
Alternative, the admin can create an offering where he will force the end user
to specify a size.
Does that make things a bit clearer?
> Configurable setting to use linked clones or not on VMware
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-670
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Hari Kannan
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Fix For: 4.1.0
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configurable+setting+to+use+linked+clones+or+not+on+VMware
> Functional Specification at:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Provide+full+clone+support+for+guest+VMs+on+VMWare+deployments+in+Cloudstack
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
