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

Bug 1091005

Summary:	[RFE] Provide a way to attach vNICs to a bridge not managed by RHEV
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Amador Pahim <asegundo>
Component:	vdsm	Assignee:	Amador Pahim <asegundo>
Status:	CLOSED DUPLICATE	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	bazulay, iheim, lpeer, myakove, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	3.5.0
Hardware:	All
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-04 10:34:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amador Pahim 2014-04-24 15:05:16 UTC

Use Cases:

* Private Network for vms 

Ability to configure 'Private Networks' for VMS within a hypervisor. Create a private network in a such way it will be not connected to any physical interface and visible to vms running on the hypervisor only.

* Why is private network needed?

Hosts that need to talk to very locked down database machines.  We do not want those machines talking to anything else.

* Attach a vNIC to a bridge not managed by RHEV

Ability to attach a vNIC to a bridge not managed by RHEV or a bridge to be present in only one or some specific Hypervisors.

* Why is a bridge on selected hosts needed?

Hosts that have a custom network configuration to access a DMZ network, not acessible by all Hosts in the Cluster.

Comment 2 lpeer 2014-05-04 10:34:57 UTC

We refer to this feature as  'Isolated Logical Networks', we have an RFE open for this request.

*** This bug has been marked as a duplicate of bug 988285 ***