Versions Compared

Old Version 29

changes.mady.by.user Unknown User (alena1108)

Saved on

compared with

New Version 30

changes.mady.by.user Unknown User (alena1108)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are 2 tiers in the VPC - Web tier A and Application tier B. Traffic to Web tier is balanced on the VPC VR on the public side. User wants traffic coming from Web to App tier to be balanced as well. Load balancing on the APP tier will be covered by the Internal LB feature.

Internal LB can be handled by 2 network providers:

  • InternalLBVm - have to add support for this provider first.
  • Netscaler VPX

General flow

With InternalLBVM:

...

API name

Request parameters

Response parameters

Available to regular user

createLoadBalancingRule

New parameters:

  • schema (String enum, with External/Internal choices; optional; =External by default)
  • sourceIpAddress (String, optional, can be used only with networkId conjunction)  
    Changes to existing parameters:
  • None
    networkId=(guestNetworkId of the network where internal LB is supported) is passed in w/o sourceIpAddress param, 
    the IP address from the guest network will get acquired on the fly and be assigned to the Load Balancing Rule.

New parameters:

  • schema
  • sourceIpAddress
    Changes to existing parameters:
  • None

yes

listLoadBalancingRules

New parameters:

  • schema
  • sourceIpAddress
    Changes to existing parameters:
  • None

Each Load Balancer will have new parameters:

  • schema
  • sourceIpAddress
    Changes to existing parameters:
  • None

yes

...