Start points:

• S1: New version of the Seamless Access software
  The development team publishes a new release version of the Seamless Access software, which was formerly approved according to the Release and Deployment process. Release notes of new versions of the software are available at https://thiss-js.readthedocs.io/en/latest/releasenotes.html 
• S2: Changes of the infrastructure
   SUNET NOC may initiate changes by themeself. This applies to major changes which have a potential impact on the service, and therefore can not be handled as a standard change.
• S3: Regular updates of the infrastructure
  SUNET NOC performs regular updates of the underlying infrastructure, operating system and dependent software. These minor changes may be deployed using an shortened change process. Since these changes are very trivial, they are considered as pre approved.

Tasks:

• CM 01: SA development prepares new release and updates the release manual.
• CM 02: SA development does software testing - such as functional and quality testing. 
• CM 03: The release version of the software is tagged in thiss repository at GitHub, and Release manual updated. 
• CM 04: SUNET engineering assists dev team by preparing the resources needed for deployment. 
• CM 05 : SA development, with assistance of SUNET engineering, deploys the release at https://staging.thiss.io
• CM 06: Service operational manager creates Request for Change (RfC Template) and submits it to the SUNET engineering by creating ticket at SUNET JIRA. This step is also considered to be implicit change approval. 
• CM 07: Service operational manager approves S2 type of change, initiated by the SUNET NOC.
• CM 08: Based on the RfC, SUNET engineering plans the change, the times of deployment  and updates the ticket in SUNET JIRA.  Changes with "Highest" priority are executed as soon as possible. All other changes are executed in next regular maintenance window.
• CM 09: Changes are deployed to the https://use.thiss.io according to the release manual using the defined release version from GitHub and, if applicable, docker images, puppet configs and other artefacts prepared during deployment at staging.  JIRA ticket is updated. Start/stop the maintenance window in status.io. 
• CM 10: Smoke tests are performed using the SA monitoring. The deployment has to be monitored for T1 proceeding with the change workflow. In case of any issues and if the change was initiated by Seamless Access the Service Manager will be notified. JIRA ticket is updated.
• CM 11: Previous docker image is used to roll back to previous state. JIRA ticket is updated.
• CM 12: Repeat CM10
• CM13: Service Operational Manager creates Request for Change (RfC Template) and submits it to the SUNET engineering by creating ticket at SUNET JIRA. This step is also considered to be implicit change approval. 
• CM 14: Based on the RfC, SUNET engineering plans the change, the times of deployment  and updates the ticket in SUNET JIRA.  Changes with "Highest" priority are executed as soon as possible. All other changes are executed in next regular maintenance window.
• CM 15: Changes are deployed to the https://service.seamlessaccess.org  according to the release manual using the defined release version from GitHub and, if applicable, docker images, puppet configs and other artefacts prepared during deployment at staging.  JIRA ticket is updated. Start/stop the maintenance window in status.io. 
• CM 16: Repeat CM10
• CM 17: Previous docker image is used to roll back to previous state. JIRA ticket is updated.
• CM 18: Repeat CM10
• CM19: Update and close the JIRA ticket.  

Instructions for RfC Template, Message for the slack channel and how to announce maintanence on status.io is described at Seamless Access Change Management Instructions