Triggers:

• T1: 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.
• T2: Changes of the infrastructure
  The operations team 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.
• T3: Regular updates of the infrastructure
  The operating team 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 owner 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 Owner approves T2 type of change, initiated by the SUNET NOC.
• CM 08: Based on the RfC, SUNET engineering plans the change and updates the ticket in SUNET JIRA.
• CM 09: Changes are deployed to the https://thiss.io/use 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. 
• CM 10: Smoke tests are performed using the SA monitoring. The deployment has to be monitored for at least 24 hours before 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: Smoke tests are performed using the SA monitoring. The deployment has to be monitored for at least 24 hours before 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 13: 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. 
• CM 14: Smoke tests are performed using the SA monitoring. The deployment has to be monitored for at least 24 hours before 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 15: Previous docker image is used to roll back to previous state. JIRA ticket is updated.
• CM 16: Smoke tests are performed using the SA monitoring. The deployment has to be monitored for T2 before 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.
• CM17: Update and close the JIRA ticket.  

RfC Template

Each RfC shall contain the following attributes:

• Service Name: InAcademia
• (NDN Service ID / Customer ID)?
• Change Type: Software / Infrastructure / Other
• Priority: Standard / Emergency
• Time schedule: Suggested time frame for the Change to be implemented
• Description: Summary of the Change
• Customers Affected: Customers affected by change
• Times for testing: T1, T2, T3