...
- Jira and Confluence these servics are used mostly via GUI, therefore all active users are effectively informed mainly by banners:
- users are informed by notification banner in affected service
- key stakeholders (or SPOC) are informed by agreed channels
- Artifactory, Bitbucket, Gitlab, Subversion, SeedDMS - these services are mostly used via some sorts of clients or integrations (CI/CD integrations, git/subversion clients, ...), therefore following channels are used:
- users are informed by notification banner in affected service
- relevant users are informed by email
- key stakeholders (or SPOC) are informed by agreed channels
- In case of project dedicated services
- users are informed by notification banner in affected service
- key stakeholders (or SPOC) are informed by agreed channels
- Servers - each project is always responsible for its own servers, however TDS team is usually performing security patching to mitigate security issues without delays to avoid any incidents
- in case of expected downtime project owners/admins are informed by email (or chat platform when applicable)
- key stakeholders (or SPOC) are informed by agreed channels
Indication of upcoming updates is available on Roadmap page.
TDS team reserves the right to do planned upgrades in other time-slot by informing users 5 days in advance.
...
TDS team reserves the right to take needed urgent actions to deploy changes, patches, workaround and other corrective actions in case of critical security issues to prevent security incidents. Key stakeholders (or SPOC) are informed by agreed channels about ongoing activities. During such emergency activities some services might be affected by temporary outages. The TDS team communicates the emergency changes to the Customer as soon as possible (banner, mail, or chat).
...
TDS Outage and Upgrade Communication
TDS maintenance windows are scheduled every Wednesday 5-7 PM CET. Operations team deploys service upgrades, patches, or changes. Typical service outage takes less than 15 minutes, major changes are in most cases deployed in less than 30 minutes.
Communication Scheme
All production changes are announced at least 5 business days in advance.
Service | Communication in Tietoevry | Communication in External Customer Environment |
|---|---|---|
Shared Jira and Confluence | Application banner | Application banner Named stakeholders including SPOC are informed according to agreed channels. |
Artifactory, Bitbucket, Gitlab, Subversion, SeedDMS | Application banner Relevant users are informed by email (This is not clear and needs to be more specific.) | Application banner Named stakeholders including SPOC are informed according to agreed channels. |
Services dedicated to TDS Project | Application banner All project users are informed via e-mail | Application banner Named stakeholders including SPOC are informed according to agreed channels. |
Servers | Project owners and server admins are informed by email (or chat platform when applicable) | Named stakeholders (or SPOC) are informed by agreed channels. |
Due to TDS operational reasons, regular schedule can be occasionally altered (e.g. longer outage scheduled for weekend). All irregular changes are announced according to Communication Scheme above.
Emergency Changes
Emergency changes (typically urgent security patches) are deployed as soon as possible, preferably after 5 PM regardless of maintenance windows. Users are informed according to Communication Scheme above, however the time between user communication and service outage/change is less than 5 days. Note that critical security vulnerabilities are often patched within 24 hours after CVE is published.
Related Pages
Roadmap - Indication of upcoming updates (best-effort development team plan).
Release Notes - TDS service release notes
Service description and Service Level Agreement
TDB - ?