Managing load balancers for the Azure Provider
A load balancer pool is a group of server network interfaces across which network traffic is load balanced. The server network interfaces must all be on the same network. A load balancer pool has a virtual IP address (VIP). Network traffic is addressed to the load balancer VIP and forwarded to a server in the pool based on the load balancing algorithm used for the pool.
The Azure Provider configures an endpoint of a provisioned VM as a load-balanced endpoint to distribute a specific type of traffic among multiple virtual machines in a cloud service. For example, you can spread the load of web request traffic across multiple VMs. For details about how an endpoint serves as an Azure load balancer, see Load balancing virtual machines in Microsoft Azure.
When you configure load balancing of traffic among multiple virtual machines or services, Azure provides random distribution of the incoming traffic.
This topic contains the following sections:
Load balancer pool support for the Azure Provider
You configure and manage load balancers for the Azure Provider, within the context of network containers or within the context of servers. This section provides links to the steps required to configure and manage load balancers.
Note
As a Cloud Administrator, you must define the load balancer settings in the Azure service blueprint if you want to create a load balancer pool and load balancer pool entry as part of an Azure service offering.
| Tasks | Role | Details |
|---|---|---|
| Cloud Administrator | You can perform the following tasks to manage a load balancer and its pools at the network container level:
| |
| Managing load balancer pools by server | Cloud Administrator or End User | You can perform the following tasks to manage a load balancer and its pools at the server level:
|
Considerations for configuring load balancers for the Azure Provider
For an Azure Provider, consider the following information:
- The onboarded Logical Data Center contains a default load balancer, as shown in the figure below:
- The name of the load balancer pool must not be fewer than 3 characters and must not exceed 15 characters.
- The default probe values specified for a load balancer pool for probe interval (in secs) is 15 and the probe count is 2.
- The load balancer pool created by using BMC Cloud Lifecycle Management at the network container level does not create a corresponding entry in the Microsoft Azure portal.
- In a single SOI, you can have multiple load balancer pools.
- All the VMs in a cloud service will have the same NAT IP address and the load balanced pool will also have the same NAT IP address.
- When you have decommissioned an SOI, it removes the load balancer pool entry (created at the network container level), but retains the load balancer pool details in BMC Cloud Lifecycle Management.
- When you disable a pool entry in BMC Cloud Lifecycle Management, it retains the load balancer pool entry with the Enabled value as FALSE (as shown in the figure below) and removes the endpoint from Microsoft Azure management portal.
- When you delete a pool entry in BMC Cloud Lifecycle Management, it removes the load balancer pool entry from BMC Cloud Lifecycle Management and also removes the endpoint from the Microsoft Azure management portal.
Comments
Log in or register to comment.