Project

General

Profile

communication #99711

Server maintenance workflow for openSUSE Meet

Added by cdywan 23 days ago. Updated 22 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Jitsi/ Meet
Target version:
-
Start date:
2021-10-04
Due date:
% Done:

0%

Estimated time:

Description

Issues such as #94637 and #93859 are very difficult to address because there's no defined workflow. Changes can be made by several people and there's no requirement to document in e.g. a ticket what was done or go through smoke testing and revert.

I'd like to suggest that common procedures are defined, and if something needs to be done there's one or several people who can help work on a task. I'm thinking of these ones to begin with:

  • Host upgrade
  • Jitsi version upgrade
  • Smoke testing steps after any change
  • Ticket-based process for all changes

Related issues

Related to openSUSE admin - communication #94637: openSUSE Meet (Jitsi) disables video and screensharing to save bandwidthNew2021-06-24

Related to openSUSE admin - tickets #93859: openSUSE Meet (Jitsi) is borked after upgradeNew2021-06-10

History

#2 Updated by cdywan 23 days ago

  • Related to communication #94637: openSUSE Meet (Jitsi) disables video and screensharing to save bandwidth added

#3 Updated by cdywan 23 days ago

  • Related to tickets #93859: openSUSE Meet (Jitsi) is borked after upgrade added

#4 Updated by cdywan 23 days ago

  • Private changed from Yes to No

No need for this to be Private.

#5 Updated by cdywan 23 days ago

Also #98823 may be worth mentioning, which is an openQA test for Jitsi which could be used in the future to spot regressions in automated tests.

#6 Updated by lrupp 22 days ago

Agreed in general, but can I suggest to not document host information in a ticket, which will get lost (means: get lost in the minds of the admins)?

Under normal conditions, I would suggest to add the information about a machine in our Salt setup. As meet.o.o is currently not using Salt, we need to find another place. What about a page in our Admin-Wiki here?

#7 Updated by lrupp 22 days ago

  • Category set to Jitsi/ Meet

#8 Updated by cdywan 22 days ago

lrupp wrote:

As meet.o.o is currently not using Salt, we need to find another place. What about a page in our Admin-Wiki here?

Yeah, that sounds good to me. It should be as discoverable as possible.

Also available in: Atom PDF