Re: [alto] How Data Center Virtualization influence ALTO mechanism.
stefano previdi <sprevidi@cisco.com> Wed, 13 October 2010 11:32 UTC
Return-Path: <sprevidi@cisco.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 96B5A3A69F0 for <alto@core3.amsl.com>; Wed, 13 Oct 2010 04:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, 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 2t-QGHkpZCQM for <alto@core3.amsl.com>; Wed, 13 Oct 2010 04:32:17 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 7D31F3A6A01 for <alto@ietf.org>; Wed, 13 Oct 2010 04:32:16 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o9DBMEq1010748; Wed, 13 Oct 2010 13:22:14 +0200 (CEST)
Received: from [192.168.62.100] (ams3-vpn-dhcp5884.cisco.com [10.61.86.251]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o9DBMDFY025143; Wed, 13 Oct 2010 13:22:13 +0200 (CEST)
Message-Id: <95CC4772-BE72-403D-A1E8-4696E61BA3B2@cisco.com>
From: stefano previdi <sprevidi@cisco.com>
To: "Y.J. GU" <guyingjie@huawei.com>
In-Reply-To: <006201cb6782$2cb463a0$45548a0a@china.huawei.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 13 Oct 2010 13:22:13 +0200
References: <006201cb6782$2cb463a0$45548a0a@china.huawei.com>
X-Mailer: Apple Mail (2.935.3)
Cc: 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 11:32:19 -0000
On Oct 9, 2010, at 9:18 AM, Y.J. GU wrote: > 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. the methods of grouping are orthogonal to ALTO protocol specification. There are ALTO implementations that allow address/prefixes grouping relaxed from pure IP aggregation. The fact that you use IP addresses in the protocol doesn't mean that locality is solely based on address/mask pairs. It is mostly a policy definition by the ALTO and infrastructure operator. > 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. that is true. ALTO relies on accurate infrastructure/topology information. It can be derived from lower layers (routing and below) or inferred by policy DBs. > 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. the "swamp" already validated the theory... > Does anyone think this is an interesting aspect to study? probably yes but I'm not sure I see the protocol implication. s.
- [alto] How Data Center Virtualization influence A… Y.J. GU
- Re: [alto] How Data Center Virtualization influen… Tao Ma
- Re: [alto] How Data Center Virtualization influen… Lars Eggert
- Re: [alto] How Data Center Virtualization influen… Enrico Marocco
- Re: [alto] How Data Center Virtualization influen… Y.J. GU
- Re: [alto] How Data Center Virtualization influen… stefano previdi
- Re: [alto] How Data Center Virtualization influen… Y.J. GU
- Re: [alto] How Data Center Virtualization influen… Tao Ma