Networking Internals on Oakestra

Overlay Network

Mon, 01 Jan 0001 00:00:00 +0000

Let’s first understand the different network abstraction layers within Oakestra, as well as the associated address space reservations, before we discuss with semantic addressing.

IPv4 Addressing

Mon, 01 Jan 0001 00:00:00 +0000

Oakestra uses the reserved private IPv4 subnet 10.0.0.0/8 for its service addressing.

The detailed network partition can be taken from the table below.

IPv6 Addressing

Mon, 01 Jan 0001 00:00:00 +0000

Oakestra makes use of the reserved private IPv6 subnet fc00::/7 for its service addressing and uses the following network split for IPv6 networking

Load Balancing

Mon, 01 Jan 0001 00:00:00 +0000

The load balancing in Oakestra consists of a multistep address conversion protocol using semantic addresses as part of an overlay network.

Proxy Conversion

Mon, 01 Jan 0001 00:00:00 +0000

In order to make the service layer networking functional, a worker-level tunnel-proxy is transparently instantiated as part of the Oakestra network component. The following picture is an example of what happens in a worker node based on the IPv4 implementation of the Network Manager component. Note that IPv4 and IPv6 work identically. For simplicity, we will stick to IPv4 addresses in this walkthrough.

MQTT Authentication

Mon, 01 Jan 0001 00:00:00 +0000

Intra-Cluster Communication

The above image shows how intra-cluster communication takes place. Nodes send application status and node health reports to the cluster-service-manager. The cluster-service-manager then appropriately propagates this information to other nodes and the root-service-manager. Since the nodes report sensitive information, such as IP Addresses, we highly recommend securing the MQTT channels.