...
For the purposes of this document, 'production service' means any service or tool listed in 'Production' column in Domain name conventions but also any other component of Up2U platform that is intended to be accessed by external users (which is currently, for instance, Moodle pedagogy-test platforminstance together with its backend-components).
The pilot coordinator is Michał Zimniewicz, PSNC (or, in his absence, Allan Third, OU).
The procedures:
- Service and tool owners (WP3/WP4) report all planned downtimes of production services
I would also see a short written procedure to have it clearly announced to all partners. E.g. that we report all downtimes of production services to WP7 leader in advance, maybe for test services too if a break is expected to last at least several hours, what is the suggested time of day for downtimes if any, etc. I can do this.
- Maintenance window should be decided and announced (e.g., to wp-all).
- Notification on the Moodle front page should be visible.
...
- to the pilot coordinator. Other maintenance actions, even if they do not cause downtimes, should be reported too.
- The maintenance window must be properly scheduled according to planned pilot activities (WP5/WP7).
- The pilot coordinator announces about the maintenance window to the WP7 mailing list (and other specific people, if relevant).
- In cases of longer or more serious downtimes
- a notification to the WP7 mailing list might be sent after the maintenance job is finished,
- a notification in the Wordpress site (possibly at https://up2university.eu/up2universe/) might be published (the pilot coordinator → WP2 leader).