You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "JnSchl (JIRA)" <ji...@apache.org> on 2018/04/24 16:56:00 UTC

[jira] [Created] (CLOUDSTACK-10371) Internal Names of VMs if a move was performed

JnSchl created CLOUDSTACK-10371:
-----------------------------------

             Summary: Internal Names of VMs if a move was performed
                 Key: CLOUDSTACK-10371
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10371
             Project: CloudStack
          Issue Type: New Feature
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: JnSchl


The "Internal Names" of VMs follow a specific schema.

If a VM is moved to another account or project the internal name does not change and the schema breaks.

There is some potential to get confused if you try to find/list/debug moved VMs in the UI and on the hypervisor level too.

Maybe the best way is to have the ability to change the naming schema to a neutral one in the global settings. Changing the internal name during a move might an alternative way. Goal should be not break the naming schema if some VMs are moved during their lifecycle.

In addition, the second number displays the exact amount of deployed VMs, maybe a neutral suffix might be better.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)