Re: [Supa] PPT for agenda 5a (Gap analysis from SUPA's view)

John Strassner <strazpdj@gmail.com> Thu, 19 March 2015 16:29 UTC

Return-Path: <strazpdj@gmail.com>
X-Original-To: supa@ietfa.amsl.com
Delivered-To: supa@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEEF01A1ADF for <supa@ietfa.amsl.com>; Thu, 19 Mar 2015 09:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 GC01HTUVGYix for <supa@ietfa.amsl.com>; Thu, 19 Mar 2015 09:29:36 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47BA41A1B51 for <supa@ietf.org>; Thu, 19 Mar 2015 09:29:30 -0700 (PDT)
Received: by wgbcc7 with SMTP id cc7so67103808wgb.0 for <supa@ietf.org>; Thu, 19 Mar 2015 09:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7El0P1o5OWZmvdKqIPuBVdRAxcChT0WIC7UpuQY8zyo=; b=akd1Pr2mD/DHCSpjqG525mnI05vm5MIWfQrRRpYR/T6TAL+LxaLOEyRnXp5wmo4FmR KQCeUb/CV82UKR08e0+YXjVHXrvBnL8uWQUL3hZ0K8m5qcni8OGDq4lRzkdMgr2n2Gzb jS5UVB2TO8URerIEEyt+Flc2ZqqB0Xd7b3HiyMmzWHv33zRUNxbYAx0Ew280fxVnrusb +ELKqHQb1xQ6ZIPxY6T9EKKyYD1Rff+JD/978CwjQ9Ltrq8Tm1CgeEGa7Ofv5W6dFQtj oJ9drKmWEv3KqJs+iBKm4vwEI9VDnoPjlrvYYlnTVcxAlY7X3ixbQSRX5JlNSMYKIYYS e7kA==
MIME-Version: 1.0
X-Received: by 10.180.13.146 with SMTP id h18mr17466857wic.73.1426782569056; Thu, 19 Mar 2015 09:29:29 -0700 (PDT)
Received: by 10.27.85.139 with HTTP; Thu, 19 Mar 2015 09:29:29 -0700 (PDT)
In-Reply-To: <CY1PR09MB0922F7A51874E82162C761F5A8010@CY1PR09MB0922.namprd09.prod.outlook.com>
References: <000401d0623b$33514120$99f3c360$@tsinghua.edu.cn> <CY1PR09MB0922F7A51874E82162C761F5A8010@CY1PR09MB0922.namprd09.prod.outlook.com>
Date: Thu, 19 Mar 2015 09:29:29 -0700
Message-ID: <CAJwYUrG8s3m2eC4WYgL=mMDj8aXxqzf7zY8jqfYZQVzp2uJLyw@mail.gmail.com>
From: John Strassner <strazpdj@gmail.com>
To: "Natale, Bob" <RNATALE@mitre.org>, John Strassner <strazpdj@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c2270c334eaf0511a6b480"
Archived-At: <http://mailarchive.ietf.org/arch/msg/supa/dM9RKV4EWYIUEaInEfetjSefNoo>
Cc: Jun Bi <junbi@tsinghua.edu.cn>, "SUPA@ietf.org" <supa@ietf.org>
Subject: Re: [Supa] PPT for agenda 5a (Gap analysis from SUPA's view)
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This list is to discuss SUPA \(Shared Unified Policy Automation\) related issues." <supa.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/supa>, <mailto:supa-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/supa/>
List-Post: <mailto:supa@ietf.org>
List-Help: <mailto:supa-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/supa>, <mailto:supa-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 16:29:38 -0000

I agree with Bob.

I think that ONOS is applicable **as long as we take intent-based policy
models seriously**. Right now, I have seem some work on ECA policy rules,
but no work of any substance of undertaken in SUPA. (Well, to be honest, I
could argue that the intent-based work is not that substantive in other
areas as well...).

This begs the question, will we in SUPA do **both** ECA policy rules and
**intent-based (i.e., declarative)** policy rules? I said that we would in
the PBSM presentation, but **I would suggest that we add something to the
charter**, as the content and structure of ECA policy rules is very
different than that from intent-based policy rules.

That being said, I have the following comments on slide 6:
ODL has TWO approaches: GBP and NIC. GBP is really a relational model of
how two EPGs communicate and interact, while NIC is a different, more
generic, effort.

Comments on slide 7
In principle, OpenStack NIC is similar to ODL NIC. GBP was first defined in
ODL, so I would cover GBP in the ODL section in slide 6, and then simply
reference it here on slide 7.

OpenStack Congress on slide 7 needs some serious rework:

   - Congress is meant to drive all other OpenStack projects; it doesn't so
much "work in conjunction with keystone" as express facts and policies that
Keystone (or other modules) can use.

    - Congress is **based** on Datalog, but extends it in a number of ways
(I am one of the committers to the Congress grammar)

    - Datalog is entirely declarative, but is **not** pure first-order
logic (it is a subset of)

    - Congress does not yet "enforce" anything. Rather, it states what
should or should not be done or occur, and then some other entity fixes that

    - Congress is neither a "problem finder" or an "intelligent solver"
(especially the latter). Congress is basically a query language. We have
proposed Rule-X as an intelligent multi-constraint optimization solver that
will work with Congress. With respect to "problem finder", I assume you
mean "answer set programming" - AFAIK, nothing is yet prepared for this.

Please make these changes asap.

Finally, the gap analysis should also cover the TMF. I'll build a slide for
you on this later today.


regards,
John






On Thu, Mar 19, 2015 at 5:05 AM, Natale, Bob <RNATALE@mitre.org> wrote:

>  Hi Jun,
>
>
>
> Thanks … helpful deck for those of us trying to keep up with everything on
> a part-time basis!
>
>
>
> However, I believe that discussion of “Other working groups” starting on
> slide #5 should also cover the (open source) Open Network Operating System
> (ONOS) project’s Intent Framework, which would seem to provide a somewhat
> higher-order context for possible PBSM implementation based on
> Intents/Goals driving E-C-A rules. See http://onosproject.org/, and
> especially
> http://onos.wpengine.com/wp-content/uploads/2014/11/ONOS-Intent-Framework.pdf
> .
>
>
>
> Or perhaps there some specific reasons why ONOS Intent Framework does not
> apply to the SUPA work…?
>
>
>
> Avanti,
>
> BobN
>
>
>
> *From:* Supa [mailto:supa-bounces@ietf.org] *On Behalf Of *Jun Bi
> *Sent:* Thursday, March 19, 2015 7:53 AM
> *To:* 'SUPA@ietf.org'
> *Subject:* [Supa] PPT for agenda 5a (Gap analysis from SUPA's view)
>
>
>
> Hi All,
>
>
>
> The attached file is the PPT for agenda 5a (Gap analysis from SUPA's view).
>
>
>
> The draft was submitted by the deadline weeks ago,
>
> but the PPT is enhanced to reflect the recent discussions.
>
>
>
> Best Regards,
>
> Jun Bi
>
>
>
>
>
> *SUPA BOF Agenda*
>
> Monday 3/23/2015
>
> Afternoon Session I - 13:00 to 15:00
>
>
>
> 1. Note Well, logistics, agenda bashing (chairs, 5 min)
>
> 2. Introduction and scoping of BoF (AD and chairs, 5 min)
>
> 3. Policy Driven Service Management - John, Fukushima (15 min)
>
> 4. Distributed Data Center Use Case - TBA (15 min)
>
> 5. Gap Analysis
>
>   5a. SUPA view – Jun Bi (10 min)
>
>   5b. Related Work in the Routing Area - Susan (10 min)
>
>   5c. Related OpenSource Projects: OpenStack Congress, GBP, ODL GBP/NIC -
> Tom (10 min)
>
> 6. Scope Discussion - 30 min
>
> 7. Questions to the audience (chairs, 15 minutes)
>
>
>
>
>
>
>
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa
>
>


-- 
regards,
John