[OPS-AREA] YANG Device Profile for Data Center switches - in RTGWG and OPS-AREA

"Black, David" <David.Black@dell.com> Mon, 27 March 2017 17:05 UTC

Return-Path: <David.Black@dell.com>
X-Original-To: ops-area@ietfa.amsl.com
Delivered-To: ops-area@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 175E512945D; Mon, 27 Mar 2017 10:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.496
X-Spam-Status: No, score=-5.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=eJz6zgvt; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=CADTreoQ
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id D_NUr2GHbY4T; Mon, 27 Mar 2017 10:05:12 -0700 (PDT)
Received: from esa5.dell-outbound.iphmx.com (esa5.dell-outbound.iphmx.com []) (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 95CBC129479; Mon, 27 Mar 2017 10:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1490633737; x=1522169737; h=from:cc:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=Lz7VclSW8bYkHlFxUm0rrSUR/2V1edpIDAAQwjeCRf4=; b=eJz6zgvtJFQghrhxRcuqPKADgvdf7AqMsMFXL0mnnRRO9vrsA67N/rST Jh9L3OrT7BUIgktzPGL9F8vkPBMOaPLbWi2Lo/ZCUhbeDAKdhKMPVoHXy PuQuMdYNdBCxt02OTghpoAJNVqODT2LNOuBIcPFGvDOFKznyzDto6Ty1V c=;
Received: from esa5.dell-outbound2.iphmx.com ([]) by esa5.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2017 11:55:36 -0500
From: "Black, David" <David.Black@dell.com>
Cc: "Black, David" <David.Black@dell.com>, "White, Joseph L" <Joseph.L.White@dell.com>, "John Leung (john.leung@intel.com)" <john.leung@intel.com>
Received: from mailuogwhop.emc.com ([]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2017 23:05:06 +0600
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com []) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v2RH54lM028001 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Mar 2017 13:05:05 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com v2RH54lM028001
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1490634306; bh=0IcNB3jAYwS8VpiAdJ9oZSmt7LE=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=CADTreoQ2yCw8+t7GH1XcH7g+4Dhswnhvlo8ywQZtSwRQSxTZiQUTEPV7V+xzG6Zk 6gd6UVa8ia8tI/EpNVcrJRUEZ2nFTdLY7Jf7++4Fu+m63zw14GHLOGdRG7020FEJEW Sf2FuHTbow3fngEvaVjy1AeuRtTsK7Y0UouPIa+c=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com v2RH54lM028001
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com []) by maildlpprd03.lss.emc.com (RSA Interceptor); Mon, 27 Mar 2017 13:04:34 -0400
Received: from MXHUB310.corp.emc.com (MXHUB310.corp.emc.com []) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v2RH4kLf001288 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Mon, 27 Mar 2017 13:04:46 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB310.corp.emc.com ([]) with mapi id 14.03.0266.001; Mon, 27 Mar 2017 13:04:45 -0400
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "ops-area@ietf.org" <ops-area@ietf.org>
Thread-Topic: YANG Device Profile for Data Center switches - in RTGWG and OPS-AREA
Thread-Index: AdKnHEHhHrAiDD35RQisC3nm4Ia8CQ==
Date: Mon, 27 Mar 2017 17:04:45 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F97A9C0@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public, GIS Solicitation
Archived-At: <https://mailarchive.ietf.org/arch/msg/ops-area/AWmHPn5fu_eccp-oYhrvrTGZ180>
Subject: [OPS-AREA] YANG Device Profile for Data Center switches - in RTGWG and OPS-AREA
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ops-area/>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 17:05:16 -0000

Gentle rtgwg and ops-area participants,

I wanted to call attention to a couple of drafts about early activity on a YANG profile for data center switches that will be discussed in RTGWG (first session, Wed , 9a start) and OPS-AREA (Thursday, 1p start):


For those who don't want to wade through the drafts, the RTGWG chairs have already posted the slides:


[watch out for URL split across lines ...]

The short summary is that for data center converged infrastructure [CI], networking should be managed as part of the overall infrastructure - e.g., single "pane of glass" for an 84U rack of which 4U may be networking equipment.   Another standards body (DMTF - Distributed Management Task Force) is working on a standard for CI management, Redfish, and is reusing YANG models for network management via a translation approach (hallelujah - not-invented-here doesn't win every time!) - among the benefits of reuse this should be common views of underling state via YANG-based CI management and network management tools. 

This reuse is working "running code" today, as described in the slides and the ci-profile-background draft.  The next step is to define the minimum implementation requirements for what data center switches to be managed as part of CI - i.e., when a YANG-based management tool looks at such a switch, what does it expect to see as the minimum set of supported YANG modules, i.e., a device profile.  This avoids "defensive programming" in management tools to deal with different switch implementations supporting different YANG modules - that inevitably leads to switch-specific code in management tools.  The baseline-switch-model draft is a rather drafty first start on the minimum set of supported YANG modules for data center switches (NB: the set will differ for other classes of equipment/devices) - we're looking to do this work in the IETF so that the resulting device profile is broadly useful well beyond Redfish, and we (draft co-authors) are looking for all the help, advice, etc. that people care to offer.   In particular, we're not attached to the format of that draft - it was our first attempt to capture material.

The longer, more detailed discussion of this activity will be in RTGWG - the shorter OPS-AREA session is intended to be more of an overview of the activity and why it's useful in the hope of engendering interest.  We'll be happy to take questions on the lists, in the meetings or directly.

Thanks, --David (on behalf of Joe White, David Black and John Leung, the wbl draft co-authors)
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com  <=== NEW ===