Page History

...

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: The dev team updates the release manual according to the SA development prepares new release and deploys it as described (in the manual) to the Test Environment. Engineering team assists in this process in order to prepare the deployment configs and resources. updates the release manual.
• CM 02: Functional and quality tests are performed by the development team.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 deployed in the staging environment. The release is announced to early adopters for testing, and after given amount of time elapsed if no reported issues the release version is considered a release candidate and development team informs service owner published in the OPS wiki., 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 and submits it to the SUNET engineering by creating ticket at SUNET JIRA. CM 04: A Request for Change is created and submitted to the NDN support either via email or JIRA by the IA Service Manager (- RfC Template). 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 08CM 05: Based on the RfC, SUNET engineering plannes the change is planned and details are published in JIRA by the NDN supportand updates the ticket in SUNET JIRA.

• CM 06: The IA Service Manager has to approve each change (via GitHub or email) before it will be processed by NDN. Approved (major) changes may be announced to the customers.
• CM 07: Changes are deployed to the test server according to the release cookbook using the defined release version from DockerHub.
• CM 08: Smoke tests are performed using the IA Test Tool. The test server has to be monitored for at least 24 hours before proceeding with the change workflow. During this time the development team may use the service for manual tests. In case of any issues and if the change was initiated by InAcademia the IA Service Manager will be notified.
• CM 09: In case of a major change, a snapshot of the current VM state is created and stored for backup.
• CM 10: The change is fully deployed firstly to all TIER2 nodes and monitored during a probation period no shorter than one hour and no longer than 6 hours.
• CM 11: If functional errors are experienced on TIER2 nodes these nodes will be rollbacked to previous software versions. No deployment on TIER1 will occur. Change workflow will jump to point CM 14.
• CM 12: The change will be deployed on TIER1 nodes. The server has to be monitored for at least 24 hours before proceeding with the change workflow.
• CM 13: If the change causes any issues during the monitoring period a rollback will be performed (e.g. revert data, re-deploy the former InAcademia version or using a snapshot available).
• CM 14: The change created in JIRA will be updated or closed.