You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2013/05/16 07:37:18 UTC

[jira] [Commented] (CLOUDSTACK-2529) [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name

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

Murali Reddy commented on CLOUDSTACK-2529:
------------------------------------------

Its possible, response for GSLB rule does not have the full FQDN. I am assigning this bug to self to have a llok.
                
> [GSLB] [UI] Currently there is no way for an non-ROOT domain user to know the full GSLB domain name
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2529
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2529
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>
>
> Steps to reproduce :
> 1. Have at least one GSLB enabled zone
> 2. Have at least one non-ROOT domain user
> 3. Login as the above user and create a GSLB rule and assign LB rules to GSLB
> Observations:
> (i) Everything goes fine but, there is no way currently to inform the user what will be the full domain name. 
> (ii) It will be good if we can prompt a message and show the complete domain name 
> Complete domain name will be "GSLB domain name specified by user + value of the global setting cloud.dns.name"

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