Description of problem:
Currently we enforce multipath configuration to a specific set of params we determined are necessary, this behavior might cause problems if an existing (compliant) configuration is used.
Current solution is to mark the configuration as private but no further checking is done to make sure that the private configuration complies with rhev's requirements.
What we should do is:
a. upon startup, check configuration (e.g. make sure that use_friendly_names=no) and if the configuration is not ok, either enforce it (add relevant params instead of overriding entire conf) or fail on startup (if private flag is marked)
In case of hybrid servers (run both as hypervisor and additional services) this has to be dealt with.