Versions Compared

Old Version 6

changes.mady.by.user Jeremy Songster

Saved on

compared with

New Version 7

changes.mady.by.user Ming Yan Shu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update point intent document

...

Test SuiteTest CasesPassing CriteriaRoad Map
Intent Functionality (FUNCintent)Host intent
  • Intents can be installed between network nodes
  • Connectivity between hosts when intents are installed
  • Intent state is in INSTALLED state for each active instances
  • All devices that are being used are in ACTIVE state
  • Each active device is assigned to one master controller
  • Network topology from Mininet is equivalent to ONOS view for each active instances
  • Flows should be in its appropriate state before and after an event such as intent installation, rerouting flows etc.
  • System state is consistent to all active ONOS instance
  • Connectivity is preserved in rerouting flows when particular links are down
  • Every match action given when adding intents should correctly stored in each of intents status
  • Network nodes ( switch and host ) information are consistent such as MAC, IPs, IDs, Ports.
  • All steps and verification should pass with different types of host: Dual stack, IPV4, VLAN etc.
  • Completely remove or purge all intents that have been installed
  • Point-to-Point intent supports protection intent
Now
 Point intentNow
 Multi-to-single point intentNow
 Single-to-multi point intentNow
 Host Mobility
  • Hosts connections can be moved between switches
Now
 

Single-to-multi point intent

multi-to-single point intent

partial failure

  • As with single-to-multi and multi-to-single intent tests but including
  • Connectivity is preserved when a part of the intent is isolated from the network is partial failure flags are set
Now

...