Skip to main content

'loadbalancer' interface protocol API library

Project description

loadbalancer Interface Protocol API Library

This library provides an API for requesting and providing load balancers or ingress endpoints from one charm to another. It can be used in either charms written in the newer Operator Framework or older charms still using the charms.reactive Framework.

Installation / Setup

Include this library as a dependency for your charm, either in requirements.txt for Operator Framework charms, or wheelhouse.txt for reactive charms:

loadbalancer_interface

Usage

Requesting Load Balancers

Requesting a load balancer from a provider is done via the LBProvider class. The general pattern for using the class is:

  • Wait for the provider to become available
  • Get a Request object via the get_request(name) method
  • Set the appropriate fields on the request object
  • Send the Request via the send_request(request) method
  • Wait for the Response to be provided (or updated)
  • Get the Response object via either the get_response(name) method or via the new_responses property
  • Confirm that the request was successful and use the provided LB's address
  • Acknowledge the Response via ack_response(response)

There are examples in the repo for how to do this in an operator charm or in a reactive charm.

Providing Load Balancers

Providing a load balancer to consumers is done via the LBConsumers class. The general pattern for using the class is:

  • Wait for new or updated requests to come in
  • Iterate over each request object in the new_requests property
  • Create a load balancer according to the request's fields
  • Set the appropriate fields on the request's response object
  • Send the request's response via the send_response(request) method

There are examples in the repo for how to do this in an operator charm or in a reactive charm.

API Reference

See the API docs for detailed reference on the API.

Test Charms

To ease testing of charms using this interface, this library provides test charms which can be used with a pytest_operator.OperatorTest based integration test to serve as a basic counterpart to the charm providing or requiring this interface.

To use the charms, simply mark your test class with the lb_charms mark. This will cause an lb_charms attribute to be injected into your test instance with attributes for each of the example charms available in the repo. (The attribute names will be the charm names with dashes replaced with underscores.) For example:

import pytest
from pytest_operator import OperatorTest

@pytest.mark.lb_charms
class MyCharmTest(OperatorTest):
    def test_build_and_deploy(self):
        my_charm = await self.build_charm(".")
        lb_provider = await self.build_charm(self.lb_charms.lb_provider)
        await self.model.deploy(my_charm)
        await self.model.deploy(lb_provider)
        await self.model.add_relation("my-charm", "lb-provider")

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

loadbalancer_interface-1.0.8.tar.gz (28.6 MB view details)

Uploaded Source

File details

Details for the file loadbalancer_interface-1.0.8.tar.gz.

File metadata

  • Download URL: loadbalancer_interface-1.0.8.tar.gz
  • Upload date:
  • Size: 28.6 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/51.1.2 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.2

File hashes

Hashes for loadbalancer_interface-1.0.8.tar.gz
Algorithm Hash digest
SHA256 78be92b552f8ace7eb94ff671299624aa8f96a685d3389b3275d5b9fee780524
MD5 6bd6a44f4ef9f5c699f45e023a907891
BLAKE2b-256 f740579d0f72b508e665b86697d6fc546d0a2521c966dc7c102c55481fd63b1b

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page