[
https://issues.apache.org/jira/browse/LIBCLOUD-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990439#comment-13990439
]
ASF subversion and git services commented on LIBCLOUD-550:
----------------------------------------------------------
Commit b20c62a97167d71fe1fc3f7ba4bc2938476d7042 in libcloud's branch
refs/heads/trunk from [~fifthecho]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=b20c62a ]
LIBCLOUD-550_DisplayName
Added support for "displayname" CloudStack deployment parameter and removed
automatic setting of "name" parameter.
This will allow for deployment of instances without a hostname, but with a
displayname, so that you can have multiple tenants using the same displayname
with unique hostnames being generated from the instance UUID.
Closes #289
Signed-off-by: Tomaz Muraus <[email protected]>
> Add support for CloudStack deployVirtualMachine displayname parameter
> ---------------------------------------------------------------------
>
> Key: LIBCLOUD-550
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-550
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Affects Versions: 0.14.0-beta3
> Reporter: Jeff Moody
> Priority: Trivial
> Labels: easy, easyfix, patch
> Fix For: 0.14.0-beta3
>
> Attachments: cloudstack-display-name.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Add support for the displayname API parameter and modify the name API
> parameter to allow for instances to be created without that parameter being
> set.
> This is the behavior we expect when provisioning instances in a multi-tenant
> Public flat-network Cloud to prevent customers from encountering instance
> name conflicts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
