Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE OpenStack Cloud 8

13 Using Load Balancing as a Service with Orchestration Service Edit source

13.1 Orchestration Service Edit source

HPE Orchestration service, based on OpenStack Heat, enables the design and coordination of multiple composite cloud applications using templates.

You can use the Orchestration Service templates to describe and execute OpenStack API calls to create running cloud applications. The templates can be used to describe relationships and resources to help manage your cloud infrastructure and can also help you with the creation of resource types.

13.2 Orchestration Service support for LBaaS v2 Edit source

In SUSE OpenStack Cloud, the Orchestration Service provides support for LBaaS v2, which means users can create LBaaS v2 resources using Orchestration.

The OpenStack documentation for LBaaSv2 resource plugins is available at following locations.

13.3 Limitations Edit source

In order to avoid stack-create timeouts when using load balancers, it is recommended that no more than 100 load balancers be created at a time using stack-create loops. Larger numbers of load balancers could reach quotas and/or exhaust resources resulting in the stack create-timeout.

13.4 More Information Edit source

For more information on configuring and using the SUSE OpenStack Cloud Load Balancing as a Service, see: Section 9.3.8, “Configuring Load Balancing as a Service (LBaaS)” and Chapter 12, Using Load Balancing as a Service (LBaaS).

For more information on the neutron command-line interface (CLI) and load balancing, see the OpenStack networking command-line client reference: http://docs.openstack.org/cli-reference/content/neutronclient_commands.html

For more information on Heat see: http://docs.openstack.org/developer/heat

Print this page