Page History

...

1. Create App tier using network offering with Service=Lb, Provider=InteralLBVm
2. Acquire guest IP address - Ip1 - from the App tier.
3. Create Internal Load Balancer LB1 for Ip1, public port 80, private port 80. The new internal LB VM starts up on App tier with the Ip1.
4. Add vm1 to the LB1. 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

...

Architecture and

...

design description

Enable Internal LB on VPC tier

...

Allocate IP address from the guest network

Before creating the Internal Load Balancer gets created for , the Guest IP address has to be allocated from the App tier.

Java code changes

• New code for allocating and managing IP addresses from the guest network to the account. Might need to create a new manager for that.

Backend changes

No backend changes are needed for this part

Web Services API

New set of APIs to allocate guest IP address to the account.

...

DB
TBD

Create Load Balancer for the Guest IP address

Internal Load Balancing Vm life cycle

...

Limitations

• Internal and Public Lb are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB
• Supported just on VPC networks

...