Modular and Adaptive Plugin
This blueprint describes a new neutron pluging named MAP (Modular and Adaptive Plugin). This plugin differs from current approach by providing neutron with an abstract network representation using modeling languages (MetaCLI, Yang...). Knowledge on the underlying network allow this plugging to choose a strategy and a set of services to apply. This choice is then realized by drivers managing a specific configuration protocol (netconf, CLI, Openflow..), allowing managing various multi-vendor networks.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Mark McClain
Related branches
Related bugs
Sprints
Whiteboard
Has the relationship between this and the Modular L2 (ml2) plugin introduced in hanvan been explored? They seem to share some similar goals.
-> They have some common points indeed. But MAP uses its representation of the network to choose any services (within and between datacenters) automatically (thanks to a few rules).
