I'm trying to think how it actually affects the service itself or the end user experience. It does not, does it?
Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: David Nalley [mailto:da...@gnsa.us] Sent: 21 December 2012 16:44 To: cloudstack-dev@incubator.apache.org Cc: Musayev, Ilya Subject: Re: [PROPOSAL] Raise cluster size limit to 16 on VMware On Fri, Dec 21, 2012 at 5:46 AM, Tamas Monos <tam...@veber.co.uk> wrote: > The end user will have no idea what linked-in or full clone means so I would > recommend not to reflect this to the end user in any way especially in the > deployment wizard. > There should be a global option for this and the deployment api would use > that value. Only admins should be able to change cloning behaviour. Defining it in the service offering would make more sense to me. --David
