oVirt is still managing the cluster via ovirtmgmt network. The same rule
applies for tagging networks as VM networks, Live Migration networks
etc. Gluster is no different, except that it involved a couple of manual
steps for us to configure it.
On 01/18/2016 03:53 PM, Fil Di Noto wrote:
Thanks I will try this. I am running ovirt-engine
3.6.1.3-1.el7.centos
In the configuration described, is oVirt able to manage gluster? I am
confused because if oVirt knows the nodes by their ovirtmgmt network
IP/hostname aren't all the VDSM commands going to fail?
On Mon, Jan 18, 2016 at 6:39 AM, combuster <combuster(a)gmail.com> wrote:
> Hi Fil,
>
> this worked for me a couple of months back:
>
>
http://lists.ovirt.org/pipermail/users/2015-November/036235.html
>
> I'll try to set this up again, and see if there are any issues. Which oVirt
> release are you running ?
>
> Ivan
>
> On 01/18/2016 02:56 PM, Fil Di Noto wrote:
>> I'm having trouble setting up a dedicated storage network.
>>
>> I have a separate VLAN designated for storage, and configured separate
>> IP addresses for each host that correspond to that subnet. I have
>> tested this subnet extensively and it is working as expected.
>>
>> Prior to adding the hosts, I configured a storage network and
>> configured the cluster to use that network for storage and not the
>> ovirtmgmt network. I was hopping that this would be recognized when
>> the hosts were added but it was not. I had to actually reconfigure the
>> storage VLAN interface via oVirt "manage host networks" just to bring
>> the host networks into compliance. The IP is configured directly on
>> the bond0.<vlanid>, not on a bridge interface which I assume is
>> correct since it is not a "VM" network.
>>
>> In this setup I was not able to activate any of the hosts due to VDSM
>> gluster errors, I think it was because VDSM was trying to use the
>> hostname/IP of the ovirtmgmt network. I manually set up the peers
>> using "gluster peer probe" and I was able to activate the hosts but
>> they were not using the storage network (tcpdump). I also tried adding
>> DNS records for the storage network interfaces using different
>> hostnames but gluster seemed to still consider the ovirtmgmt interface
>> as the primary.
>>
>> With the hosts active, I couldn't create/activate any volumes until I
>> changed the cluster network settings to use the ovirtmgmt network for
>> storage. I ended up abandoning the dedicated storage subnet for the
>> time being and I'm starting to wonder if running virtualization and
>> gluster on the same hosts is intended to work this way.
>>
>> Assuming that it should work, what is the correct way to configure it?
>> I can't find any docs that go in detail about storage networks. Is
>> reverse DNS a factor? If I had a better understanding of what oVirt is
>> expecting to see that would be helpful.
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>