Hi Chris,
Thanks very much for taking the time to write such a detailed reply.
That answers my question, and that's what I'd suspected since I didn't see
any reference in the docs.
Best regards,
-Adam
On 3/28/12 8:32 PM, "Brown, Chris (GE Healthcare)"
<Christopher.Brown(a)med.ge.com> wrote:
What you seem to be getting at is a feature like VMware, VirtualBox,
or
the libvirt default constructed virbr0 interface to provide NAT to your
guests. At the moment RHEV/oVirt only supports bridged networking with
the ability to vlan if you so wish. In essence all the typical
functionality of the linux bridgeutils and bonding driver. The
restriction at the moment is that RHEV/oVirt only allows creating a valid
network from a bridge which is attached to physical NIC. I have the usual
suspect tricks by creating virtual NICs, using openvswitch, or VDE, etc
in an attempt to achive both the notion of a private internal network
between guests or a NAT networking for the guests.
Thus this limits the ways you could achive NAT or internal networking for
your guests.
- Bridge to a physical NIC(s) which are attached to a network which
already NAT'd.
- Bridge to physical NIC on a private switch and create mutiple vlan's on
top of that
- Via the vlans you can in essence create multiple networks for your
guests
- Via the vlans you can either NAT to multiple networks or create private
internal networks for your guests
--> attach a VM or linux box with one nic attached to the private switch
vlan this NIC appropriately and go to town with NAT attached to an
external network on the other NIC
- Hand configure macvtap (VEPA) or create vdsm hook for it and bridge to
a private switch which supports hair-pinning (guest to guest
communication)
Suffice to say this is definately an area that both RHEV/oVirt could
improve.
- Chris
________________________________
From: users-bounces(a)ovirt.org on behalf of Adam vonNieda
Sent: Wed 3/28/2012 7:38 PM
To: users(a)ovirt.org
Subject: Re: [Users] New to oVirt, I've got a couple of questions.
Thanks for the Reply, Andrew. OK, so local storage obviously isn't the
best architecture, but that's what I've got, so I'll figure something out.
How about the networking question? How are people getting to their VM's
from the physical network? Here's the original question..
Networking: When I set up a logical network, how is that accessed
from the physical network? For example, if my physical network is
192.168.1.0, and my logical network is 155.223.44.0, how will I
connect to port 80 on a virtual machine with the IP 155.223.44.5
from IP 192.168.1.10. Is there port forwarding? I didn't see mention
of it in the guide.
Thanks folks,
-Adam
On 3/28/12 6:41 PM, "Andrew Cathrow" <acathrow(a)redhat.com> wrote:
>
>
>----- Original Message -----
>> From: "Adam vonNieda" <adam(a)vonnieda.org>
>> To: users(a)ovirt.org
>> Sent: Wednesday, March 28, 2012 5:29:01 PM
>> Subject: [Users] New to oVirt, I've got a couple of questions.
>>
>>
>>
>>
>> Hi Folks,
>>
>>
>> I've got oVirt 3.0 installed on a Fedora 16 machine, and I'm planning
>> my data center. Great process, by the way, very straight forward.
>> I'll have two host machines (on order) which I'll likely load with
>> the oVirt image. These two hosts each will have a large amount of
>> RAID 5 local storage. Here's my questions..
>>
>>
>> Storage: If I'm using this local storage on each host, will I be able
>> to migrate VM's from host A to host B if needed, or does storage
>> need to be shared. I guess another way of asking the question is,
>> what's the best way for me to set this up? :)
>
>You'll need shared storage - NFS, iSCSI or Fiber channel. In the future
>they'll be other options such as native Gluster, but for now you'll need
>something like NFS.
>>
>>
>> Networking: When I set up a logical network, how is that accessed
>> from the physical network? For example, if my physical network is
>> 192.168.1.0, and my logical network is 155.223.44.0, how will I
>> connect to port 80 on a virtual machine with the IP 155.223.44.5
>> from IP 192.168.1.10. Is there port forwarding? I didn't see mention
>> of it in the guide.
>>
>>
>> Thanks very much!
>>
>>
>> -Adam vonNieda
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users