ow if somebody else sees our naming issue as well or if it
could be related to our setup/installation
Regards
Andi
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: Mittwoch, 22. Januar 2014 17:43
> To: users@cloudstack.apache.org
> Subject: Re
Hi Andreas,
if you set the flag vm.instancename.flag to false your instance name will
look like : i-##--VM where VM is define in instance.name settings.
Also when you are admin in cloudstack you can see the internal name of all
instances. Would that work for you ?
Pierre-Luc Dion
Archit
Hi we just tested the upgrade from 3.0.7 to 4.2.1 in our test environment
While the upgrade went smooth we see a big issue with vm naming in vmware.
With cs 3.0.7 vm's where named like this:
"i-id-number-user_entered_vm_name"
(with global setting of vm.instancename.flag = true)
After the updat
