Red Hat Bugzilla – Bug 802831
Request For Enhancement (RFE): Add the possibility to define Virtual Switches in RHEV
Last modified: 2016-01-28 16:54:42 EST
Description of problem:
We are evaluating RHEV3.0 to see if it is a good candidate for setting up a Cloud Infrastructure for our Test Environment. The test objects we have, are products which normally are installed on scale-able clusters of physical nodes. To save money on hardware for testing purpose, we transformed those nodes into virtual machines running as a cluster on one single host.
VMware ESXi is currently used as hypervisor, which provides "Virtual Switches" for setting up the networking within that virtual cluster. In VMware they know as well in vCenter the concept of "Virtual Distributed Switches", where virtual switches can be defined among several ESXi hosts, for internal network connectivity between virtual machines running on different hosts (for this an extra physical NIC is needed on every involved host). I guess that the logical networks which can be defined in RHEV offer something similar...
We want to migrate towards the flexibility offered by a cloud infrastructure. The evaluation of RHEV + RHEVM 3.0 gives a very good first impression. However the prerequisite for us is to have the possibility to define internal networking between the virtual machines within the host. So we simply need Virtual Switches, and we cannot start using RHEV (yet) without them...
Version-Release number of selected component (if applicable):
RedHat Enterprise Virtualization 3.0 (Hypervisor + RHEVM)
Non applicable as this is a RFE.
Steps to Reproduce:
ovirt engine doesn't support "private networks" right now.
have you looked at custom hooks as a temporary solution?
custom hooks let you change the guest, including mapping networks to it.
(for example, there is an isolated private vlan sample of a cusotm hook:
this sample is for no traffic to other guests, but if this is relevant can be looked at.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.