That was the intention but I'm unclear as to which is the better approach.
I intended to host all VM related data including OS on the data volumes
(split between data on sdb and data2 on sda).. but now it sounds like doing
VM os disks on a separate volume could be a better approach after reading
this e-mail chain, as I do intend to setup georeplication disaster recovery
at some point and it might be nice to have the flexibility to only
georeplicate the vm data and not OS disks data.
If I were to set it up the other way, i.e. using vmstore to host OS disks
would it be recommended to create a VMSTORE on each device, like this for
example?
ENGINE = SDA (device 1) = 100gb
DATA = SDB (device 2) = 1200gb
DATA2 = SDA (device 1) = 1100gb
VMSTORE = SDA (device 1) = 500gb
VMSTORE2 = SDB (device 2) = 500gb
500gb may be a bit overkill here but you get the point.
On Mon, Jul 30, 2018 at 10:52 AM, Sahina Bose <sabose(a)redhat.com> wrote:
On Mon, Jul 30, 2018 at 7:09 PM, Jayme <jaymef(a)gmail.com> wrote:
> Hello,
>
> Thanks for the feedback. I don't "need" to create only one data
domain,
> I'm more or less trying to confirm whether or not it is proper to configure
> multiple data domains or if I was mis-understanding the setup procedure.
>
> So if I am correct, you are saying that if I have 2 JBOD storage devices
> in each host that best practice is for each of those to have its own data
> volume?
>
> Like this for example:
>
> ENGINE = SDA (device 1) = 100gb
> DATA = SDB (device 2) = 2000gb
> VMSTORE = SDA (device 1) = 500gb
>
DATA2 = SDA (device 1) = 1100gb
>
> That would allocate all the space available on both of my drives (2x2tb)
> and create two data volumes, a 2TB one on SDB device and a 1.1TB on SDA
> device. SDA device would also be used for engine and vmstore volumes. Is
> this correct configuration for two JBOD devices per host?
>
Looks good. I'm assuming you're using VMStore to host ISOs and not VM OS
disks?
> On Mon, Jul 30, 2018 at 10:31 AM, Sahina Bose <sabose(a)redhat.com> wrote:
>
>>
>>
>> On Mon, Jul 30, 2018 at 6:46 PM, Jayme <jaymef(a)gmail.com> wrote:
>>
>>> It's nice to know someone else out there has these questions as well.
>>> What I'd really like confirmation on is basically this: In a JBOD oVirt
>>> HCI configuration with multiple disk devices per host node is it possible
>>> to have just one data volume or is it necessary to create multiple data
>>> volumes (one or more per each physical disk you want to store vm data on)?
>>> Meaning if I had 4 JBOD disks in each node and I wanted VM data to be
>>> stored and accessed on all 4 would I need to create 4 different data
>>> volumes (one per disk). And if so would they have to have unique names and
>>> brick dirs/mount points?
>>>
>>
>> The guideline is to create 1 brick per device and this is what the
>> Cockpit UI implements. When you group together all 4 JBOD disks to form 1
>> brick - you're essentially setting up 1 large brick without any hardware
>> RAID protection for the disks. Any 1 of the disk failure would cause the
>> entire brick to be unavailable and would require healing the whole brick.
>> So if you had 4 1TB disks, you would end up creating a 4TB brick which
>> needs healing - not the best of scenarios.
>>
>> Why do you need to create 1 data storage domain instead of multiple?
>>
>>
>>> - James
>>>
>>>
>>> On Mon, Jul 30, 2018 at 10:09 AM, <william.dossett(a)gmail.com> wrote:
>>>
>>>> Hi James... I'm in sort of the same position... I have 6 JBOD drives
>>>> in each node. I am unsure if I am going to wind up with 6 data stores.
I
>>>> have 5 nodes and have other problems related to when I add those nodes
>>>> further complicating the gluster issue. Hopefully someone can help
clear
>>>> this up as its the last hurdle I face before starting to actually put
work
>>>> loads on this and connecting it into our ManageIQ environment.
>>>> _______________________________________________
>>>> Users mailing list -- users(a)ovirt.org
>>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
https://www.ovirt.org/communit
>>>> y/about/community-guidelines/
>>>> List Archives:
https://lists.ovirt.org/archiv
>>>> es/list/users(a)ovirt.org/message/VX5CRCDEF4XJBT5LP3VQ6QULSOYX3UTR/
>>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
https://www.ovirt.org/communit
>>> y/about/community-guidelines/
>>> List Archives:
https://lists.ovirt.org/archiv
>>> es/list/users(a)ovirt.org/message/7BVDT2OKDZKRYQAFSLRDJK6RIWAFH7GG/
>>>
>>>
>>
>