Server maintenance workflow for openSUSE Meet
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
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?