You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/21 16:59:17 UTC

[jira] [Commented] (CLOUDSTACK-778) user provided hostname to be specified in vCenter instead of CloudStack generated name

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663041#comment-13663041 ] 

ASF subversion and git services commented on CLOUDSTACK-778:
------------------------------------------------------------

Commit 2bc88ea277a4024afd3b365910ea9f85fde44ebf in branch refs/heads/master from [~gpshilamkar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2bc88ea ]

CLOUDSTACK-778: Add tests for user provided hostname for vms

Automation tests to qualify User provides hostname feature.
1. Defines services class
2. Test to verify custom hostname for the instance with internal name
3. Test to verify custom hostname for the instance without internal name

Signed-off-by: Prasanna Santhanam <ts...@apache.org>

                
> user provided hostname to be specified in vCenter instead of CloudStack generated name
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-778
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-778
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: haroon abdelrahman
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>             Fix For: 4.2.0
>
>
> Release Planning:
> Dev List discussion: unknown
> Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+provided+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs
> Feature Branch: unknown

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira