Re: [Ibnemo] How to group/reuse definitions

Zhoutianran <zhoutianran@huawei.com> Mon, 09 November 2015 07:46 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: ibnemo@ietfa.amsl.com
Delivered-To: ibnemo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D36EC1B6EF8 for <ibnemo@ietfa.amsl.com>; Sun, 8 Nov 2015 23:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.611
X-Spam-Level:
X-Spam-Status: No, score=-3.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_65=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9b8L6-avvEj5 for <ibnemo@ietfa.amsl.com>; Sun, 8 Nov 2015 23:46:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB821B6EF2 for <ibnemo@ietf.org>; Sun, 8 Nov 2015 23:46:22 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CAB96069; Mon, 09 Nov 2015 07:46:19 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 9 Nov 2015 07:46:18 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.203]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0235.001; Mon, 9 Nov 2015 15:46:11 +0800
From: Zhoutianran <zhoutianran@huawei.com>
To: "Bert Wijnen (IETF)" <bwietf@bwijnen.net>, "ibnemo@ietf.org" <ibnemo@ietf.org>
Thread-Topic: [Ibnemo] How to group/reuse definitions
Thread-Index: AQHRF64yuRuATcKFWUqUwGcFIS41SZ6TT/jA
Date: Mon, 09 Nov 2015 07:46:11 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F2183167D60@nkgeml512-mbx.china.huawei.com>
References: <563B2449.6040802@bwijnen.net>
In-Reply-To: <563B2449.6040802@bwijnen.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.56404F4C.001A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.203, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d7d058bc838e1da5f40d6ac9fa414caf
Archived-At: <http://mailarchive.ietf.org/arch/msg/ibnemo/HUuVdlSpHcJETHd4H6n5I_P4yVI>
Subject: Re: [Ibnemo] How to group/reuse definitions
X-BeenThere: ibnemo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of Nemo, an intent-based North Bound \(NB\) interface consisting of an application protocol running over HTTP \(RESTful interfaces\) to exchange intent-based primitives between applications and meta-controllers controlling virtual network resources \(networks, storage, CPU\)." <ibnemo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ibnemo/>
List-Help: <mailto:ibnemo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ibnemo>, <mailto:ibnemo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2015 07:46:26 -0000

It's really useful to group a set of atomic components and provide the whole as a micro/template, just like the DMZ example. The hierarchy enables the reusability.
To describe a DMZ, I can see two ways.
1. One is to describe the exact connectivity among those atomic components. I think the switch and router are what we want to eliminate. It seems too detail with the intent concept. I hope they can be auto generated by the intent engine.
2. The other way I would prefer is to define DMZ as a layer 2 group, in which by default all the components are connected by a logic switch(which do not need to explicitly describe again). Or we can define DMZ as a layer 3 group with a  router. In this way, we can put any number of components in easily with fully flexibility.

That's my 2 cents.

Best,
Tianran

> -----Original Message-----
> From: Ibnemo [mailto:ibnemo-bounces@ietf.org] On Behalf Of Bert Wijnen
> (IETF)
> Sent: Thursday, November 05, 2015 5:41 PM
> To: ibnemo@ietf.org
> Subject: [Ibnemo] How to group/reuse definitions
> 
> During the IETF94 Hackaton, we got some discussion on how much detail we
> want to allow or need in the Intent Language when reusing definitions. For
> example, let us assume that you
> 
> - define a router
> - define a firewall
> - define a loadbalancer
> - define a l2 switch
> - etc
> 
> And that later on you want to define something like a DMZ and inside that
> DMZ you want to use the defined router, firewall, l2 switch, etc.
> 
> The end-user/customer would want to just express his/her intent to have
> an internet connection with a DMZ I guess.
> 
> The network administrator of the ISP (operator) needs to then express that
> the DMZ consists of let us say a router, a firewall, a l2switch etc.
> Do we want/need the network administrator to have to (or to be able to)
> specify the details on how these nodes get connected? Or would we rather
> see that the Intent Engine generates the proper connections?
> 
> I suggest that those who have proto-type implementations express their
> approach and that network operators express their wants/needs for such a
> scenario.
> 
> Bert
> 
> _______________________________________________
> Ibnemo mailing list
> Ibnemo@ietf.org
> https://www.ietf.org/mailman/listinfo/ibnemo