Re: [armd] soliciting typical network designs for ARMD
Vishwas Manral <vishwas.ietf@gmail.com> Tue, 09 August 2011 17:58 UTC
Return-Path: <vishwas.ietf@gmail.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 5028F21F8A95 for <armd@ietfa.amsl.com>; Tue, 9 Aug 2011 10:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.937
X-Spam-Level:
X-Spam-Status: No, score=-2.937 tagged_above=-999 required=5 tests=[AWL=0.661, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 rfTvd5tUDNzd for <armd@ietfa.amsl.com>; Tue, 9 Aug 2011 10:58:04 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCE521F8A23 for <armd@ietf.org>; Tue, 9 Aug 2011 10:58:04 -0700 (PDT)
Received: by qwc23 with SMTP id 23so164301qwc.31 for <armd@ietf.org>; Tue, 09 Aug 2011 10:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PLUdRhEW63VA6EDqwByv3OJfF9MDBU2awpfVz8p7LWA=; b=p0e6gEpWEXw3qEfYZYRhYpObLXkQIQ0nh99O0jeC1gax242BmKD3WytEkVIKDuQDly EjoYH+4mT1j78w+fWgG/Tn8G9FbFe0UH/StypVnVkvqZ7iQcoe7jewH+QkDpF757kMDu eJc1kXDddPssQL2MxQ8EW+ekcwGrTTjdIYAcA=
MIME-Version: 1.0
Received: by 10.229.107.5 with SMTP id z5mr5265755qco.229.1312912711067; Tue, 09 Aug 2011 10:58:31 -0700 (PDT)
Received: by 10.229.65.91 with HTTP; Tue, 9 Aug 2011 10:58:30 -0700 (PDT)
In-Reply-To: <CAP_bo1b_2D=fbJJ8uGb8LPWb-6+sTQn1Gsh9YAp8pFs3JY_rrw@mail.gmail.com>
References: <CAP_bo1b_2D=fbJJ8uGb8LPWb-6+sTQn1Gsh9YAp8pFs3JY_rrw@mail.gmail.com>
Date: Tue, 09 Aug 2011 10:58:30 -0700
Message-ID: <CAOyVPHTLYv=-GbjimpDr5NsxMUeWKtVKzStY9yxQO7s4YD2Ywg@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Linda Dunbar <dunbar.ll@gmail.com>
Content-Type: multipart/alternative; boundary="0023544711bcc3a7a404aa164fca"
Cc: armd@ietf.org
Subject: Re: [armd] soliciting typical network designs for ARMD
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: Tue, 09 Aug 2011 17:58:05 -0000
Hi Linda, I am unsure what you mean by this, but: 1. layer 3 all the way to TOR (Top of Rack switches), We can also have a heirarchical network, with the core totally Layer-3 (and having seperate routing), from the hosts still in a large Layer-3 subnet. Another aspect could be to have a totally Layer-3 network. The difference between them is the link between the servers and the ToR. Thanks, Vishwas On Tue, Aug 9, 2011 at 10:22 AM, Linda Dunbar <dunbar.ll@gmail.com> wrote: > During the 81st IETF ARMD WG discussion, it was suggested that it is > necessary to document typical data center network designs so that address > resolution scaling issues can be properly described. Many data center > operators have expressed that they can't openly reveal their detailed > network designs. Therefore, we only want to document anonymous designs > without too much detail. During the journey of establishing ARMD, we have > come across the following typical data center network designs: > > 1. layer 3 all the way to TOR (Top of Rack switches), > 2. large layer 2 with hundreds (or thousands) of ToRs being > interconnected by Layer 2. This design will have thousands of hosts under > the L2/L3 boundary router (s) > 3. CLOS design with thousands of switches. This design will have > thousands of hosts under the L2/L3 boundary router(s) > > We have heard that each of the designs above has its own problems. ARMD > problem statements might need to document DC problems under each typical > design. > Please send feedback to us (either to the armd email list or to the ARMD > chair Benson & Linda) to indicate if we have missed any typical Data Center > network designs. > > Your contribution can greatly accelerate the progress of ARMD WG. > > Thank you very much. > > Linda & Benson >
- [armd] soliciting typical network designs for ARMD Linda Dunbar
- Re: [armd] soliciting typical network designs for… Vishwas Manral
- Re: [armd] soliciting typical network designs for… Linda Dunbar
- Re: [armd] soliciting typical network designs for… Vishwas Manral
- Re: [armd] soliciting typical network designs for… Vishwas Manral
- Re: [armd] soliciting typical network designs for… Anoop Ghanwani
- Re: [armd] soliciting typical network designs for… Anoop Ghanwani
- Re: [armd] soliciting typical network designs for… Vishwas Manral
- Re: [armd] soliciting typical network designs for… Warren Kumari
- Re: [armd] soliciting typical network designs for… Linda Dunbar
- Re: [armd] soliciting typical network designs for… david.black
- Re: [armd] soliciting typical network designs for… Murari Sridharan
- [armd] how does "draft-sridharan-virtualization-n… Linda Dunbar
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] soliciting typical network designs for… Balus, Florin Stelian (Florin)
- Re: [armd] how does "draft-sridharan-virtualizati… Linda Dunbar
- Re: [armd] soliciting typical network designs for… Joel M. Halpern
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Murari Sridharan
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Murari Sridharan
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Murari Sridharan
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Murari Sridharan
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Gary Berger
- Re: [armd] soliciting typical network designs for… Warren Kumari
- Re: [armd] how does "draft-sridharan-virtualizati… Linda Dunbar
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Benson Schliesser
- Re: [armd] how does "draft-sridharan-virtualizati… Narasimhan Venkataramaiah
- Re: [armd] how does "draft-sridharan-virtualizati… Gary Berger
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Linda Dunbar
- Re: [armd] how does "draft-sridharan-virtualizati… Michael Smith
- Re: [armd] how does "draft-sridharan-virtualizati… Vishwas Manral
- Re: [armd] how does "draft-sridharan-virtualizati… Gary Berger (gaberger)
- [armd] Multi-homing in data center Linda Dunbar
- Re: [armd] Multi-homing in data center Gary Berger
- Re: [armd] how does "draft-sridharan-virtualizati… Michael Smith
- Re: [armd] how does "draft-sridharan-virtualizati… david.black