Bug 1091005 - [RFE] Provide a way to attach vNICs to a bridge not managed by RHEV
Summary: [RFE] Provide a way to attach vNICs to a bridge not managed by RHEV
Keywords:
Status: CLOSED DUPLICATE of bug 988285
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Amador Pahim
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-24 15:05 UTC by Amador Pahim
Modified: 2019-04-28 09:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-04 10:34:57 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17895 0 None None None Never

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 ***
Note You need to log in before you can comment on or make changes to this bug.