search

numerique-gouv / meet

MIT License
1 stars 0 forks source link

Deploy our own STUN and TURN server #8

Open lebaudantoine opened 1 week ago

lebaudantoine commented 1 week ago

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe. We should not use any American-owned cloud tool or services.

According to @rouja, LiveKit Helm by default relies on Google cloud infrastructure. I found few references of AWS and Google running grep on their livekit/livekit-helm repository.

Also, the livekit repo itself mention using Google by default in its server config (cf. here)

Describe the solution you'd like Deploy our own TURN and STUN servers.

Drawbacks:

Describe alternatives you've considered Using Google infrastructure is acceptable in short term, to deploy our staging environment.

Discovery, Documentation, Adoption, Migration Strategy WIP - define TURN and STUN servers.

lebaudantoine commented 1 week ago

@rouja will be responsible for deploying our own instances of STUN and TURN servers on a dedicated VM, using tools such as Ansible and Terraform.

For the MVP, all environments will utilize a single LiveKit server instance provided by Indie Hoster, accessible at livekit.beta.numerique.gouv.fr. This instance currently runs on Google infrastructure but will transition to servers deployed by @rouja when they are ready.

Why use a single instance of the LiveKit server? We aim to load test the LiveKit server and stress it to study its behavior and performance under scaling conditions.