Contents

Major Features

• NEMO engine provides the mapping from users' intent expressed by NEMO model into the control to physical network.

• NEMO openflow renderer provides the configuration of openflow devices according to users' intent.

• NEMO cli renderer provides the configuration of traditional devices.

• NEMO UI display the intent graph for tenant user, and display physical resources, all tenant' intent, and all mapping result for admin user.

Target Environment

For Execution

• Requires Java 7 compliant runtime environment.

• Follow the user guide documentation to install OpenDaylight controller with NEMO engine.

For Development

• Requires Java 7 compliant runtime environment, Maven version 3.1.1.

• Follow the user guide documentation to install OpenDaylight controller with NEMO engine.

• Use NEMO UI and apidocs to check the intent instance, physical topology and mapping result.

Known Issues and Limitations

• For using openflow-renderer, requiring special switch to construct physical network. The install guide is in https://github.com/zhangmroy?tab=repositories. Other virtual switch, such as, ovs, will be support in the boron version.

• For using cli-renderer, the physical network should be constructed with HuaWei's device: NE40E. More devices will be considered in the boron version.