Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1103986

Summary:	[RFE][neutron]: External attachment points
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	lpeer <lpeer>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	chrisw, markmc, nyechiel, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/neutron-external-attachment-points
Whiteboard:	upstream_milestone_none upstream_definition_obsolete upstream_status_needs-code-review
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 11:38:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-06-03 04:05:14 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-external-attachment-points.

Description:

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. 

Specification URL (additional information):

https://review.openstack.org/#/c/87825/

Comment 1 lpeer 2015-03-19 11:38:41 UTC

This RFE was automatically opened to track status of upstream development.
At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.