---
# System prepended metadata

title: 'Maintainers Meeting, 15th February 2023'
tags: [maintainers]

---

---
title: "Maintainers Meeting, 15th February 2023"
tags: maintainers
datetime: 2023-02-15T16:00UTC
location: Online, Discord, the `#voice-meeting` voice channel
teams:
- maintainers
participants:
- Nitinder (NM)
- Daniel (DM)
- Simon (SZ)
---

## 📋 Agenda
- ToDos from last meeting
    - [ ] NM: Oakestra open thesis topics compilation
    - [x] SZ: Understanding node_manager and netmanager for IPv6 translation
    - [x] DM: Make the repo public.
    - [ ] DM: Integration with the backend -- next week
    - [x] NM: **[Immediate]** Create a FrontendWG. Invite Daniel and Michael.
    - [ ] SZ: Finish the IPv4 to IPv6 translation of the `netmanager`
    - [x] SZ: Create a first version of the oakestra network partitioning in IPv6

- Next meeting

## 📢 Discussions

NM: The first frontendWG meeting will take place on Feb 22 at 17:30 on voice-meeting channel

*moved GB open tasks to next week since he is on vacation*

DM: Merged refactoring in main. We should be up to date.

NM: Dashboard repo is public!

DM: We need to write more GitHub issues.

DM: We also need to change the account managements. Make it more like AWS. i.e. appln belongs to an account and several users can work with an account.

DM: Advntage -  multiple folks can work with an account. Disadvantage - Might need to change some logic and SLA.

NM: Pin this discussion and move to next week. DM to prepare a list of changes required and beneficial usecase.

DM: Integration with backend requires some changes from backend

SZ: Working `net-manager` implementation. Now working on MongoDB where subnets are being handled. Currently implementing MongoDB schema for MQTT fetch.

SZ: Looked into how serviceIPs are handed out 

`fc00::/7` ->                    oakestra network
`fc00::/64` ->                   oakestra cluster subnetworks
    -> 2^58 - 1              possible clusters (too much?)
`fdff:ffff:ffff:ffff::/64` ->     service IP subnet
    -> 2^64                  possible service IPs

Example:
new cluster C:
    `fc00::1:0000:0000:0000:0000/64` ->     cluster subnet
new Service A in Cluster C
    `fdff::ffff:ffff:ffff::1/64` ->         ServiceIP
Service A with 16 Instances and 16 balancing strategies -> 16 load balanced IPs
    `fc00::1:0000:0000:0000:00f[1-f]` -> load balanced IPs
    `fc00::1:0000:0000:0000:00[0-e][1-f]` -> InstanceIPs -> 240 InstanceIPs

NM: less clusters, more Instances in general

## 🛠️ TODOs
GB: Maintainer's discussion on versioning

GB: Create discussion thread about testing coverage automations -> when do we block PR? what automation to check it?

DM: Discussion on update to account creation.

DM: Integration with the backend -- cleanup

SZ: Formalize in a document

SZ: More work on MongoDB. 

