Hi Pierre We are aware that vm.instancename.flag=false lead's tot he described naming. But our experience with this setting was not good, we are running also some PaaS services for our client's and troubleshooting became a nightmare as the client is not aware if the "i-xx-yyyy-VM" name of his instances and for our support it's not easy to find the releation between client's hostname and cs instance name.
Also in the 4.2.1 documentation it states clearly that the naming should be as follow: "The following table explains how a VM name is displayed in different scenarios. User-Provided Display Name | vm.instancename.flag | Hostname on the VM | Name on vCenter | Internal Name Yes | True | Display name | i-<user_id>-<vm_id>-displayName | i-<user_id>-<vm_id>-displayName We really like to know 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: instance naming in a vmware 5.1 cloudstack 4.2.1 setup > > 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 > Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Tue, Jan 21, 2014 at 10:48 AM, Fuchs, Andreas (SwissTXT) < > andreas.fu...@swisstxt.ch> wrote: > > > 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 update, vm's are just named as follow: > > > > "user_entered_vm_name" > > > > No "i-id-number-" anymore in vSphere. Global setting is unchanged. > > This leads to issues when two different customers try to create a vm > > with the same name! while cloudstack creates the instance in the db, > > vspeher will not create a vm with the same name as an already existing vm. > > This naming is also different from the descriptions in the docs. > > Do others see this issue too? Or might it be related to our installation? > > > > Best regards > > Andi > > > > > > > >
