On 10/03/2013 03:45 PM, Gianluca Cecchi wrote:
On Thu, Oct 3, 2013 at 2:08 PM, Dan Kenigsberg wrote:
>>
>>>> SO the question is : what about ovirtmgmt network for gluster
>>>> replication when gluster domain is provided by ovirt nodes?
>>>> I suppose it could be a problem too, couldn't it?
>>
>> yes that is correct, using ovirtmgmt for non management traffic is not a
>> good idea.
>>
>>>> In case I have a dedicated network for gluster for the nodes, how can
>>>> i configure it?
>>
>> Generally there two ways to go about this:
>>
>> 1. add a new network role 'gluster replication' and then adjust the
>> engine code to pass the network with this role as parameter to the
>> replication verb in VDSM.
>>
>> 2. in the replication verb in the UI let the user choose which network
>> to use for the replication.
>>
>> I am not familiar with the replication verb so I might be missing
>> something but otherwise I think that solution 2 is more simple and less
>> invasive then requiring a new network role.
>
> Bala, is there a means to select, for each node, which IP address is to
> be used for replication? AFAICT we use the host fqdn, which most
> probably resolves to the ovirtmgmt device.
what is "replication verb in the UI"? Inside UI when I click "create
volume" and then "add Bricks" buttons I can only select "Server"
that
in my case is a drop down menu containing only ip addresses of my 2
hypervisors....
Or simply do you mean development steps to integrate this missing
functionality in oVirt with steps 1. and 2.?
I am probably missing some background around Gluster, could you share
what triggers the gluster replication?
Thanks,
Gianluca