Create a continuously updating test system

[lkiesow]

For users, it is hard to test the current state of the plugin. It would be great to be able to always have a public system for the community to run tests.

Best case, we have a test deployment for every pull request like we have with Opencast Editor, Opencast Studio or Tobira. For example, the editor has a live deployment and a deployment of every pull request with notifications posted at the pull request.

As an alternative or additional, we could do a daily resetting test system of the latest state of the branch master like we have with develop.opencast.org in Opencast. That leaves users to always easily test at least the merged patches.

Initial Test System

Osnabrück University can provide resources for this (compute, storage).

The setup should be designed to easily replace infrastructure (Ansible, Container, …) so we won't run into problems if we have to replace a machine in the future.

We can expand this later, but for the initial test system:

• We need a Stud.IP installation
  • This should be a recent Stud.IP. Latest release? Git? Not sure what makes the most sense, but we shouldn't need to manually update this.
  • There should be a basic course structure inserted into the fresh install
  • There should be several videos inserted into the installation
  • We need to include Coursware resources
  • We need a set of test users with different roles. Would be nice to document them on the login page like on the Opencast test servers.
  • We need to connect to an Opencast
• We need an Opencast installation
  • We can probably use the deployment scripts for the test servers
  • We need LTI configured
  • We need the Stud.IP user provider configured
  • We probably cannot incorporate this into Opencast's community test servers, can we?
  • We should track the latest state of Opencast's branch develop.

Extension: Add Room/Capture Agent

Let's ignore this for now, but keep this in mind for the future

It would be great to test scheduled recordings as well. For that, we should hook up a capture agent to Opencast and pretend that it is recording a specific room.

The work would be to:

• Set up a test capture agent using pyCA.
• Register capture agent/room with Stud.IP
• Automatically schedule a recording for a short time after the test system has been reset

Extension: Connect BigBlueButton

Let's ignore this for now, but keep this in mind for the future

It would also be great to check if the Meetings Plugin/BigBlueButton integration works. For this, we need to connect a BigBlueButton server and configure it to publish media to Opencast:

• Set up a BigBlueButton server
• Configure BigBlueButton Opencast integration
• Install and configure Meetings plugin

---

Does this make sense? Any other suggestions?

[alinastolzenburg]

@ssrahn @dennis531 das Testsystem (https://lms-demo-studip.vm2.elan.codes/index.php?again=yes) verfügt gerade nicht mehr über das OC Plugin (bzw. irgendein Plugin) kann jemand von euch da etwas machen ich glaube Till ist im Urlaub?

[ssrahn]

Da scheint es ein Problem bei der Installation gegeben zu haben:

Allerdings habe ich keine Zugriffsrechte auf die Datenbank und kann es deshalb auch nicht beheben.

[alinastolzenburg]

Da scheint es ein Problem bei der Installation gegeben zu haben:

Allerdings habe ich keine Zugriffsrechte auf die Datenbank und kann es deshalb auch nicht beheben.

ok danke fürs nachschauen. Weißt du wer Zugriffsrechte hat (außer Till)

[g550]

Leider funktioniert der Video-Upload im Testsystem immer noch nicht. Ich kann Videos zwar ohne Fehlermeldung hochladen und sehe dann die in #760 erwähnte unmittelbare Anzeige als "in Bearbeitung"; aber nach einer Weile verschwinden die gelben Zahnräder und das Video wird als "nicht verfügbar" angezeigt (Stand: 1h20m nach Upload eines 3-sekündigen Testvideos). @alinastolzenburg bekommt indes direkt beim Versuch des Hochladens eine Fehlermeldung.