I understand the risks, and things seem to be working so far. I've been able to work around some oddities before in the database and xen config files, so I'm not too concerned with what I have. We also have a testing/dev environment to learn lessons on before mucking up the live environment.
The concern I have though, is if the virtualizor UI is not available for any reason (proxy server goes down, IP change, etc), then matching hostname to LVM is not obvious.
NOW I know you can grep the configs in /etc/xen/auto/, but the first time I had an issue with no UI available, some extra downtime was eaten up figuring out which of the dozens of LVMs I had to work on. If they were named less randomly, that wouldn't have been the case.
|