• Created by Unknown User (alena1108), last updated on Mar 18, 2013 2 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Introduction

This documents gives an overview to the design and functional implementation for Internal Load Balancing on VPC tiers.

Feature developers:

  • APIs and Orchestration level - Alena Prokharchyk
  • Backend - to be assigned

Use case

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. Admin wants traffic coming from LB to App tier to be balanced as well. Load balancing on the APP tier will be covered by the Internal LB feature.

The general flow

  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

API and Orchestration level

Enable Internal LB on VPC tier

Introduce new Network Provider - InternalLBVm. This provider supports only 1 service  - LB

In order to have Internal Load Balancing support on VPC tier, the tier has to be created from the network offering with Service=LB, Provider=InternalLBVm. 

Java code changes
  • Introduce new Network Element - InternalLBVm. Make it extend LoadBalancingServiceProvider interface.
  • Introduce InternalLBNetworkApplianceManager
  • Allow to use network offering having LB/InternalLBVm to be used only when create network inside VPC
Backend changes

For the backend engineer to complete. We might need a separate template/set of scripts for this kind of vm, or we might use the existing VR template.

Web Services API

No changes to existing Apis

DB

Add one more default Network offering having LB Service with Internal LB provider. Insert this offering as a part of the upgrade as well.

Allocate IP address from the guest network

Internal Load Balancer gets created for the Guest IP address allocated from the App tier.

Java code changes
Backend changes
Web Services API

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

  • allocateIpAddress. Request parameter
  • releaseIpAddress
  • listIpAddresses

DB
TBD

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

UI

TBD

  • No labels