External attachment points
It would be useful to have a way for a tenant to control the network access of his/her baremetal servers via the standard assignment of a neutron port to a network, etc.
This will allow a tenant to associate a physical attachment point with a Neutron network.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Undefined
- Drafter:
- Kevin Benton
- Direction:
- Needs approval
- Assignee:
- Kevin Benton
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Needs Code Review
- Milestone target:
- None
- Started by
- Kyle Mestery
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
3-Sep (markmcclain): Moving out of Juno as the code missed the freeze.
15-July (mestery): Moving to Juno-3, as the second two patches in this series (according to the commit message) haven't been posted for review yet.
6-Jun (mestery): Moving this to Juno-2.
Leaving this in Juno-1 for now, but we need the spec to land this week to have a chance at this realistically landing in Juno-1.
Gerrit topic: https:/
Addressed by: https:/
External Attachment Point Extension Mixin
Gerrit topic: https:/
Addressed by: https:/
Add spec for neutron-
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Implement external attachment mixin in ML2 plugin