IETF Logo Mail Archive

[sami] 答复: First SAMI email in the new year, can we go further? Look forward to your opinions.

"Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com> Fri, 02 March 2012 02:32 UTC

Return-Path: <zhangdacheng@huawei.com>
X-Original-To: sami@ietfa.amsl.com
Delivered-To: sami@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A79B121E80D5 for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 18:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level:
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=-1.562, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7PnnHETFWBJK for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 18:32:16 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE1A21E8012 for <sami@ietf.org>; Thu, 1 Mar 2012 18:32:16 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M08007PYKDJD1@szxga03-in.huawei.com> for sami@ietf.org; Fri, 02 Mar 2012 10:32:07 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M08001UYKCNBS@szxga03-in.huawei.com> for sami@ietf.org; Fri, 02 Mar 2012 10:32:07 +0800 (CST)
Received: from szxeml209-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHN68609; Fri, 02 Mar 2012 10:32:05 +0800
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 02 Mar 2012 10:31:30 +0800
Received: from SZXEML528-MBX.china.huawei.com ([169.254.4.52]) by szxeml412-hub.china.huawei.com ([10.82.67.91]) with mapi id 14.01.0323.003; Fri, 02 Mar 2012 10:31:53 +0800
Date: Fri, 02 Mar 2012 02:31:53 +0000
From: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
In-reply-to: <20120301172841.GB33202@elstar.local>
X-Originating-IP: [10.108.4.58]
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
Message-id: <C72CBD9FE3CA604887B1B3F1D145D05E120626C8@szxeml528-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="gb2312"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: zh-CN, en-US
Thread-topic: [sami] First SAMI email in the new year, can we go further? Look forward to your opinions.
Thread-index: Acz3SUkn2F6H2TiuReyy+E4fTWsLVgARGdSAACMoBnA=
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-hashedpuzzle: AkQN Arg6 Eg71 EiiF E809 FncX Ha/g LqxY N257 OPbx PRW7 R3r9 T3mL T9Dl UYhB UqJ6; 2; agAuAHMAYwBoAG8AZQBuAHcAYQBlAGwAZABlAHIAQABqAGEAYwBvAGIAcwAtAHUAbgBpAHYAZQByAHMAaQB0AHkALgBkAGUAOwBzAGEAbQBpAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {C0C8A05D-1162-4923-8B39-CEBD665EAAD2}; egBoAGEAbgBnAGQAYQBjAGgAZQBuAGcAQABoAHUAYQB3AGUAaQAuAGMAbwBtAA==; Fri, 02 Mar 2012 02:31:47 GMT; VHsNWToAIABbAHMAYQBtAGkAXQAgAEYAaQByAHMAdAAgAFMAQQBNAEkAIABlAG0AYQBpAGwAIABpAG4AIAB0AGgAZQAgAG4AZQB3ACAAeQBlAGEAcgAsACAAYwBhAG4AIAB3AGUAIABnAG8AIABmAHUAcgB0AGgAZQByAD8AIABMAG8AbwBrACAAZgBvAHIAdwBhAHIAZAAgAHQAbwAgAHkAbwB1AHIAIABvAHAAaQBuAGkAbwBuAHMALgA=
x-cr-puzzleid: {C0C8A05D-1162-4923-8B39-CEBD665EAAD2}
X-CFilter-Loop: Reflected
References: <A27496C192613C44A82D819E1B98DB5721DAE9A6@SZXEML511-MBS.china.huawei.com> <20120301172841.GB33202@elstar.local>
Cc: "sami@ietf.org" <sami@ietf.org>
Subject: [sami] 答复: First SAMI email in the new year, can we go further? Look forward to your opinions.
X-BeenThere: sami@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: State Migration <sami.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sami>, <mailto:sami-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sami>
List-Post: <mailto:sami@ietf.org>
List-Help: <mailto:sami-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sami>, <mailto:sami-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 02:32:16 -0000

>> 
>> Lets assume VM migration happens today (which I am fine to assume - I
>> am however unsure how frequent live migration takes place and hence
>> whether its worth to optimize for it).
[Dacheng Zhang] I think this will happen quite frequently in some conditions. Assume for energy conversation purpose at night an operator of a DC can move active VMs to several physical servers and switch other physical servers off. In this case, migration will happen very day.

>> 
>> That said, this assumption alone does not necessarily imply there is a
>> state migration problem worth to be solved by the IETF. I am missing
>> statements from VMware engineers (since you mention VMotion) or the
>> like where they explain how IETF protocol work can help them to make
>> their migration solutions work even better as they do.
[Dacheng Zhang] 
Agree. If we all agree that VM migration is happening or will happen in DC, it is the right time to discuss where there are any important scenarios where state migration across network side devices is necessary.

By the way, there is a Cisco white paper " Virtual Machine Mobility with Vmware VMotion and Cisco Data Center Interconnect Technologies". I personally think it is quite interesting. Anybody having interests can download it and have a look. ^_^


Cheers

Dacheng

v2.23.0 | Report a Bug | By Email