Using this logic, oVirt should detect existing storages instead of
attaching/mounting them. The same is for networks. A VM can be placed on any
host that has required storage(s) and network(s) attached. Datacenters/clusters
would be virtual things.
Pros:
* Flexibility for Linux admins, wider usage
* Less code. Less bugs.
Cons:
* You must be a Linux admin to maintain oVirt instances.
* It’s a step back in RHEV/oVirt functionality. I oVirt would lose users.
RedHat would lose customers.
From: <users-boun...@ovirt.org> on behalf of Marcin Kruk
<askifyoun...@gmail.com>
Date: Thursday, 16 March 2017 at 20:17
To: users <users@ovirt.org>
Subject: [ovirt-users] iSCSI and multipath deliberation
In my opionion the main problem in configuration iscsi and multipath is that
the ovirt developers try to start everything automaticaly during installation,
and then during start services like vdsmd.
But during installation process adminstrator shoud choose the right multipath
WWID identifier only.
And administrator should be responsible for setting multipath and iSCSI
properly.
Otherwise ovirt installator does everything automaticaly in the universal way
which is weak due to so many storage types.
Howgh :)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
