Contents
Project Name
Features
- odl nemo rest provides an abstracted intent model whose target is to enable network users/applications to describe their intent in an intuitive way without caring about the underlying physical network.
- nemo engine is the core module of NEMO project, which releases the mapping from intent to physical network. It includes two import process: intent-virtual network(VN) and virtual network-physical network(PN).
- openflow renderer is a sourthbound render to translate the mapping result of VN-PN to flow table in devices supporting for openflow protocol.
- cli render is also a sourthbound render to translate the mapping result of VN-PNinto forwarding table in devices supporting for traditional protocol.
- nemo engine ui is reponsible for showing the status of physical network, intent, generated virtual network and mapping result of VN-PN, which facilitate users to understand better the intent handling process if they want to.
Non-Code Aspects (user docs, examples, tutorials, articles)
Architectural Issues
- There are no architectural issues.
Security Considerations
- There are no security issues found.
Quality Assurance (test coverage, etc)
Test Coverage
- Unit Test: 42.8% (Sonar data does not update frequently, the coverage may be higher)
- Manual Test: External System Test is done manually, since the sandbox environment could not satisfy NEMO's requirement.(Will migrate in boron)
CSIT
End-of-life (API/Features EOLed in Release)
Bugzilla (summary of bug situation)
Standards (summary of standard compliance)
Schedule (initial schedule and changes over the release cycle)