The above plan has been developed somewhat. Here is the first draft of copy for the plan that @Graham requested to unlock any further labour hours from me and Nick. This is currently Work in Progress but I am sharing early for community feedback and knowledge sharing.
We have a plan to reunite our users with their old recordings
ColloCall recommended following steps:
-
Drop the new Greenlight 3
-
Setup a Greenlight 2
-
Import all data (database, recordings)
-
Migrate to Greenlight 3
We responded to CollCall expanding this plan with additional details. We’ll share that with you now:
-
We want to keep the current live de.meet.coop hosted by ColloCall as-is. This is what our customers are currently using.
-
We have two old servers that hold recordings.
-
We can provide the entire
/var/bigbluebutton/directory for both of those servers. -
The old de.meet.coop
/var/bigbluebutton/directory is 834 GB. -
The old ca.meet.coop
/var/bigbluebutton/directory is 133 GB. -
We have a central keycloak server for SSO that we will continue to manage and host ourselves.
-
We have full control over meet.coop DNS records.
Based on what we know, we only wish to proceed with the second and third actions in the ColloCall recommendations above:
-
Set up a Greenlight 2 server (on new hosting)
-
Import all data (recordings, data files, Keycloak)
Regarding the fourth step ColloCall recommended, we won’t need to migrate the to Greenlight 3 as we will spin these recordings servers down after a few months of meet.coop users being able to access their recordings.
However, because we have two old servers, we believe it will be easier for meet.coop users if ColloCall spin up two Greenlight 2.7.x servers so that the users can access a simulacrum of the old setup.
We think we should name the servers:
Based on our research, we believe that the previous Greenlight 2 servers were migrated off of separate databases in 2022. None of the database instances we’ve found have been modified since then, and do not appear functional. All of the BigBlueButton servers appear to store data in trees of structured text files (XML, JSON, that sort of thing).
Therefore, our understanding is that the meet.coop Keycloak authentication server has superseded any SQL database for either Greenlight or BigBlueButton and therefore the /var/bigbluebutton directory will be sufficient to mimic the old servers.
If everything goes as we hope, we will have a situation where the meet.coop users will be able to log in to both recordings.de.meet.coop and recordings.ca.meet.coop with their existing Keycloak accounts, in order to access and download their recordings. Then after a period time (3 months), we spin down recordings.de.meet.coop and recordings.ca.meet.coop.
We are seeking feedback from ColloCall about the feasibility of this plan and how much it’s going to cost meet.coop.