I hereby claim:
- I am cmeiklejohn on github.
- I am cmeiklejohn (https://keybase.io/cmeiklejohn) on keybase.
- I have a public key ASAbjNbPtSzfJWtdZBFbQD4LnTdhOB1PJ1UA-bGk6l4FHAo
To claim this, I am signing this object:
def test_vc_diagram(): | |
clock_a = VectorClock() | |
clock_b = VectorClock() | |
clock_c = VectorClock() |
#!/usr/bin/python3 | |
import copy | |
def test_vector_clock_create(): | |
assert VectorClock() | |
def test_vector_clock_value(): | |
clock = VectorClock() | |
assert clock.value("a") == 0 |
I hereby claim:
To claim this, I am signing this object:
version: "3" | |
services: | |
mayan-edms-postgres: | |
image: | |
ports: | |
- | |
restart: always | |
volumes: | |
- | |
environment: |
...
We start by creating a gen_server for the direct mail protocol implementation. This implementation will support two calls broadcast
, for sending a message, and update
, for updating the membership received from the Partisan system for when view changes occur. For state at each node, we'll track the currently known membership, so we don't have to look it up every time we want to make a broadcast.
%% API
In our case, we're looking at adding another membership strategy to Partisan. The membership strategy we're looking to add is a superset of one of the existing strategies (HiScamp is a superset of Scamp functionality.)
Each membership strategy in partisan uses a well defined interface -- figure out how this interacts with the rest of the system and how the existing strategy (Scamp, in this case) operates using this API.
kube running for unir-567495c6d5-zmtmf |
kube running for unir-567495c6d5-r2pj8 |
kube running for unir-567495c6d5-5mq7d |
kube running for unir-567495c6d5-2l98t |