cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Luc Dion <pd...@cloudops.com>
Subject Re: instance naming in a vmware 5.1 cloudstack 4.2.1 setup
Date Wed, 22 Jan 2014 16:42:26 GMT
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.Fuchs@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
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message