91
Bugs / Re: Installation of OMS fails
« Last post by Decoyed on February 28, 2013, 10:04:57 PM »Deemoowoor, thanks for hints!
best
Dec.
best
Dec.

[formatters]
keys=default
[formatter_default]
format=%(asctime)s %(thread)x %(name)s %(levelname)s %(message)s
[handlers]
keys=default
[handler_default]
class=logging.FileHandler
args=('omsd.log',)
formatter=default
[loggers]
keys=root
[logger_root]
level=INFO
handlers=default
simple HA approach where High-Availablity service will be the hypervisor service - not VM itself. So cluster checks hypervisor status (vz and kvm) - if that service or server hardware fails all VMs will be restarted on another server/cluster node.

OMS at the moment only supports management of OpenVZ-based VMs. We started by supporting both via libvirt, unfortunately libvirt is too high level abstraction, so we've switched to hypervisor specific functionality starting from OpenVZ containers as this is what we use the most. 
please note that if VM is put under HA cluster service - then you MUST manage VM state (starting/stopping) also with cluster tools.
Currently TUI/OMS wont detect VMs under HA - and wont use cluster tools for such VM management. However they can be still used to deploy VMs into RHCS HA cluster and then configure HA service and control VM state with clusvcadm tool
TUI offers a local management of VMs, which are running on the same host. So, if a system is configured for HA and the failover brings new VMs to a certain host, then yes, TUI will be able to show/manage those VMs.