On 07/05/2012 02:19 PM, Itamar Heim wrote:
On 07/05/2012 10:06 AM, Robert Middleswarth wrote:
>> > 2) You can not change what interface / IP gluster uses, it will
>>> always use the ovirtmgmt network. This is a weakness as many people
>>> have
>>> an independent network just for storage and they can't use them with
>>> 3.1.
>>
>> sorry, i don't understand this one - only the management of gluster is
>> done via this interface. you can define a different logical network in
>> the cluster for storage, configure ip addresses for them, and define
>> the mount point that way.
>> (well, apart from potential bugs on network definitions in 3.1 which
>> may still exist)
>>
>
> Unless I am missing something if I setup Gluster to use anything other
> then the ovirtmgmt network then I can't create volumes because the
> engine uses the ovirtmgmt networks IP's and Gluster doesn't recognize
> it.
engine uses ovirtmgmt to create them.
you can define another network to consume them (assuming you have more
than a single nic. otherwise, i'm not sure why it matters).
Are you suggesting that I add both Network IP into Gluster. That would
work but how would I know what network Gluster would use to sync up with?
Thanks
Robert