[
https://issues.apache.org/jira/browse/CLOUDSTACK-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106024#comment-15106024
]
ASF GitHub Bot commented on CLOUDSTACK-9235:
--------------------------------------------
Github user pdube commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1337#discussion_r50060205
--- Diff: ui/scripts/network.js ---
@@ -3667,8 +3652,16 @@
return 2;
//hide Autoscale button (both header and form)
}
} else { //from VPC
section
- //VPC doesn't
support autoscale
- return 2;
+ var
lbProviderIsNetscaler;
+ var services =
args.context.vpc[0].service;
+
+
lbProviderIsNetscaler = checkIfNetScalerProviderIsEnabled(services);
+
+ if
(lbProviderIsNetscaler == true) { //AutoScale is only supported on Netscaler
(but not on any other provider like VirtualRouter)
--- End diff --
You could remove the condition here, it is unnecessary
> Autoscale button is missing in VPC
> ----------------------------------
>
> Key: CLOUDSTACK-9235
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9235
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Kumar Maharana
>
> Autoscale button is missing. This should not be the case since we are able to
> add NS as the external LB provider in VPC.
> Steps:
> =====
> 1. Create a VPC offering with NS as the external LB provider
> 2. Create a VPC and configure the public tier with the above offering
> 3. Acquire an IP address and try to configure Load Balancing rule
> Result:
> ======
> Autoscale option is not visible at all for the LB.
> Expected Result:
> =============
> Autoscale option should be available and should work exactly like the way it
> works for a normal isolated network with NS. If we choose NS as service
> provider for LB, autoscale should also be visible. If VR is chosen, only then
> we should not display autoscale.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
