I had this situation a while back. As I recall ovirt has no way to selectivity un-mount
devices exposed via an iSCSI target.
So the problem you could hit is that if you tried to put your data domain into maintenance
it would nuke any other domains that are accessed through that target (e.g. your
For me the situation was even worse as I was doing boot-from-SAN as well. So I would loose
the boot disk.
On my NetApp I ended up creating three targets: BFS, hosted-engine & data.
---- On Mon, 28 Oct 2019 11:27:53 +0000 wodel youchi <mailto:email@example.com>
We have an oVirt Platforme using the 4.1 version.
when the platforme was installed, it was made of :
- Two HP Proliant DL380 G9 as hypervisors
- One HP MSA1040 for iSCSI
- One Synology for NFS
- Two switches, one for network/vm traffic, the second for storage traffic.
The problem : the hosted-engine domain was created using iSCSI on the HP MSA. The problem
is that this disk array does not give the possibility to create different targets, it
presents just one target.
At that time we create both the hosted-engine and the first data domain using the same
target, and we didn't pay attention to the information saying "if you are using
iSCSI storage, do not use the same iSCSI target for the shared storage domain and data
- what problems can be generated by this (mis-)configuration?
- Is this a must to do (correct) configuration.
Users mailing list -- mailto:firstname.lastname@example.org
To unsubscribe send an email to mailto:email@example.com
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/