Re: Feature proposal: Resource naming policies

ursday, April 14, 2016 9:40 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 p

Re: Feature proposal: Resource naming policies

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

Re: Feature proposal: Resource naming policies

Thursday, April 14, 2016 5:10 PM > To: dev@cloudstack.apache.org > Subject: Feature proposal: Resource naming policies > > Yesterday, we submitted this pull request: > https://github.com/apache/cloudstack/pull/1492 > > This originally grew out of making the VirtualMachineName class n

Re: Feature proposal: Resource naming policies

t;j...@greenqloud.com> Sent: Thursday, April 14, 2016 5:10 PM To: dev@cloudstack.apache.org Subject: Feature proposal: Resource naming policies Yesterday, we submitted this pull request: https://github.com/apache/cloudstack/pull/1492 This originally grew out of making the VirtualMachineName cla

Re: Feature proposal: Resource naming policies

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: >

Feature proposal: Resource naming policies

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 presenting this as a refactoring of the existing code to enable more