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

## 📋 Agenda
- ToDos from last meeting
- [ ] NM: Oakestra open thesis topics compilation
- [ ] SZ: Understanding node_manager and netmanager for IPv6 translation
- [ ] DM: Integration with the backend
- [x] DM: Check service creation on HPI and in API browser
- [ ] DM: Make the repo public.
- [ ] NM: Create a FrontendWG. Invite Daniel and Michael. First meeting in early.
- [x] GB: open a discussion in GitHub discussion about 0.major.minor versioning
- [ ] GB: Create discussion thread about testing coverage (And the milestone)

- Next meeting

## 📢 Discussions

DM: Service creation with HPI cluster -> worked

DM: next week, work more on the integration with the backend.

DM: to make the repo poublic we have to wait until its done

NM: demo of the current state of the frontend? Code-wise, what changed?

DM: mainly refactoring, redux store, that's why a lot of files. Trying out lot of functions to check correct response from backend. Will try to emrge next week. Better to avoid collisions before merging the frontend.

NM: Michael should not work ont he forntend next week.

NM: One new topic -> we should summarize the open things that we can re-structure as thesis topics. The research/implementation oriented stuff. If you have ideas, please let me know.

NM: current topics, orchestration with k8s, marketplace for oeachestra. This might be improtant for Daniel because some features can be shipped like plugins. If you have something in ming add content (over Discord).

DM: Helo woud be good. E.g., K8s integration done from the student in the frontend as well.

NM: Michael should be integrated into our meetings because he'll work on the frontend as well.

NM: I'll get the frontend working group started to offload some os Daniel's work there.

NM: We had a meeting with an industry (Omax). They have machines on the floor that need to coordinate. They currently interact with MQTT. Their requirements can be fulfilled by Okaestra. They need partitions with clusters. They have been looking on K8s stuff but they are still figuring out stuff. Nothing concrete, but first there is an NDA and further discussion are required with them. We might need to deploy stuff on their machines and see how it goes.

SZ ipv4 to ipv6 translation on its way.

SZ: If you take docker compose file, how to patch new image instead of the pre-compiled ones?

SZ: Replacing the images we cna deploy services in dual stack.

SZ: Started with NetManager, the gateway can support ipv6 stack.

GB: NodeManager mostly uses MQTT, so IPv6 things should be similar to NetManager.

GB: Each component has a docker file which can be used to build the image. You can push it or substitute the link to image name locally.

GB: Images are built automatically from main branch. Works with a pull request. You can use custom tags.

SZ: You are using `water` for IPv4. Should I reintegrate it for IPv6?

GB: Only used for TUN interface.

SZ: It works well. *whew*

NM: which components are complete?

SZ: NodeManager untouched, NetManager on tis way.

NM: from clsuter orch?

SZ: Clsuter orch fully migrated in dual stack. Neet to check the IP lease.

SZ: So far we don't check boundaries for the net?

GB: We don't

SZ: need to check on that.

SZ: 10.x.x.x subnetwork. Shall we change it?

GB: 10.30.x.x might be restrictive. Ipv6 would give us larger addressing space.

NM: need to talk about this in focus group.

GB: 10.30.x.x. gets serviceIPs. It limits the number of services. IPv6 must have more addressing space.

GB: added the workflow for developed images. currently testing how it works. If it works well, then will make it work on develop branch

GB: "open a discussion in GitHub discussion about 0.major.minor versioning" --> Done. Link here: https://github.com/oakestra/oakestra/discussions/142

GB: "Create discussion thread about testing coverage (And the milestone" --> Might require discussion on this.

NM: Next maintainer's meeting -> discussion about versioning thread created.

## 🛠️ TODOs

DM: Integration with the backend -- next week

NM: **[Immediate]** Create a FrontendWG. Invite Daniel and Michael.

GB: Maintainer's discussion on versioning

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

SZ: Finish the IPv4 to IPv6 translation of the `netmanager`