Re: [bmwg] A new draft aimed at bmwg

"MORTON, ALFRED C (AL)" <acm@research.att.com> Fri, 22 March 2019 08:28 UTC

Return-Path: <acm@research.att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C58AB130EA1 for <bmwg@ietfa.amsl.com>; Fri, 22 Mar 2019 01:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQEMt_jzksh7 for <bmwg@ietfa.amsl.com>; Fri, 22 Mar 2019 01:28:36 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C8FF130DEA for <bmwg@ietf.org>; Fri, 22 Mar 2019 01:28:36 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x2M8PMMR046098; Fri, 22 Mar 2019 04:28:32 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0048589.ppops.net-00191d01. with ESMTP id 2rcv1g065s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Mar 2019 04:28:32 -0400
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id x2M8STSg001788; Fri, 22 Mar 2019 03:28:31 -0500
Received: from zlp30499.vci.att.com (zlp30499.vci.att.com [135.46.181.149]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id x2M8SQJt001737; Fri, 22 Mar 2019 03:28:26 -0500
Received: from zlp30499.vci.att.com (zlp30499.vci.att.com [127.0.0.1]) by zlp30499.vci.att.com (Service) with ESMTP id 839274009E8B; Fri, 22 Mar 2019 08:28:26 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30499.vci.att.com (Service) with ESMTP id 628574009E8A; Fri, 22 Mar 2019 08:28:26 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id x2M8SQRs012196; Fri, 22 Mar 2019 03:28:26 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id x2M8SLQn011847; Fri, 22 Mar 2019 03:28:22 -0500
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-blue.research.att.com (Postfix) with ESMTP id E4B9FF151A; Fri, 22 Mar 2019 04:28:20 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0439.000; Fri, 22 Mar 2019 04:27:47 -0400
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: WB Lee <leewb@etri.re.kr>, "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] A new draft aimed at bmwg
Thread-Index: AdTVY9tv7YkGX6MVR5S114UAvq6Y0gAMBg4QArzrq6A=
Date: Fri, 22 Mar 2019 08:27:43 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF6C007AE8@njmtexg5.research.att.com>
References: <000601d4d565$1dfd26d0$59f77470$@etri.re.kr> <4D7F4AD313D3FC43A053B309F97543CF6C001DC5@njmtexg5.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF6C001DC5@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [88.128.80.82]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-22_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903220065
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/JmTQydusM2lT2vFHeZbJcsCXWrU>
Subject: Re: [bmwg] A new draft aimed at bmwg
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2019 08:28:39 -0000

Mr. Lee and co-authors,

I read your draft: it is a good start for this topic,
and have a few comments to share.

General:
Instantiation of containers, pods, and internetworking
with K8s is somewhat non-deterministic and apparently
NUMA-Node agnostic, which is one way of saying that 
performance will likely vary from one instantiation to
the next, and the next, etc.  It would be good to 
specifically mention repeated instantiation and testing 
to quantify the performance variation under these 
conditions.

Related to the Memory Management Unit POV, section 3.1:
Life-cycle operations usually require considerable memory transfers.
Does this also imply that memory access times in Container VNFs
will be be affected when host resources are committed to Life-cycle
operations on other VNFs (such as instantiation/migrqation/deletion)?
IOW, will the effects of Life-cycle management be greater in the 
containerized infrastructure than for hypervisor with VM-based VNFs?

thanks,
Al
(as a participant)
 

> -----Original Message-----
> From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of MORTON, ALFRED C
> (AL)
> Sent: Friday, March 8, 2019 4:52 AM
> To: WB Lee <leewb@etri.re.kr>; bmwg@ietf.org
> Subject: Re: [bmwg] A new draft aimed at bmwg
> 
> *** Security Advisory: This Message Originated Outside of AT&T ***.
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Thanks for your timely contribution,
> Mr. Lee and co-authors.
> I will certainly take time to review.
> 
> Al
> bmwg co-chair
> 
> > -----Original Message-----
> > From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of WB Lee
> > Sent: Thursday, March 7, 2019 11:12 PM
> > To: bmwg@ietf.org
> > Subject: [bmwg] A new draft aimed at bmwg
> >
> >
> > Hi All,
> >
> > We have been researched the POD testing in Containerized
> Infrastructures.
> > We submitted the new draft, "Considerations for Benchmarking Network
> > Performance in Containerized Infrastructures".
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_id_draft-2Ddcn-2Dbmwg-2Dcontainerized-2Dinfra-
> > 2D00.txt&d=DwICAg&c=LFYZ-
> >
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=GqCJ6KxJEotosmsZYGIRkgzSnPHw6
> > 9gsd-qljl5VsKM&s=8TVO-ODX_CHjQHvGlCffATtz0hQeX6HUeog7Q8mGajc&e=
> >
> > Abstract
> >
> >    This draft describes benchmarking considerations for a containerized
> >    infrastructure.  In a containerized infrastructure, Virtualized
> >    Network Functions(VNFs) are deployed on operating-system-level
> >    virtualization platform by abstracting the user namespace as opposed
> >    to virtualization using a hypervisor.  Leveraging this, the system
> >    configurations and networking scenarios for VNF benchmarking will be
> >    partially changed by way of resource allocation and network port
> >    binding between a physical host and VNFs.  In this draft we compare
> >    the state of the art in container networking architecture with
> >    networking on VM-based virtualized systems, and provide several test
> >    scenarios for network performance in containerized infrastructure.
> >
> > We welcome any comments.
> >
> > Regards,
> > Wangbong Lee
> >
> > _______________________________________________
> > bmwg mailing list
> > bmwg@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_bmwg&d=DwICAg&c=LFYZ-
> >
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=GqCJ6KxJEotosmsZYGIRkgzSnPHw6
> > 9gsd-qljl5VsKM&s=Bw0LUXS-NxJHsEwXDVqXkyG-vuE7YWyeQMbEHEWsGfA&e=
> 
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_bmwg&d=DwICAg&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=qXXXuSDIome9R0009wamlXyeacskd
> HvEajvNIkJnZi0&s=5A7xn7LyNn_hq7KAWSW9fFJj4i1SrXVeH8uoZ4DlPZU&e=