Investigate Jitsi Meet requirements
As it is based on XMPP, I think it only needs the videobridge and one other program. No idea, hence this issue.
(Someone offered to donate a considerable amount, in case we offer it for their Kosmos account.)
Notes (translate to Chef recipe):
Add meet domain to loopback host entry:
sudo sed -i 's/^127.0.1.1.*$/127.0.1.1 meet.kosmos.chat meet/g' /etc/hosts
Open firewall for meet traffic:
sudo ufw allow in 10000:20000/udp
Add nginx vhost with LE cert (find example config and adapt)
universeapt repo (required for deps):
Add the package repo
echo 'deb https://download.jitsi.org stable/' >> /etc/apt/sources.list.d/jitsi-stable.list wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | apt-key add -
Install package, but with flag that prevents adding nginx vhost (conflicts with existing 443 vhosts)
apt install --no-install-recommends jitsi-meet
Increase systemd limits for processes and open files. In
DefaultLimitNOFILE=65000 DefaultLimitNPROC=65000 DefaultTasksMax=65000
Also good to know: performance of the videobridge seems to be pretty good. When they introduced it last year, they said it would be orders of magnitude better than what they had before.
On a plain Xeon server [...] for about 20% CPU you will be able to run 1000+ video streams using an average of 550 Mbps!
We performed all tests on an unmodified Jitsi Meet installation, on a dedicated server. The server is running all the services needed by Jitsi Meet: a web-server (nginx), an XMPP server (prosody) and Jitsi Videobridge. The server machine is equipped with a quad-core Intel ® Xeon® E5-1620 v2 @ 3.70GHz CPU.
I checked again, and Andromeda is actually not too far from RAM limits, and also using considerable CPU resources already. So it would probably make more sense to throw Jitsi on the new Centaurus, which is going to be online soon.
From my first quick try, it looks like Jitsi Meet is requires Prosody as XMPP server. :/
Have to investigate further. The
jisti-meet package installs many different packages (incl. Prosody), which, in combination, make up the system.
Just found out it's possible to set up normal XMPP auth for Jitsi Meet room creation after all:
This is becoming a priority with a deadline now, so we can use an opensource tool for remote participants at the upcoming Kosmos Summit.
Ideally using existing Kosmos XMPP/LDAP accounts for permission to create rooms, of course. And probably even kosmos.chat MUC rooms for the chat in Jitsi.
If we want to record meetings/sessions, there's a Jitsi module called Jibri:
Jibri provides services for recording or streaming a Jitsi Meet conference.
It works by launching a Chrome instance rendered in a virtual framebuffer and capturing and encoding the output with ffmpeg. It is intended to be run on a separate machine (or a VM), with no other applications using the display or audio devices. Only one recording at a time is supported on a single jibri.
I looked into BigBlueButton this morning, because someone recommended it to me on fedi, after I asked about remote confs with whiteboards.
Summary of my findings, copied over from chat:
seems OK, but not sure it's better than jitsi meet
it doesn't come with any user accounts by default, but just an API
but there's a rails app for managing meetings and recordings, and it supports LDAP
so that could work
it's similar to zoom i guess, api-wise
but for kosmos chat and as a service, it would obviously be cool to just use plain xmpp for meeting management and permissions
much easier to do from hyperchannel then, because a user doesn't have direct API access
bigbluebutton shows a collaborative whiteboard by default, which is why it was recommended to me
so, to sum it up: i guess the easy and automatable recordings are the biggest benefit vs jitsi meet
and the whiteboard would handily solve that problem on the side
but not sure it's great as an overall kosmos service
Deleting a branch is permanent. It CANNOT be undone. Continue?