Jump to: navigation, search

NEMO:Beryllium:System Test

NEMO Engine

Description

NEMO language is a DSL based for the abstraction of network models and conclusion of operation patterns. It provides NBI fashion in the form of language. Instead of tons of abstruse APIs, with limited number of key words and expressions, NEMO language enables network users/applications to describe their demands for network resources, services and logical operations in an intuitive way. And finally the NEMO language description can be explained and executed by a language engine.

Enabling The Feature

To enable the feature set, follow the instructions at this link here:

Using The Feature

The basic interactions for the consumer of the feature is described in our User Guide at this link here:

Incompatibilities

None

Feature Pro-activeness

our feature does not pro-actively interact with other systems like configuring devices, sending flows, sending packet outs, without any special setting or configuration. We do not bind to any ports.

How to test

Purpose Pre-conditions or Pre-requisites Test Steps Expected Results

Connections

  • Fresh installation of the controller
  • Install NEMO UI
  • From the UI console, enter the following:
    • CREATE Connection c1 Endnodes node1, node2;
    • CREATE Connection c2 Endnodes node1, node3;
    • CREATE Connection c3 Endnodes node1, node4;
  • In this example, one geographically distributed company has three sites need to communicate with headquarter, and each sites usually should not be communicate with other sites directly. So with NEMO model, this company should apply for three link resources through connection as bellow. With these expressions, user create three link resources between headquarter and sites, and default, headquarter can communicate with each site, but any site could not communicate with other sites.

Flows

  • Fresh installation of the controller
  • Install NEMO UI
  • From the UI console, enter the following:
    • CREATE Connection c1 Endnodes node1, node2;
    • CREATE Connection c2 Endnodes node1, node3;
    • CREATE Connection c3 Endnodes node1, node4;
    • CREATE Flow f1 Match source-node: n2 destination-node: n3 destination-port: 8443;
    • CREATE Flow f2 Match source-node: n3 destination-node: n2 destination-port: 8443;
    • CREATE Operation o1 Target f1 Action go-through: n1;
    • CREATE Operation o2 Target f2 Action go-through: n1;
  • If in some cases, some flows could be transferred between sites, user should define flows and operations to allow the flow. With these scripts, user allows the voice flow to transfer between site A and site B, and the flow will take use of link resources, c1 and c2. However, if user wants to guarantee the communication quality, he’d better apply for another resources between site A and site B, i.e. create a connection between site A and site B.


Performance/Scalability Concerns

None