Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79595E1D3 for ; Wed, 16 Jan 2013 02:35:29 +0000 (UTC) Received: (qmail 57248 invoked by uid 500); 16 Jan 2013 02:35:28 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 57164 invoked by uid 500); 16 Jan 2013 02:35:27 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 57152 invoked by uid 99); 16 Jan 2013 02:35:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 02:35:27 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.149.197] (HELO na3sys009aog107.obsmtp.com) (74.125.149.197) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 02:35:19 +0000 Received: from mail-yh0-f69.google.com ([209.85.213.69]) (using TLSv1) by na3sys009aob107.postini.com ([74.125.148.12]) with SMTP ID DSNKUPYR0dfR/crEHA2JuAyWhWqQJJ7f19vH@postini.com; Tue, 15 Jan 2013 18:34:59 PST Received: by mail-yh0-f69.google.com with SMTP id i57so1376272yha.0 for ; Tue, 15 Jan 2013 18:34:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=6z2B4UkMdlIvLnKE9zJOVB435CkLiyJmf46HeDUL/wY=; b=Zv05doLfRoZGwzOE/rFm2AZUsew2nZR06fMizcmmjVhSbDzadh9sg5flDQi4P2msSW RiAiXsv5ILwVVN+3rjtJgTe/AGqTvS2uNqzvCDJRdKBpfqQp9zGC7XNFE7cuysEEokbD j0HrpWE1e6f4HB5hTa1wYOeHGJFnKiAlmwdxev0kbbkqi9fYV6ADnXY8Uisp1qkSqlh9 uG1rhh+lhpSZ6OzjJ21LXA2JHyqA9DLzyLAEWdxMNgMjMjFmE0pYFIMLHujfyiJ9IgmH 7UaTM/v8t1xwkRMxglpI4wQGnbcFEoJnniCOiVM8yhIX9gPM8WRod+Vp91x2FQi7cvjR LE5Q== X-Received: by 10.52.66.34 with SMTP id c2mr92603065vdt.62.1358303696264; Tue, 15 Jan 2013 18:34:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.66.34 with SMTP id c2mr92603062vdt.62.1358303696128; Tue, 15 Jan 2013 18:34:56 -0800 (PST) Received: by 10.220.249.198 with HTTP; Tue, 15 Jan 2013 18:34:56 -0800 (PST) In-Reply-To: References: <2529883E7B666F4E8F21F85AADA43CA7010C8EB1B92E@BANPMAILBOX01.citrite.net> <2529883E7B666F4E8F21F85AADA43CA7010C8EB1C2C0@BANPMAILBOX01.citrite.net> <6E004C34C1C59E45A35B4338808BC315013014D30E3D@SJCPMAILBOX01.citrite.net> <67EF18FDCA335F489B366120481AB6C5F6B38A44B9@BANPMAILBOX01.citrite.net> <2529883E7B666F4E8F21F85AADA43CA7010C8F171DAE@BANPMAILBOX01.citrite.net> Date: Tue, 15 Jan 2013 21:34:56 -0500 Message-ID: Subject: Re: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 From: Chris Sears To: cloudstack-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf307f35c24e0a3f04d35eb90e X-Gm-Message-State: ALoCoQnOMI89YPr3a3nyT2S2cDLsRUnYAOjR71s8V0NVYZhEhQ/0tduzQqaazchdXquCoUdDvuKdHzGvt/j7oac5EkBRh+JCEXrxoNdGaUKRsxsoV1xua5kVckYhAKv+xZO2wn11xaxHYYypPZHmPMxsIVs8LGYojyep3mRNIeV+ZSS89qKVzruKq9bw+wyx3A0mcK78Pq9/ X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f35c24e0a3f04d35eb90e Content-Type: text/plain; charset=ISO-8859-1 If we are thinking about VMware compatibility, there are a number of factors can prevent a VM from being eligible for storage vMotion: http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc_50%2FGUID-A16BA123-403C-4D13-A581-DC4062E11165.html On vSphere versions before 5.0, having snapshots or linked clones will also disqualify a VM for storage vMotion. In 5.0 and later, this is not a limitation. ESX 4.x hosts running the Standard or Advanced edition do not support Storage vMotion, whereas Enterprise or Enterprise Plus editions do support it. Can these be accounted for using the hypervisor_capabilities table? - Chris On Tue, Jan 15, 2013 at 7:16 PM, Alex Huang wrote: > Devdeep, > > I read the FS and have the following questions. > > - My understanding is that XenServer implements XenMotion by using > snapshots and that CloudStack's snapshots can interfere with this process. > This understanding might be old. Can you confirm that this is not the > case? If it is the case, how do you plan on dealing with that? > - I like to see exactly the API flow someone should execute this with. I > had one question that remains unanswered which is are we planning to > retrieve a list of available hosts and storage pools to migrate to. From > the listHosts API that seems to be the case but what if it is only storage > pool migration? > - Are we planning to add APIs to storagepool allocator to make the > selection of storage pool portion work? Is the current API enough? I see > a flow for the actual migration but I don't see a flow for selecting what > to migrate to. > - Currently preparation on the destination host to migrate is done by > management server, in the flow in the FS, it is now being done by the > source agent. What's the pros/cons of this change? I see that as an open > issue on your spec and I think if we can keep the hosts from establishing > contact with each other it will be best. > - I like to see the full API speced out. > > I also like to see Hari's question answered. Can we provide this with > VmWare as well? > > --Alex > > > -----Original Message----- > > From: Devdeep Singh [mailto:devdeep.singh@citrix.com] > > Sent: Tuesday, January 08, 2013 1:58 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: RE: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 > > > > Hi Swamy, > > > > In the following scenario when a VM has disks in different repositories, > all > > the virtual disks of the VM will be moved to the same destination > repository. > > Moving individual disks of the VM to different repositories can be done, > but > > it'll involve taking inputs from the user as to which disk should be > moved to > > which repository. What do you think, should this option be also provided? > > > > Regards, > > Devdeep > > > > > -----Original Message----- > > > From: Venkata SwamyBabu Budumuru > > > [mailto:venkataswamybabu.budumuru@citrix.com] > > > Sent: Thursday, December 27, 2012 5:42 PM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: RE: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 > > > > > > Hi Devdeep, > > > > > > Does this also cover the following use case ? > > > > > > VM1 => ROOT (Storage Repository 1) > > > => DATA-1 (Storage Repository 2) > > > > > > Can I migrate DATA-1 vdi alone to a different repository? Or Is this > feature > > > allowing the whole VM (including ROOT and DATA-1) to same destination > > > repository? > > > > > > Thanks, > > > SWAMY > > > -----Original Message----- > > > From: Hari Kannan [mailto:hari.kannan@citrix.com] > > > Sent: Thursday, December 27, 2012 2:18 AM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: RE: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 > > > > > > Hi Devdeep, > > > > > > Should this discussion be expanded to cover VMware storage migration or > > a > > > different discussion - I wish to see how we can add vSphere as a > supported > > > platform for this feature.. > > > > > > Hari > > > > > > -----Original Message----- > > > From: Devdeep Singh [mailto:devdeep.singh@citrix.com] > > > Sent: Wednesday, December 26, 2012 4:44 AM > > > To: cloudstack-dev@incubator.apache.org > > > Subject: RE: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 > > > > > > I have created an initial draft of the FS here > > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storag > > e+ > > > XenMotion+for+XenServer. I'll keep updating it based on discussion and > > > comments. > > > > > > Regards, > > > Devdeep > > > > > > > -----Original Message----- > > > > From: Devdeep Singh [mailto:devdeep.singh@citrix.com] > > > > Sent: Tuesday, December 18, 2012 2:10 PM > > > > To: cloudstack-dev@incubator.apache.org > > > > Subject: [DISCUSS] Enabling storage xenmotion on xenserver 6.1 > > > > > > > > Hi, > > > > > > > > XenServer introduced support for Storage XenMotion in the latest > > > > version (6.1). Storage XenMotion allows VMs to be moved from one host > > > > to another, where the VMs are not located on storage shared between > > > > the two hosts. It provides the option to live migrate a VM's disks > > > > along with the VM itself. It is now possible to migrate a VM from one > > > > resource pool to another, or to migrate a VM whose disks are on local > > > > storage, or even to migrate a VM's disks from one storage repository > > > > to another, all while the VM is running. More information on Storage > > > XenMotion can be found at [1]. > > > > > > > > I have filed a jira request [2] to track this feature. I plan to > > > > extend the migrate vm cloudstack api call to allow migration of > > > > instances across clusters. Do let me know your comments. > > > > > > > > [1] http://blogs.citrix.com/2012/08/24/storage_xenmotion/ > > > > [2] https://issues.apache.org/jira/browse/CLOUDSTACK-659 > > > > > > > > Regards, > > > > Devdeep > > --20cf307f35c24e0a3f04d35eb90e--