Grout community call Thu Sept 10 11:00 UTC

[Robin Jarry]

Hi all,

Here is a quick summary of the meeting we had last Thursday:

Project Vision and Architectural Scope
======================================

Grout is a high-performance software data plane with an API rather than
a full-stack solution. User-facing features such as CLI, GUI, and
provisioning tools fall outside the core project scope. Control plane is
also deferred to external components as much as possible (e.g. FRR).

The integrated grcli tool remains dedicated to low-level interface
creation, while higher-level configuration should be handled by external
wrappers.

All participants agreed that the feature-set must remain focused and
that we must define clearly what grout is and what it is not.

The README file in the git repository will be reframed to better reflect
the project mission.

CI/CD and Hardware Infrastructure
=================================

We need more testing on bare metal. D-Lake plans to provide physical
hardware to support the project CI, moving beyond current GitHub-based
virtual machine limitations.

There will be explorations for white-box benchmarking using rte_graph
TSC-based statistics per node for quick and precise performance
regression detection.

Product Roadmap and Focus Areas
===============================

* Finalize integration with https://openperouter.github.io/
* IPv4 fragments reassembly
* MPLS data plane + FRR support
* End-user documentation
* Upgrade testing

NB: do not hesitate to fill in any details I might have missed.

Recurring meetings
==================

We decided to split discussions:

* 30 minutes technical / implementation / review meeting every Thursday
* 1 hour governance / steering every 3 months.

I will send meeting invites in a separate message.

Cheers.

-- 
Robin

# Do not dry clean.