From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike McClurg Subject: Re: FT for XCP Date: Mon, 26 Sep 2011 08:08:21 +0100 Message-ID: <4E8024E5.9020406@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1085696570==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org Errors-To: xen-api-bounces-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org To: R J Cc: "xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org" , "xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org" , "xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org" List-Id: xen-devel@lists.xenproject.org --===============1085696570== Content-Type: multipart/alternative; boundary="------------090300050806030107000906" --------------090300050806030107000906 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 09/25/2011 09:11 PM, R J wrote: > Hello List, > > I have a proposal and wont mind to implement my self but need a > helping hand to start on. > I want to implement the aggressive FT feature in XCP. The best way I > could imagine is the use of feature *Live Migration* > > Steps > 1. Enable the FT of a particular VM using xe commands and adding as a > param to that VM e.g. xe vm-param-set FT=true uuid=XYZ > 2. If the FT = true detected by xenstore then xapi will initiate a > live migrate of that VM to any of available host. > 3. A parallel "network ping"/"xapi heartbit" from/to that host could > be initialized for each FT VM. > 4. Live migrate will run forever until its disabled by FT = false or > one of the host is down. e.g. the process will loop at 99.99% > migration state > 5. If there is a packet drop of x packets the VM Migrate procedure > will mark the VM Migration as Complete and will switch the devices > forcefully. > -- this could result in some data loss but I dont have any alternative > to this. > -- The specific x packets can be set by XCP but we cant rely for > default XCP Errors > 6. If there is a successful migration due to host down then we will > again start from step2 > > Above steps I have assumed to my knowledge, we can discuss the > problems in it. > > Apologies if I'm being too naive. > > Regards, > Rushikesh > This sounds like Remus (http://nss.cs.ubc.ca/remus/). Are you proposing to implement Remus support in xapi? Mike --------------090300050806030107000906 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 09/25/2011 09:11 PM, R J wrote:

Hello List,

I have a proposal and wont mind to implement my self but need a helping hand to start on.
I want to implement the aggressive FT feature in XCP. The best way I could imagine is the use of feature *Live Migration*

Steps
1. Enable the FT of a particular VM using xe commands and adding as a param to that VM e.g. xe vm-param-set FT=true uuid=XYZ
2. If the FT = true detected by xenstore then xapi will initiate a live migrate of that VM to any of available host.
3. A parallel "network ping"/"xapi heartbit" from/to that host could be initialized for each FT VM.
4. Live migrate will run forever until its disabled by FT = false or one of the host is down. e.g. the process will loop at 99.99% migration state
5. If there is a packet drop of x packets the VM Migrate procedure will mark the VM Migration as Complete and will switch the devices forcefully.
-- this could result in some data loss but I dont have any alternative to this.
-- The specific x packets can be set by XCP but we cant rely for default XCP Errors
6. If there is a successful migration due to host down then we will again start from step2

Above steps I have assumed to my knowledge, we can discuss the problems in it.

Apologies if I'm being too naive.

Regards,
Rushikesh

This sounds like Remus (http://nss.cs.ubc.ca/remus/). Are you proposing to implement Remus support in xapi?

Mike
--------------090300050806030107000906-- --===============1085696570== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1085696570==--