On 01/17/2014 11:32 AM, Gianluca Cecchi wrote:
On Fri, Jan 17, 2014 at 10:25 AM, Elad Ben Aharon  wrote:
Indeed,
Using ovirt-engine APIs you can edit your iSCSI storage domain and extend it by 
adding physical volumes from your shared storage (The process is managed by 
ovirt-engine, the actual actions on your storage are done by your host which 
has VDSM installed on).

----- Original Message -----
From: "Hans Emmanuel" <hansemman...@gmail.com>
To: "Elad Ben Aharon" <ebena...@redhat.com>
Cc: users@ovirt.org
Sent: Friday, January 17, 2014 6:37:56 AM
Subject: Re: [Users] iSCSI storage domain.

Thanks for the reply .


Are you suggesting to use Ovirt Engine to resize iSCSI storage domain ?


On Thu, Jan 16, 2014 at 7:11 PM, Elad Ben Aharon <ebena...@redhat.com>wrote:

Hi,

Both storage types are suitable for production setup.
As for your second question -
manually LVM resizing is not recommended, why not using RHEVM for that?

----- Original Message -----
From: "Hans Emmanuel" <hansemman...@gmail.com>
To: users@ovirt.org
Sent: Thursday, January 16, 2014 3:30:39 PM
Subject: Re: [Users] iSCSI storage domain.



Could any one please give valuable suggestions?
On 16-Jan-2014 12:28 PM, "Hans Emmanuel" < hansemman...@gmail.com > wrote:



Hi all,

I would like to get some comparison on NFS & iSCSI storage domain . Which
one more suitable for a production setup ? I am planning to use LVM backed
DRBD replication . And also is that possible to expand iSCSI storage domain
by simply resizing backend LVM ?

--
Hans Emmanuel


I think one option should be to provide the user, if not already
present/tested/supported, the opportunity to resize the LUN on storage
array and then run a rescan from oVIrt to see the new size and use it
without disruption of service.

3.4 adds this:
Bug 961532 - [RFE] Update storage domain's LUNs sizes in DB after lun resize

please note:
- you can extend a *storage domain* by adding an extra LUN to it from
  ovirt-engine.
- you *cannot* resize the LUN from ovirt-engine, but you can do that
  from the storage side, which in 3.4 will be reported by ovirt-engine
  via bug 961532

and on the general question - what i like about NFS is its way more simple to work with, troubleshoot, inject and recover on issues.

also note, on iscsi, LVM has issues on scale once you pass a several hundreds of disks or snapshots (per storage domain).

To avoid also LUNs proliferation on storage arrays that in general are
providing storage to many sources, also different from oVirt itself
Gianluca
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to