[ovirt-users] Migrate hosted-engine from NFS to ISCSI

[Simone Tiraboschi]

On Wed, Jun 15, 2016 at 5:16 PM, Madhuranthakam, Ravi Kumar
<ravi-kumar.madhuranthakam at hpe.com> wrote:
> Hi ,
> Thanks for your reply. Looking forward to get this feature integrated in in upcoming releases .
>
> One more question
>
> 1) I have few Raw disks (/dev/sdx  or some LVM's ) and I need to directly attach it to oVirt VM without any file system bottle necks.
> But this VM is part of data center(shared type) .
> We are not planning to use any shared storage and shared data center .
>
> Here use case is that One Of the VM(HP StoreVirtial Applaince ) is our software oriented storage which  will consume raw disks which are attached to local host.
>
> How to do that ? I see that attach disk shows only NFS/ISCSI /direct LUn optins .
>
> Thanks for your time.

You can expose it over iSCSI via targetcli and directly attach it to
the single VM as a direct LUN.

> ~Ravi
>
> -----Original Message-----
> From: Simone Tiraboschi [mailto:stirabos at redhat.com]
> Sent: Monday, June 13, 2016 5:42 PM
> To: Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam at hpe.com>; Yedidyah Bar David <didi at redhat.com>
> Cc: users at ovirt.org
> Subject: Re: [ovirt-users] Migrate hosted-engine from NFS to ISCSI
>
> On Thu, Jun 9, 2016 at 9:00 AM, Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam at hpe.com> wrote:
>> Is there any solution to it on oVirt 3.6?
>
> You can try to follow the discussion here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1240466
>
> Basically you have to:
> - take a backup of the engine with engine-backup
> - deploy from scratch on an host pointing to the new storage domain
> - - if you are going to use the engine appliance, here you have to avoid automatically executing engine setup since:
> - - - you have to manually copy the backup to the new VM
> - - - you have tu run engine-backup to restore it,
> - - - only after that you can execute engine-setup
> - at the end you can continue with hosted-engine setup ***
> - then you have to run hosted-engine --deploy again on each host to point to the new storage domain
>
> *** the flow is currently broken here: hosted-engine-setup will fail since:
> - the old hosted-engine storage domain is already in the engine (since you restored the DB) but you are deploying on a different one
> - the engine VM is already in the DB but you are deploying with a new VM
> - all the hosted-engine host are already in the engine DB
>
> So you'll probably need to manually edit the engine-DB just after DB recovery in order to:
> - remove the hosted-engine storage domain from the engine DB
> - remove the hosted-engine VM from the engine DB
> - remove all the hosted-engine host from the engine DB since you are going to redeploy them
>
> We are looking for adding this capability to engine-backup
>
>> I am also planning to move hosted engine from NFS storage to ISCSI .
>>
>>
>>
>> ~Ravi
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>