You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/07/31 18:01:52 UTC
[jira] [Closed] (CLOUDSTACK-2082) [Enhancement] [GSLB] Provide a
machanism to reprogram/update GSLB info on Network Element.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru closed CLOUDSTACK-2082.
--------------------------------------------------
Have verified it on the latest CloudStack build with new "updateGloabalLoadBalancerRule" API. Everything went fine. Closing the bug.
> [Enhancement] [GSLB] Provide a machanism to reprogram/update GSLB info on Network Element.
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2082
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2082
> 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
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
>
> As of now we don't have anyway to update / reprogram GSLB info on Netscaler device.
> Providing such a mechanism will address the following situations
> 1. When Cloud Admin wants to change the "isGslbProvider" value
> 2. In case of any GSLB related information change
> 3. GSLB element is corrupted or configuration lost situations
--
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