...
- 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 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 Changes with "StandardHighest" priority are executed as soon as possible. All other changes are executed in next regular maintenance window. Changes with "Emergency" priority are executed as soon as possible.
- 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 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
- 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: Repeat CM10
- CM 15: Previous docker image is used to roll back to previous state. JIRA ticket is updated.
- CM 16: Repeat CM10
- CM17: Update and close the JIRA ticket.
RfC Template
Each RfC shall contain the is JIRA ticket raised in SUNET JIRA with following attributes:
- Service NameProject: InAcademia
- (NDN Service ID / Customer ID)? Change Type:
- SeamlessAccess(SA)
- Issue Type: Change
- Summary: Change Type [Software / Infrastructure / Other
- Standard], and summary of the change
- Description:
- Describe in more detail what the change is about.
- Summary of the change.
- Suggest
- Priority: Standard / Emergency Time schedule: Suggested
- time frame for the Change to be implemented. Define T1 and T2
- Description: Summary of the Change Customers Affected: Customers affected by change
- .
- Describe which customers the change is affecting and wether it is potentially disruptive.
- Priority: Highest for emergency/security changes, Medium for software and infrastructure changes, Lowest for standard changes