libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-550) Add support for CloudStack deployVirtualMachine displayname parameter
Date Tue, 06 May 2014 08:54:15 GMT


ASF subversion and git services commented on LIBCLOUD-550:

Commit b20c62a97167d71fe1fc3f7ba4bc2938476d7042 in libcloud's branch refs/heads/trunk from
[;h=b20c62a ]


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

> Add support for CloudStack deployVirtualMachine displayname parameter
> ---------------------------------------------------------------------
>                 Key: LIBCLOUD-550
>                 URL:
>             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

View raw message