Re: [Ibnemo] Feedback on Nemo Status

["Susan Hares" <[e-mail]>]

Tianran:

This is excellent update to my write-up.   I will start my work with the use
cases this week. 

Sue 

From: Ibnemo [mailto:[e-mail]] On Behalf Of Zhoutianran
Sent: Tuesday, May 26, 2015 3:07 AM
To: Susan Hares; [e-mail]; [e-mail]
Subject: Re: [Ibnemo] Feedback on Nemo Status

 

Hi Sue,

Thanks for your write up.

The following figure shows my consideration on how to coordinate intent
related work. 

In IETF, I think we can work on:

l  Use case for intent networking

l  Intent definition

l  Gap analysis to other working groups in IETF

l  Intent network models

l  Intent description language facilitating intent expression

And we can discuss all these topics in this mailing list.

Then we can implement the intent engine and the protocol related to the
controller NBI in open source projects, e.g. OpenDaylight.



 

Best Regards,

Terence

From: Susan Hares [mailto:[e-mail]] 
Sent: Saturday, May 23, 2015 4:25 AM
To: [e-mail]
Cc: Zhoutianran; Xiayinben
Subject: Feedback on Nemo Status 

 

I was asked to provide an overview for the Cablelabs write-up for their MSO.
Does this write-up capture the Nemo work? 

 

Sue Hares 

 

--------------

NeMo provides a simple transaction based Intent-based NBI, enabling
applications to creat, modify and takedown virtual networks built on virtual
nodes with policy-controlled flows. The NeMo Intent NBI allows an
application to communicate with a controller, providing 10 commands: 

 

·         4 network commands: Node, Link, Flow, Policy

·         6 controller communication commands: connect, disconnect,
transact, commit, notification, query

An application exchanges NeMo commands using the REST Protocol to a
controller running a Nemo language processing engine to instruct the
controller to set up a virtual network of nodes and links with flow policy
to control the data flows across the network links.  

NeMo uses an application’s view of the compute, storage, and network to
allow an application to set any grouping of compute, storage, or network as
a virtual ‘node’. This allows the application to decide what constitutes a
compute node and what constitute a ‘link’ and a ‘flow’.  From the
application’s viewpoint, it intends to connect two or more nodes in a
network.  It does not matter to the application if the node is a single
virtual machine (VM) or a cluster of interconnected compute and storage
devices with many network connections. NeMo’s NBI API hides this complexity,
making the application’s commands prescriptive and simple.   Nemo’s  

Nemo’s language engine in the controller is associated with a model that
allows a group of applications to have a set of pre-loaded defintions (model
sematics) for nodes, flows, or policy.  For example, a company nodes could
be defined along with the necessary flows for accounting traffic or big-data
transfers.   

 

NEMO Engine

 

Technically, Nemo is a declarative, domain specific policy language.  

 


Status and Relevance


 

Nemo has open source projects in:

·         Open Daylight
(https://wiki.opendaylight.org/view/Project_Proposals:NEMO) 

Goals of ODL project: 

o   Design and develop consistent NBI models and patterns for intent
networks.

o   Design the syntax for a language style NBI.

o   Design and develop a NEMO language engine for language parsing and model
mapping to SB models. It is possible to reuse the ongoing NIC project in
OpenDaylight for the intent manager and model mapping component

·         OPNFV (Movie)   

Goals: 

o   Provide a more abstract NBI alternative by extending the general cloud
platform to simplify the orchestrator and VNF manager

o   Compose various scenarios with a same set of abstractions

o   Use the MDA approach for NBI consistency and interface automation

 

·         IB-Nemo Pre-BOF in the IETF (www.nemo-project.net) 

o   Mail list: [e-mail]

Goals: 

o   Focus on a clear definition of Intent that can be operationalized in
networks, 

§  https://datatracker.ietf.org/doc/draft-xia-ibnemo-icim/

o   Define use cases scenarios for Nemo, 

o   Provide a gap analysis for other work in the IETF, and  

o   Standardize a protocol language for Nemo   

§  https://datatracker.ietf.org/doc/draft-xia-sdnrg-nemo-language/

§  https://datatracker.ietf.org/doc/draft-xia-sdnrg-nemo-language/

o   Standardize data models to provide 

§  https://datatracker.ietf.org/doc/draft-zhou-netmod-intent-nemo/