Last week, one of our DC went through a network crash, and surprisingly,
most of our hosts did resist.
Some of them lost there connectivity, and were stonithed.
I'd like to be sure to understand what tests are made to declare a host
- On the storage part, I guess EVERY host is doing a read+write test
(using "dd") towards the storage domain(s), every... say 5 seconds (?)
In case of failure, I guess a countdown is triggered until this host is
But the network failure we faced was not on the dedicated storage
network, but purely on the "LAN" network (5 virtual networks).
- What kind of test is done on each host to declare the connectivity is
OK on every virtual network?
I ask that because oVirt has no knowledge of any gateway it could ping,
and in some cases, some virtual networks don't even have a gateway.
Is it a ping towards the SPM?
Towards the engine?
Is it a ping?
I ask that because I found out that some host restarted nicely, ran some
VMs, which had their NICs OK, but inside those guests, we find evidences
that they were not able to communicate with very simple networks usually
provided but the host.
So I'm trying to figure out if a host could come back to life, but
 Thus, I don't clearly see the benefit of the SPM concept...
I'm trying to find what are the different ways / approaches to automated users/groups creation, based on a LDAP/AD database.
This is my first problematic : when a LDAP/AD provider is joined, and a user is created in ovirt from this provider, the user heritates a part of the attributes from this LDAP database. Now if I change one attribute on the LDAP side (for example "first name"), it isn't updated on the ovirt user.
Would there be other way to update this information than creating / deleting the user ?
My second problematic is what should I use to automate creation of users.
It seems possible with :
- shell scripting : using ovirt-aaa-jdbc-tool
- python SDK
- java SDK
- rest API
Which one of these approaches would be the most simple ? I'm more familiar with shell scripting than other languages. That would be nice to find a way with it.
Concerning ovirt-aaa-jdbc-tool, I've heard it was only adding/deleting users from the internal DB, not the others. In that case, is there a way in shell scripting to interact with other profiles than internal ?
Is there files somewhere containing users and their informations I could modify ?
What would happen if a user is in use and it is modified/deleted at the same time ?
I know it makes a lot of questions, but I can't really get started before having those answers.
I did a yum update on one of my Ovirt Hosts a few days ago.
All of the VM's on that host have been shown in the web UI with a status of
'Wait For Launch'.
The VM's all appear to still be up and running but I can't manage/migrate
Is there anything I can do to clear this issue ?