Re: [alto] How Data Center Virtualization influence ALTO mechanism.

"Y.J. GU" <guyingjie@huawei.com> Wed, 13 October 2010 03:29 UTC

Return-Path: <guyingjie@huawei.com>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D7693A6B33 for <alto@core3.amsl.com>; Tue, 12 Oct 2010 20:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.716
X-Spam-Level:
X-Spam-Status: No, score=-98.716 tagged_above=-999 required=5 tests=[AWL=1.178, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikEpEOCfMbom for <alto@core3.amsl.com>; Tue, 12 Oct 2010 20:29:28 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 9BEFA3A6B26 for <alto@ietf.org>; Tue, 12 Oct 2010 20:29:27 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA700AYFLP6ZZ@szxga04-in.huawei.com> for alto@ietf.org; Wed, 13 Oct 2010 11:29:31 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA7003WVLP6WF@szxga04-in.huawei.com> for alto@ietf.org; Wed, 13 Oct 2010 11:29:30 +0800 (CST)
Received: from g00107907 ([10.138.41.80]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA7004LWLP6D5@szxml04-in.huawei.com> for alto@ietf.org; Wed, 13 Oct 2010 11:29:30 +0800 (CST)
Date: Wed, 13 Oct 2010 11:29:41 +0800
From: "Y.J. GU" <guyingjie@huawei.com>
In-reply-to: <AANLkTi=V0YnzzKGih5F-2uOXzCkrD1wimSSmf1uo9s2R@mail.gmail.com>
To: 'Tao Ma' <abcdmatao@gmail.com>
Message-id: <005e01cb6a86$df92c190$50298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_2eF8T6ATTemKaiBn5wdwdg)"
Thread-index: Actpt3czCnketqwAQHKfUimi7zSIwgAx7kmA
Cc: 'chunhong zhang' <zhangchbupt@gmail.com>, wifnstone@gmail.com, miwei1985@gmail.com, alto@ietf.org
Subject: Re: [alto] How Data Center Virtualization influence ALTO mechanism.
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 03:29:30 -0000

Hi,

Good question. I don’t know how this is guaranteed in real world. But there are some discussions on this. 

HSRP is one way. IP mobility is another example.  

 

  _____  

From: Tao Ma [mailto:abcdmatao@gmail.com] 
Sent: Tuesday, October 12, 2010 10:45 AM
To: guyingjie@huawei.com
Cc: qiuxiaofeng@gmail.com; alto@ietf.org; chunhong zhang; wifnstone@gmail.com; miwei1985@gmail.com
Subject: Re: [alto] How Data Center Virtualization influence ALTO mechanism.

 

Hi,
    I think it is an interesting aspect for ALTO protocol to be considered. The current ALTO uses IP address as the endpoint adress for grouping and locating. For the VM migration, this would fail, especailly without the contol of the ISP or ALTO service provider. Can ALTO mechanism make some changes to reflect this migration in some way? By using other alternatives such as geolocations or PoP to group, can we avoid this and how?
PS: I have a question personally. How the routing would succeed after VM are migrated without changing IP adress? Can you tell me some current mechanism? Thanks:)
Tao Ma
Beijing University of Posts and Telecommunications 
 

From: Y.J. GU <guyingjie@huawei.com>
Date: Sat, Oct 9, 2010 at 3:18 AM
Subject: [alto] How Data Center Virtualization influence ALTO mechanism.
To: alto@ietf.org


Hi all,
I was thinking about how Data Center Virtualization and Virtual Machine(VM) Migration will influence ALTO mechanism.

Current ALTO Protocol defines clustering of peers according to their IP Addresses. E.g. peers in same subnet will be classified into same PID, and path cost will indicate the cost within and between PIDs, which is also actually based on IP Addresses.

In the current world, peers are partitioned by IP subnet. While considering virtual machines migration, there might be more interesting things to think of.

In Data Center operation, one basic consensus is 'When Virtual Machines move from one site to another, the IP Addresses will not change, so that the existing service connection will not be broken'.  VMs can migrate to arbitrary site, not under the control and knowledge of ISP. For example, some VMs in Data Center A(IP subnet 198.1.1.0) move to Data Center B (IP subnet 210.1.1.0). IP-based, Vms are closer to DC-A. Physically, these VMs are much closer to hosts in DC-B. However things are not so easy, especially considering how these VMs are routed. Current ALTO may give wrong cost ranking.

VMs may migrate under, but not limited to, these situations: 1) to save electricity power, 2) disaster recovery, 3) customer prefer another Data Center, 4) company extension, etc. In the end, the internet will not be a regular world partitioned by IP Addresses.

Does anyone think this is an interesting aspect to study?



_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto