---
# System prepended metadata

title: 'Networking WG, 9th February 2023'
tags: [' oakestra', networking]

---

---
title: "Networking WG, 9th February 2023"
tags: networking, oakestra
datetime: 2023-02-09T11:00UTC
location: Online, Discord, the `#voice-meeting` voice channel
teams:
- networkingWG
participants:
- Giovanni (GB)
- Nitinder (NM)
- Simon (SZ)
---

## 📋 Agenda

- IPv4 to IPv6 load balancing
- subnetwork choice 10.30.x.x

## 📢 Discussions

SZ: What was the reason of the 10.30.x.x was? How is it going to change in the future. How is that going to be implemented in IPv6?

GB: The subnet is defining serviceIPs. Understand if the IP address is semantic or not? If the IP belongs to subnet, then we know that we have to fetch the metadata. Also designed to limit semantic addresssing to a few addresses. 

GB: 10.30.x.x is arbitrary choice. Can be changed to anything we fancy

SZ: Gateway IP is also an arbitrary choice?

GB: Yes

GB: We also have *namespace addresses* which are from a subnetwork. Has 64 addresses but can be updated. These are recycled when we undeploy the applications.

GB: *InstanceIPs* are part of semantic IPs and identify instances. Needed to map instances when they migrate to other nodes.

GB: *serviceIPs* refer to all replicas of a service, can have load balancing conotations. `10.30.x.x` will affect serviceIP and instanceIPs.

GB: With IPv6, can we encode balancing strategy inside the address?

SZ: Is it okay if they are all in same subnet?

GB: Yes.

NM: Comment on encoding: how does it scales when we increase the amount of balanced addresses? If we insert new strategies what happens? We don't want to break the design. 

SZ: For now fc00::/7 <-> 10.0.0.0/8 is used in oakestra.

SZ: Number of IPs per service: (# of load balancing strats + InstanceIP) * Instances

GB: 1 IP for each instance, 1 for each balancing policy. For each service, there are fixed amount of balanced addresses. Increasiong amount of instances we only increase instanceIPs. But with increasing services we increase both balanced addresses and service addresses.

SZ: deployment of a service: 1 service = 10 instances => 10 instanceIPs + `n` load balanced addresses (n = num of load balancing strats)

![](https://i.imgur.com/98A1OQW.png)

GB: In Ipv4, with two balancing polices, the IP addresses get depleted cloise to 5000 services. We need to take something similar into account in Ipv6 since with IPv4 this limits public deployments of Oakestra.

GB: [*Posted presentation in `net-manager` channel in Discord. It shows the Ipv4 schema which can be helpful.*].
    
## 🛠️ TODOs

SZ: Break down an addressing scheme for IPv6.

NM: Discuss about the proxy gateway solutions when cluster is within a private n/w