incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <imusa...@webmd.net>
Subject RE: Functional Specification for Full clone support for CS VMWare deployments
Date Wed, 20 Feb 2013 03:37:57 GMT
Understood, I will test this out and let you know what happens.

Would you know if it will be done as per original specifications in the near future?

Presently boolean logic is good progress, but it takes away the hybrid ability and I may have
to flop back and forth in order to have some vms as full clones (prod) and some (like dev/qa/test)
as link.

Thanks
ilya


-----Original Message-----
From: Hari Kannan [mailto:hari.kannan@citrix.com] 
Sent: Tuesday, February 19, 2013 7:28 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Hi Ilya,

It appears that this version will only support the " boolean global configuration parameter"
- as it is noted in the FS under use cases where it says " Approach a) above will be taken
in implementing this feature" 

Hari

-----Original Message-----
From: Musayev, Ilya [mailto:imusayev@webmd.net]
Sent: Tuesday, February 19, 2013 4:04 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Vijay and Hari,

I've looked at the patch as well as the docs listed below, here is the part that confuses
me.

The functional spec says we will user either per cluster setting for full or linked clone
or create a system/disk offering with this option - which was the agreed approach.

However, then I see that we use New global parameter flag : vmware.create.full.clone - so
we still have the ability to selectively choose what type of disk we can get, or is it major
on/off switch that we support at the moment.

Please kindly clarify, I'm planning to test this patch out tomorrow,

Thanks
ilya

-----Original Message-----
From: Vijayendra Bhamidipati [mailto:vijayendra.bhamidipati@citrix.com]
Sent: Friday, January 25, 2013 8:56 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Hi Tamas, Hari, Ilya!

Thank you for your inputs. I've updated the FS with more details incorporating these for further
review by the community:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Provide+full+clone+support+for+guest+VMs+on+VMWare+deployments+in+Cloudstack

Thanks,
Regards,
Vijay

-----Original Message-----
From: Tamas Monos [mailto:tamasm@veber.co.uk]
Sent: Wednesday, January 23, 2013 7:47 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Hi,

A linked-clone conversion into full-clone would be very useful feature!
+1

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: Musayev, Ilya [mailto:imusayev@webmd.net]
Sent: 22 January 2013 20:01
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Hari

I would like to comment on two open questions:

   - If a VM is created as a linked clone, there is no need to make it non-linked clone afterwards
(or vice-versa)

   - similarly, if upgrading from 4.0 to 4.1, VMs created in 4.0 (linked clones) dont need
to be allowed to become non-linked clones

We can convert the existing link clone to full clone - by full cloning the VM. Why would not
you want that ability? I actually would very much prefer that option - as I have to guarantee
disk reliability of that VM. 
The way I envision this, if the host needs to be promoted to a production, to add an extra
layer of safety on disk level - would prefer that ability. Conceptually, to achieve this we
can use vmware APIs to migrate and instead of migrating - just making it thin/thick. Just
like you can do so in VmWare now. Alternatively, we can initate a shutdown command and do
the same task in cold state.

Thoughts?

Thanks
ilya
 



-----Original Message-----
From: Hari Kannan [mailto:hari.kannan@citrix.com]
Sent: Tuesday, January 22, 2013 2:09 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

I also added a couple of questions here https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configurable+setting+to+use+linked+clones+or+not+on+VMware


-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
Sent: Tuesday, January 22, 2013 11:00 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Functional Specification for Full clone support for CS VMWare deployments

Vijay do you have any updates to share with community? 

Folks please provide your comments.

Animesh

> -----Original Message-----
> From: Vijayendra Bhamidipati
> [mailto:vijayendra.bhamidipati@citrix.com]
> Sent: Wednesday, January 16, 2013 5:39 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Functional Specification for Full clone support for CS VMWare 
> deployments
> 
> Please find the FS for the full clone support feature for vmware 
> deployments in cloudstack at:
> 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Provide+full+cl
> o
> ne+support+for+guest+VMs+on+VMWare+deployments+in+Cloudstack
> 
> Please note that the FS will be updated in the near future with more details.
> Please do provide comments/suggestions/pointers if you have any, that 
> would always be helpful.
> 
> Thanks,
> Regards,
> Vijay
> 










Mime
View raw message