Skip to content

Latest commit

 

History

History
38 lines (37 loc) · 1.81 KB

blueprint.md

File metadata and controls

38 lines (37 loc) · 1.81 KB

MEF-Eline

Operational requirements

  1. Switches must support multiple DPIDs through configurations
    1. This feature would enable easy replacement of damaged/RMA devices
  2. Support to disable Packet Outs out of some ports (Topology Discovery's LLDP for known host and inter-domain ports)
  3. Maintenance modes for links with scheduling
    1. Move circuits out of the link under maintenance
    2. Make the under maintenance link unavailable to users
    3. Disable notifications
    4. Disable topology discovery
    5. Disable link health checks
  4. Maintenance modes for nodes with scheduling
    1. Same as previous item
  5. Activate/Deactivate circuits (via checkbox?)
    1. Keep on database but remove from flow tables
  6. Self adjustment for circuits when a new Switch is introduced between two other switches
  7. Native support for path trace (SDN-LG)
    1. without going through an extra UI
  8. Support for moving multiple circuit from primary to backup paths
    1. Through a single operation
  9. Support for forcing circuit reprovisioning
    1. Through a single operation
  10. Inter-switch link health testing
    1. Parallel to LLDP, shorter interval
    2. If link is not "healthy", set it as "impaired" and move circuits out of it.
    3. Similar to a BFD test
  11. Support for pre-defined "core" VLANs for links (interoperability with external domains)
    1. NNI pre-defined VLAN range
  12. Adaptive statistics queries interval
    1. STAT_REQ / 30s
    2. Min (user-defined) 30 to Max (user-defined) 600
    3. Default: 5min (User-defined)
    4. Saves CPU
  13. Napp should react to network status changes to guarantee maximum resilience
    1. Backup path(s) could be pre-installed if possible protecting from node failures
      1. If feasible
    2. User chooses if circuit should go back to the primary path and waiting stable interval