Charm Interface - HA Cluster
Go to file
gnuoy 73d507e04a Revert "Add OPS framework interface"
This reverts commit 1730dfe3fd.

Reason for revert: Causing issues with reactive charms

Change-Id: Ib529b973ba8856348b0bd7383d403ceb28f235d5
2021-09-10 08:07:57 +00:00
interface_hacluster Revert "Add OPS framework interface" 2021-09-10 08:07:57 +00:00
unit_tests Revert "Add OPS framework interface" 2021-09-10 08:07:57 +00:00
.gitignore Migrate from testr to stestr 2021-02-10 11:18:06 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:48:31 +00:00
.stestr.conf Migrate from testr to stestr 2021-02-10 11:18:06 +00:00
.zuul.yaml Switch to Ussuri jobs 2019-10-31 17:51:43 +08:00
README.md Add .gitreview, update tox.ini, update readme. 2016-07-06 12:56:24 +00:00
copyright First commit of the proposed hacluster interface. 2016-01-05 21:22:27 -07:00
interface.yaml Revert "Add OPS framework interface" 2021-09-10 08:07:57 +00:00
requires.py Move common requires code 2021-08-26 12:03:41 +00:00
test-requirements.txt Revert "Add OPS framework interface" 2021-09-10 08:07:57 +00:00
tox.ini Move common requires code 2021-08-26 12:03:41 +00:00

README.md

Overview

This interface handles the communication with the hacluster subordinate charm using the ha interface protocol.

Usage

Requires

The interface layer will set the following reactive states, as appropriate:

  • {relation_name}.connected The relation is established and ready for the local charm to configure the hacluster subordinate charm. The configuration of the resources to manage for the hacluster charm can be managed via one of the following methods:

    • manage_resources method
    • bind_on method

    Configuration of the managed resources within the hacluster can be managed by passing common.CRM object definitions to the manage_resources method.

  • {relation_name}.available The hacluster is up and ready.

For example:

from charms.reactive import when, when_not
from charms.reactive import set_state, remove_state

from relations.hacluster.common import CRM


@when('ha.connected')
def cluster_connected(hacluster):

    resources = CRM()
    resources.primitive('res_vip', 'ocf:IPAddr2',
                        params='ip=10.0.3.100 nic=eth0',
                        op='monitor interval="10s"')
    resources.clone('cl_res_vip', 'res_vip')

    hacluster.bind_on(iface='eth0', mcastport=4430)
    hacluster.manage_resources(resources)

Additionally, for more code clarity a custom object implements the interface defined in common.ResourceDescriptor can be used to simplify the code for reuse.

For example:

import ipaddress

from relation.hacluster.common import CRM
from relation.hacluster.common import ResourceDescriptor

class VirtualIP(ResourceDescriptor):
    def __init__(self, vip, nic='eth0'):
        self.vip = vip
        self.nic = 'eth0'

    def configure_resource(self, crm):
        ipaddr = ipaddress.ip_address(self.vip)
        if isinstance(ipaddr, ipaddress.IPv4Address):
            res_type = 'ocf:heartbeat:IPAddr2'
            res_parms = 'ip={ip} nic={nic}'.format(ip=self.vip,
                                                   nic=self.nic)
        else:
            res_type = 'ocf:heartbeat:IPv6addr'
            res_params = 'ipv6addr={ip} nic={nic}'.format(ip=self.vip,
                                                          nic=self.nic)

        crm.primitive('res_vip', res_type, params=res_params,
                      op='monitor interval="10s"')
        crm.clone('cl_res_vip', 'res_vip')

Once the VirtualIP class above has been defined in charm code, it can make the code a bit cleaner. The example above can thusly be written as:

@when('ha.connected')
def cluster_connected(hacluster):
    resources = CRM()
    resources.add(VirtualIP('10.0.3.100'))

    hacluster.bind_on(iface='eth0', mcastport=4430)
    hacluster.manage_resources(resources)