Page History

...

1. Create tier B using network offering with Service=Lb, Provider=InteralLBVm
2. Acquire guest IP address - Ip1 - from the tier B.
3. Create Internal Load Balancer LB1 for Ip1, public port 80, private port 80. The new internal LB VM starts up with the Ip1.
4. Add vm1 to the LB1. A new Internal LB with IP1 starts up, and the The rule for Ip1/VM1/ports 80:80 is configured inside the HA proxy
5. Add vm2 to the LB1. The rule for IP1/VM2/80:80 is configured inside the HA Proxy
6. Create Internal Load Balancer LB2 for IP1, public port 81, private port 81. No need to start a new Internal LB vm as it's been already started for IP1.
7. If you want to manage access from tier A to tier B, setup Network ACLs

API and orchestration level

New APIs:

• createInternalLoadBalancerRule (has all parameters listed in our regular createLBRule api except for the publicIpId). NetworkId will be required.
• deleteInternalLoadBalancerRule
• listInternalLoadBalancerRules

create/list APIs should return IP that is acquired automatically as a part of LB creation.

Existing LB APIs should be supported to add user vms to the LB.

...

DB

New tables

TBD

Upgrade 

Either have to upgrade existing default VPC/Network offering with the new Provider for LB service, or create a new default one having Internal LB provider in place.

...