Project

General

Profile

communication #99711

Server maintenance workflow for openSUSE Meet

Added by cdywan 4 months ago. Updated 13 days ago.

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

100%

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 bandwidthClosed2021-06-24

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

History

#2 Updated by cdywan 4 months ago

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

#3 Updated by cdywan 4 months ago

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

#4 Updated by cdywan 4 months ago

  • Private changed from Yes to No

No need for this to be Private.

#5 Updated by cdywan 4 months 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 4 months 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 4 months ago

  • Category set to Jitsi/ Meet

#8 Updated by cdywan 4 months 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.

#9 Updated by lrupp 13 days ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Hi there - and a Happy and Healthy 2022!

I'm currently closing old tickets which did not see much change.
If the main concern still exists and should be handled, please re-open by just replying to this Email.

Thanks in advance,
Lars

Also available in: Atom PDF