Re: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]

David Allan I <david.i.allan@ericsson.com> Wed, 15 February 2012 15:45 UTC

Return-Path: <david.i.allan@ericsson.com>
X-Original-To: armd@ietfa.amsl.com
Delivered-To: armd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781BD21F8669 for <armd@ietfa.amsl.com>; Wed, 15 Feb 2012 07:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.355
X-Spam-Level:
X-Spam-Status: No, score=-6.355 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 YIEGS3ABaLP5 for <armd@ietfa.amsl.com>; Wed, 15 Feb 2012 07:45:13 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 53CB421F8623 for <armd@ietf.org>; Wed, 15 Feb 2012 07:45:13 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1FFj3GX023890; Wed, 15 Feb 2012 09:45:08 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.142]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 15 Feb 2012 10:45:06 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>, Aldrin Isaac <aldrin.isaac@gmail.com>, Thomas Narten <narten@us.ibm.com>
Date: Wed, 15 Feb 2012 10:45:04 -0500
Thread-Topic: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]
Thread-Index: AQHM6+tz2aQ3CA7uUUiJzv2UoHOYiJY+jZEA//+DSwCAAAdAcA==
Message-ID: <60C093A41B5E45409A19D42CF7786DFD522A9BE827@EUSAACMS0703.eamcs.ericsson.se>
References: <4D9F477D-70C5-44B7-8146-992579B0D543@gmail.com> <7AE6A4247B044C4ABE0A5B6BF427F8E291E4DB@dfweml503-mbx>
In-Reply-To: <7AE6A4247B044C4ABE0A5B6BF427F8E291E4DB@dfweml503-mbx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "armd@ietf.org" <armd@ietf.org>
Subject: Re: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]
X-BeenThere: armd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of issues associated with large amount of virtual machines being introduced in data centers and virtual hosts introduced by Cloud Computing." <armd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/armd>, <mailto:armd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/armd>
List-Post: <mailto:armd@ietf.org>
List-Help: <mailto:armd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/armd>, <mailto:armd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 15:45:17 -0000

We do need to be clear between protocols that leverage layer 2 broadcast and multicast vs. those that genuinely need layer 3 and the multicast group spans multiple subnets.

I suspect we are really discussing the former, the latter looks to me like complexity well beyond what a pool of VMs supporting an application need to autodiscover and self organize.

That an overlay may use IP multicast at the server layer to virtualize layer 2 broadcast/multicast is a separate issue.

Cheers
Dave

-----Original Message-----
From: armd-bounces@ietf.org [mailto:armd-bounces@ietf.org] On Behalf Of AshwoodsmithPeter
Sent: Wednesday, February 15, 2012 7:35 AM
To: Aldrin Isaac; Thomas Narten
Cc: armd@ietf.org
Subject: Re: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]

> My impression is that many data centers do not enable IP multicast on 
> their routers. That means you can use link-local multicast (which 
> works fine within one IP subnet and doesn't really have scaling 
> issues). But if you want multicast that goes beyond one link (and IP 
> subnet), which is presumably necessary for an overlay like 
> VXLAN/NVGRE, that is where you have problems.

Agreed. If you extrapolate a bit and imagine VXLAN with 1000's of logical groups.. then that maps either to head end replication in the hypervisor, or to IGMP from the hypervisor and PIM between the TOR and CORE 'switches' and the gateway router.

> The question is not even whether L3 multicast scales. It's whether the 
> DC operater is willing to enable such multicast.

No choice if you want to run a Layer 2 Emulation over IP and you care about multicast banwdidh effeciency.

This highlights one of the major differences between the L2 over IP and L2 over L2 solutions, i.e. signalling v.s. computation for the multicast state.

This is why I think an understanding of the true uses of that multicast is important because if 90% of the applications are only finding each other and signalling each other using multicast there are better ways but if they are truly multicasting data in large volumes .. well we need extremely good underlay multicast scale.

Peter



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