GitHub user nitin-maharana opened a pull request:

    https://github.com/apache/cloudstack/pull/1337

    CLOUDSTACK-9235: Autoscale button is missing in VPC

    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.
    
    Fix:
    ===
    In case of VPC, it checks the services available.
    If LB is there, It checks the provider is Netscaler then it shows the 
button or hides it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nitin-maharana/CloudStack 
CloudStack-Nitin20_4.7

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1337.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1337
    
----
commit 68ca3cb58af02bcbfc2d95d52b69483478df33ce
Author: Nitin Kumar Maharana <nitinkumar.mahar...@citrix.com>
Date:   2015-10-13T06:18:12Z

    CLOUDSTACK-9235: Autoscale button is missing in VPC
    
    In case of VPC, it checks the services available.
    If LB is there, It checks the provider is Netscaler then it shows the 
button or hides it.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to