Charm Interface - Magpie peer relation
Go to file
Andrew McLeod 1ad984a010 renamed to magpie 2016-09-29 22:10:19 +02:00
README.md renamed to magpie 2016-09-29 22:10:19 +02:00
copyright First working implementation 2016-01-28 12:19:47 +02:00
interface.yaml renamed to magpie 2016-09-29 22:10:19 +02:00
peers.py renamed to magpie 2016-09-29 22:10:19 +02:00

README.md

Overview

This interface layer handles the communication among Magpie peers.

Usage

Peers

This interface allows the peers of the Magpie deployment to be aware of each other. This interface layer will set the following states, as appropriate:

  • {relation_name}.joined A new peer in the Magpie service has joined. The Magpie charm should call get_nodes() to get a list of tuples with unit ids and IP addresses for peer members.

    • When a unit joins the set of peers, the interface ensures there is no {relation_name}.departed state set in the conversation.

    • A call to dismiss_joined() will remove the joined state in the peer conversation so this charm can react to subsequent peers joining.

  • {relation_name}.departed A peer in the Magpie service has departed. The Magpie charm should call get_nodes() to get a list of tuples with unit ids and IP addresses for remaining peer members.

    • When a unit leaves the set of peers, the interface ensures there is no {relation_name}.joined state set in the conversation.

    • A call to dismiss_departed() will remove the departed state in the peer conversation so this charm can react to subsequent peers departing.

For example, let's say that a peer is added to the Magpie service deployment. The Magpie charm should handle the new peer like this:

@when('magpie.joined')
def check_peers(magpie):
    nodes = magpie.get_nodes()
    # do stuff with nodes

Contact Information