[ovirt-users] Communicate between the guest vm's hosted on, different hosts on different data centres using OVS
Linov Suresh
linov.suresh at gmail.com
Sun Apr 23 14:12:10 UTC 2017
I have created a separate network for 10G network and made central server
part of it. After that configured the OVN controller using vdsm-tool
vdsm-tool ovn-config <OVN central server IP> <local IP used for OVN
tunneling>
Then added OVN provider to oVirt as an external network provider and
created a new network based on OVS. Now the new VM's we create use this new
network.
Thanks for your help!
On Fri, Apr 21, 2017 at 5:39 AM, Charles Tassell <ctassell at gmail.com> wrote:
> Hmm, so you have 2 10G ports on each host. 1 port is currently in use
> with oVirt, and the other isn't? Then I think you just add a new network
> in the Networks tab called OVNLink, then go into the Hosts tab, click on
> each host and then on the Network Interfaces tab in the bottom of the
> window and assign the unused 10G network device to that link.
>
> I haven't used OVN with oVirt, but that would work with regular networking
> so I think it should work with OVN.
>
> If the link is already in use, you should be able to do the same thing
> only when you add the new network set it up with a VLAN ID. If you are
> going through a switch then the switch will have to be setup to handle the
> VLANs.
>
>
>
> On 2017-04-20 10:07 PM, Linov Suresh wrote:
>
> Hi Charles,
>
> We use an Ethernet cable to connect between the hosts through 10G port.
>
> We want to use the guest VM's hosted on different hosts 10G network. oVirt
> already supports SR-IOV. So we should guest 10G speed for our VM's.
>
> In KVM we can create a second bridge and add the 10G interface to the
> bridge would do the trick.
>
> But in oVirt how do we do this? We want to use our OVs network, which was
> created using OVN Provider.
>
>
> Linov Suresh
>
>
>
> On Thu, Apr 20, 2017 at 6:59 PM, Charles Tassell <ctassell at gmail.com>
> wrote:
>
>> Hi Suresh,
>>
>> You would need to connect the two OVN instances somehow. If it's just
>> two single hosts, I think the easiest way would be to create a VPN
>> connection between the two hosts with OpenVPN or the like and then add the
>> tun/tap interfaces into the OVN on each box. You might run into problems
>> if you start adding more hosts though, as if the host with the VPN goes
>> down it would disconnect the two datacenters.
>>
>> If the two datacenters are on the same physical network (ie, you just
>> mean oVirt datacenter and not different colocation providers) then adding a
>> VLAN to the NICs connected to the OVN interface would work. You would
>> probably have to setup some sort of channel bonding/LACP as you add more
>> hosts, but OVN should be able to handle that simply enough.
>>
>> On 2017-04-20 07:33 PM, users-request at ovirt.org wrote:
>>
>>> Date: Thu, 20 Apr 2017 14:43:26 -0400
>>> From: Linov Suresh <linov.suresh at gmail.com>
>>> To: users at ovirt.org
>>> Subject: [ovirt-users] Communicate between the guest vm's hosted on
>>> different hosts on different data centres using OVS
>>> Message-ID:
>>> <CALdvvBP6MwbKa-P=q-UeZHMayZ3YPRpjersL0u=2srG=pcCnkQ at mail.gm
>>> ail.com>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> Hello,
>>>
>>> I have configured OVS network on oVirt 4.1.1, following the document
>>> https://www.ovirt.org/blog/2016/11/ovirt-provider-ovn/
>>>
>>> I have created OVN Provider, and created new Logical Network for OVS
>>> using
>>> OVN Provider. I have synced the network also selected OVS when I created
>>> the cluster.
>>>
>>> I have two data centres and each data centre has one host each.
>>>
>>> Now I have created VM's selecting OVS network (not ovirtmgmt). VM's in
>>> the
>>> same data centre can talk to each other.
>>>
>>> How do i make the VM's hosted on different data centre can talk to each
>>> other?
>>>
>>> Appreciate your help in advance,
>>>
>>> Sincerely,
>>>
>>> Suresh.
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170423/56ac6b64/attachment.html>
More information about the Users
mailing list