External attachment points

Registered by Kevin Benton on 2014-03-27

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 on 2014-05-29
Completed by
Armando Migliaccio on 2015-12-16

Related branches

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://review.openstack.org/#q,topic:bp/neutron-external-ports,n,z

Addressed by: https://review.openstack.org/97173
    External Attachment Point Extension Mixin

Gerrit topic: https://review.openstack.org/#q,topic:bp/neutron-external-attachment-points,n,z

Addressed by: https://review.openstack.org/87825
    Add spec for neutron-external-attachment-points

Gerrit topic: https://review.openstack.org/#q,topic:neutron-external-attachment-points,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/bsn-external-attachment,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/bsn-ml2-ext-attach,n,z

Addressed by: https://review.openstack.org/116187
    Implement external attachment mixin in ML2 plugin

(?)

Work Items