PM
To: dev@cloudstack.apache.org
Subject: Re: Feature proposal: Resource naming policies
With this feature, it is possible to change the names that get sent to the
hypervisor, yes. In 4.2 we actually had to fix an issue with the security
groups because they weren't parsing properly. That isn
Awesome and long awaited
On 4/14/16 4:40 AM, Jeff Hair wrote:
> Yesterday, we submitted this pull request:
> https://github.com/apache/cloudstack/pull/1492
>
> This originally grew out of making the VirtualMachineName class non-static
> (original PR is mentioned in the above link). We're pr
With this feature, it is possible to change the names that get sent to the
hypervisor, yes. In 4.2 we actually had to fix an issue with the security
groups because they weren't parsing properly. That isn't in the commit yet.
We will put it in.
It would be useful to have a list of all the places th
Are these the names that are sent to HV? For e.g. VM name in the format
i-xx-yy-VM. Currently there are functionalities that rely on the internal
naming convention. All such functionalities needs to be handled appropriately.
-Koushik
From: Jeff Hair
Sen
sounds usefull for companies that for instance want to enforce uuid in name
or include some user string in it, same would be true for networks. look
forward to your design.
On Thu, Apr 14, 2016 at 1:40 PM, Jeff Hair wrote:
> Yesterday, we submitted this pull request:
> https://github.com/apache/
