Maintenance windows
TDS team reserves regular maintenance window every Wednesday between 5-7 PM CET(winter time) or CEST (summer time). During that time frame planned changes are deployed to production environments. Service outages are usually 10-15 minutes, maximum 30 minutes. In case of expected longer outage all relevant users would be informed in advance by relevant channels.
All planned updates are communicated to users in advance. Following information channels are utilized for notifications about upcoming updates:
...
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. More complex changes can take more than 30m and this is highlighted in user communication.
Communication Scheme
All production changes are announced at least 5 business days in advance.
Most deployments are implemented within 15 minutes, however more complex changes can take 30 minutes or longer. Users are informed about all planned changes in advance, longer outages are highlighted in the communication.
Planned Changes
Planned changes deliver regular service upgrades and infrastructure changes.
Service | Communication channel and timeframe | Service | Communication in Tietoevry | Communication in External Customer Environment |
|---|---|---|---|---|
Jira and Confluence | Application banner Application banner Named stakeholders including SPOC are informed according to agreed channels.- 48h in advance | |||
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 (if preferred by SPOC) 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. | ||
- 48h in advance (not available for SeedDMS and Subversion) E-mail - 5 days in advance, addressed to TDS project owners and SaaS project admins (developers for Subversion) | ||||
Dedicated SaaS (SaaS applications dedicated to one or multiple TDS projects) | SPOC and named stakeholders are informed by agreed channels 5 days in advance Application banner 48 hours prior to change (if requested by SPOC) |
Regular schedule of maintenance windows Due to TDS operational reasons, regular schedule can be occasionally altered (e.g. longer outage outages are scheduled for weekend instead of Wednesday evening). 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 through the same communication channels as for planed changes, but the time between user communication and service outage/ change deployment is less than 5 daysshorter. Note that critical security vulnerabilities are often patched within 24 hours after CVE is published.
Servers
Related Pages
Virtual servers are dedicated to TDS projects and all maintenance is performed by project teams. In case of critical security vulnerabilities, TDS operations team patches these servers as soon as possible. Server admins (and named SPOC if applicable) are informed in advance via e-mail or chat.
Related Pages
Roadmap (best-effort development team plan) | Release Notes | Service description (Including Service Level Agreement) | Service Status | Roadmap (best-effort development team plan) | TDB - ?