Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • We can use NEMO language to capture this intent.
  • We import the enterprise site information
  • Import the internet access information
  • And we create the DMZ and the interior
  • Then we generate connections among all the nodes
  • Finally, we apply operations on the connections

 

 

Release Plan

Road Map(H release):

Date

Goal

Jun.   15, 2016

Finish   release planning

Jun.   30, 2016

Finish   requirement analysis and architecture and model design

Jul.   15, 2016

Finish   the development of NEMO model and API

Jul.   22, 2016

Finish   NEMO language compiler development

Aug.   1, 2016

Finish   NEMO storage module

Aug.   12, 2016

Finish   NEMO UI development

Aug.   15, 2016

Feature   integration freeze

Aug.   26, 2016

Finish   test and bug fix

Aug.   31, 2016

Hummingbird   release

 

Road Map(I release):

Date

Goal

Sep.   9, 2016

Finish   release planning

Sep.   16, 2016

Finish   requirement analysis and architecture design

Sep.   23, 2016

Finish   the development of tenant space management module

Oct.   17, 2016

Finish   NEMO intent resolver development

Oct.   28, 2016

Finish   VTN and SFC drivers

Nov.   12, 2016

Finish   integration test with VTN and SFC applications

Nov.   15, 2016

Feature   integration freeze

Nov.   25, 2016

Finish   test and bug fix

Nov.   30, 2016

I   release

 

H Release:

Implement five functions of NEMO engine: NEMO model and API, NEMO language compiler, NEMO storage and NEMO UI.

 

I Release:

Implement the rest of the functions of NEMO engine, including tenant space management, NEMO intent resolver and VTN and SFC drivers.

Implement the complete demonstration of VTN + SFC scenario.