2 a.m.
--_000_AT5PR84MB0033516E5EEAAAB43924AB58B55F0AT5PR84MB0033NAMP_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Is there any solution to it on oVirt 3.6?
I am also planning to move hosted engine from NFS storage to ISCSI .
~Ravi
--_000_AT5PR84MB0033516E5EEAAAB43924AB58B55F0AT5PR84MB0033NAMP_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40" <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft
Word 15 (filtered medium)" <style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" / </xml><![endif]--><!--[if gte mso
9]><xml <o:shapelayout
v:ext=3D"edit" <o:idmap v:ext=3D"edit"
data=3D"1" /
</o:shapelayout></xml><![endif]--
</head <body lang=3D"EN-US"
link=3D"#0563C1" vlink=3D"#954F72" <div
class=3D"WordSection1" <p
class=3D"MsoNormal">Is there any solution to it on oVirt
3.6?<o:p></o:p>=
</p <p
class=3D"MsoNormal"><o:p> </o:p></p <p class=3D"MsoNormal">I am also planning to
move hosted engine from NFS st=
orage to ISCSI .
<o:p></o:p></p <p
class=3D"MsoNormal"><o:p> </o:p></p <p
class=3D"MsoNormal">~Ravi<o:p></o:p></p <p
class=3D"MsoNormal"><o:p> </o:p></p <p
class=3D"MsoNormal"><o:p> </o:p></p </div
</body </html
--_000_AT5PR84MB0033516E5EEAAAB43924AB58B55F0AT5PR84MB0033NAMP_--
7:11 a.m.
New subject: Migrate hosted-engine from NFS to ISCSI
On Thu, Jun 9, 2016 at 9:00 AM, Madhuranthakam, Ravi Kumar
<ravi-kumar.madhuranthakam(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:16 a.m.
New subject: Migrate hosted-engine from NFS to ISCSI
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.
~Ravi
-----Original Message-----
From: Simone Tiraboschi [mailto:stirabos@redhat.com]
Sent: Monday, June 13, 2016 5:42 PM
To: Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam(a)hpe.com>; Yedidyah Bar
David <didi(a)redhat.com>
Cc: users(a)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(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:19 a.m.
New subject: Migrate hosted-engine from NFS to ISCSI
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(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.
~Ravi
-----Original Message-----
From: Simone Tiraboschi [mailto:stirabos@redhat.com]
Sent: Monday, June 13, 2016 5:42 PM
To: Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam(a)hpe.com>; Yedidyah Bar
David <didi(a)redhat.com>
Cc: users(a)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(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:49 a.m.
New subject: Migrate hosted-engine from NFS to ISCSI
On Wed, Jun 15, 2016 at 5:16 PM, Madhuranthakam, Ravi Kumar
<ravi-kumar.madhuranthakam(a)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@redhat.com]
Sent: Monday, June 13, 2016 5:42 PM
To: Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam(a)hpe.com>; Yedidyah Bar
David <didi(a)redhat.com>
Cc: users(a)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(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
11:18 a.m.
New subject: Migrate hosted-engine from NFS to ISCSI
On Wed, Jun 15, 2016 at 5:49 PM, Simone Tiraboschi <stirabos(a)redhat.com> wrote:
On Wed, Jun 15, 2016 at 5:16 PM, Madhuranthakam, Ravi Kumar
<ravi-kumar.madhuranthakam(a)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.
Just another things, you'll probably have also to filter that devices
out of LVM.
> ~Ravi
>
> -----Original Message-----
> From: Simone Tiraboschi [mailto:stirabos@redhat.com]
> Sent: Monday, June 13, 2016 5:42 PM
> To: Madhuranthakam, Ravi Kumar <ravi-kumar.madhuranthakam(a)hpe.com>; Yedidyah
Bar David <didi(a)redhat.com>
> Cc: users(a)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(a)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(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
2880
days inactive
2886
days old
5 comments
2 participants
participants (2)
-
Madhuranthakam, Ravi Kumar -
Simone Tiraboschi