It would be helpful to have this ‘function’ modified so that it is an option for end users to either use it, or not use it.
We are facing the same dilemma with this use case in our environment. host/vm/system names and IP’s are all centrally managed and are required to be consistent and managed upstream.
Introducing a new requirement like this introduces issues with existing operational processes within the established vCenters that are hosting over 5,000 existing VM’s.
I don’t see wild import as an issue , as opennebula would be new to the environment and the hosts can easily be renamed without the ‘wild customization’ during inital setup - but the reverse is not true - introducing new ‘prefix-’ naming convention into VM names will introduce changes to the existing infrastructure vcenter scripts, monitoring, operational processes.
I understand that can be scripted as well after landing in the vCenter, but it would be much simpler to be able to allow upstream processes already responsible for generating host/vm/system names continue to feed this information.