Maintenance windows

All planned updates are communicated to users in advance. Following information channels are utilized for notifications about upcoming updates:

Jira and Confluence these services are used mostly via GUI, therefore all active users are effectively informed mainly by banners:
- Application banner 48 hours prior to change
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:
- Application banner 48 hours prior to change (not available for SeedDMS and Subversion)
- Mail 5 days - SaaS project admins and TDS project owners (developers for Subversion)
In case of project dedicated services (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)

Emergency changes

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).

Servers - each project is always responsible for its own servers, however TDS team is usually performing security patching to mitigate critical security issues without delays to avoid any incidents
- (unless customer implemented the security patch within given timeframe)
- 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

TDS Outage and Upgrade Communication

TDS maintenance windows are scheduled every Wednesday 5-7 PM CET. Operations team deploys service upgrades, patches, or changes. 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

Jira and Confluence

Application banner - 48h in advance

Artifactory, Bitbucket, Gitlab, Subversion, SeedDMS

Application banner - 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 can be occasionally altered (e.g. longer outages are scheduled for weekend instead of Wednesday evening).

Emergency Changes

Emergency changes (typically urgent security patches) are deployed as soon as possible. Users are informed through the same communication channels as for planed changes, but the time between user communication and change deployment is shorter. Note that critical security vulnerabilities are often patched within 24 hours after CVE is published.

Servers

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

Release Notes | Service description (Including Service Level Agreement) | Service Status | Roadmap (best-effort development team plan) | TDB - ?