@@ -196,6 +196,15 @@ where **<internal_subnet_ID>** is an ID of internal subnet used by your instance
For more info, please refer to [https://docs.openstack.org/octavia/train/user/guides/basic-cookbook.html#basic-lb-with-hm-and-fip](https://docs.openstack.org/octavia/train/user/guides/basic-cookbook.html#basic-lb-with-hm-and-fip).
Sometimes it can happen that Load Balancer is working but connection is not working because it is not added into security groups. To solve this you
have to add the Load Balancer ingress traffic IP rule.
</div>
LBaaS (Load Balancer as a service) provides user with load balancing service, that can be fully managed via OpenStack API (some basic tasks are supported by GUI). Core benefits:
* creation and management of load balancer resources can be easily automatized via API, or existing tools like Ansible or Terraform
* applications can be easily scaled by starting up more OpenStack instances and registering them into the load balancer
...
...
@@ -205,6 +214,8 @@ LBaaS (Load Balancer as a service) provides user with load balancing service, th
Official documentation for LBaaS (Octavia) service - https://docs.openstack.org/octavia/latest/user/index.html