Support for Extensions in ML2
In the current ML2 plugin implementation, only the extensions defined in the
Ml2Plugin class itself are available, and there is no way for core resources to
be extended with attributes needed by specific mechanism drivers. When such
extensions are needed, whether for new general purpose features that might be
incorporated in future core API versions, or to better support specific
networking technologies, the only current option is to implement a new
monolithic plugin
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Low
- Drafter:
- Nader Lahouti
- Direction:
- Approved
- Assignee:
- Nader Lahouti
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Akihiro Motoki
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
24-June (mestery): Bumping this to Juno-3 for now, the spec needs more review and updates and I'm not sure this will make Juno-2.
[mestery] Moving this to Juno-2, as the spec is not approved yet and there is some level of disagreement in the approach so far. This will not land in Juno-1.
work in progress
Gerrit topic: https:/
Addressed by: https:/
Support for extensions in ML2 Mechanism Drivers
Addressed by: https:/
Support for extensions in ML2 Mechanism Drivers
[24-June-14] Hi Kyle,
The other blueprint (http://
I added pseudo code for extension driver based on the discussion that I had with rkukura in the etherpad:https:/
Is it possible to keep the milestone target to june-2? As soon as I get the feedback I can work on the implementation.
Thanks,
Nader.
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Passes the context variable in the ML2 Extension Driver API
Gerrit topic: https:/
Addressed by: https:/
Passes the plugin context variable in the ML2 Extension Driver API
