# Platform Deployment
The workflow below explains the step-by-step process for deployment of the ABB Ability™ Platform by the Ability Operations Team.
Note: These steps are only for new deployments. The workflow for the upgrading of an existing deployment to a new version or updating with hot fixes are part of a separate process explained here.
# Deployment Steps
# 1. Approved iProcess Ticket from BL Assigned to an Operations Engineer
The first step towards initiating a new deployment is the assignment of an iProcess ticket to the operations engineer.
- The workflow for iProcess can be found here
# 2. iProcess Ticket Assigned
Once the ticket is assigned, the operations engineer verifies the details.
INTERNAL STEPS
All steps listed below this break are internal steps taken by the ABB Ability™ Platform Operations Team. These are listed for transparency purposes.
# 3. Create a VSTS Task for Deployment
The operations engineer creates a VSTS task for deployment.
# 4. Pre-Deployment Checklist
All the pre-deployment entries are to be filled by the operations engineer or assigned as mentioned in the checklist. The details for each entry can be found in the comments against each entry in the checklist. Checklist can be found here.
All Inputs Available?
YES - The operations engineer creates the environment file for deployment and sends it out for peer review.
NO [Request Clarification] - If there is missing information, the operations engineer works with the operation lead and BL to gather information.
# 5. Send for Peer Review
After successful validation of inputs, the operations engineer creates an environment file for deployment and sends notification checks in the file to the feature branch in VSTS. Then the operations engineer sends the file out for peer review to another operations team member.
# 6. Peer Reviews the Checklist and Environment File
The operations team member verifies the environment file against the checklist and approves or rejects it (with a comment if any modification is required).
# 7. Peer Updates the Comments in Deployment Task
Peer updates the comments in the deployment tasks and assigns it back to the deployment engineer.
# 8. Operations Engineer Creates a Pull Request in VSTS and Assigns to Peer
After the verification of the environment file, the operations engineer creates the pull request and assigns it to another operations team member for approval of the pull request.
# 9. Peer Reviews the Pull Request and Provides Comments
The operations team member verifies the pull request and approves or rejects it (with a comment if any modification is required).
Note: If the peer reviewer rejects the request, then steps 3 through 8 should be repeated unless the request is approved by peers.
# 10. Peer Approves the Pull Request and Deployment Process Begins
After the approval above, the deployment process starts.
<> (The deployment process for specific version are provided in the link below:)
# 11. Verify Deployment Log and Enable Synthetic Transaction
After successful deployment, the operations engineer verifies the deployment log and enables the synthetic transaction. <!--
# (The process for enabling synthetic transactions are mentioned
After enabling the synthetic transaction, the oherehereperations engineer should wait for 30 minutes to verify the test results.
# 12. Issue Found
YES - Verify the issue and then create a bug. Work towards resolution.
NO - Continue to the next step.
# 13. Start Post-Deployment Verification and Fill the Post-Deployment Checklist
The operations engineer performs the post-deployment verification and will fill the post-deployment entries in the checklist with all the required details.
# 14. Send for Post-Deployment Review by Assigning VSTS Task
The operations engineer validates the entries and will send a notification to one of the team members for peer review with a checklist to be filled via VSTS task.
# 15. Peer Reviews the Tasks and Verifies the Checklist
The peer review is done by another operations team member. The operations team member verifies the inputs and confirms the physical verification in Azure Portal, Azure DevOps, and Ops Dashboard.
# 16. Peer Updates the Checklist and Assigns the Task
After successful validation, the operations team member fills the remaining entries in the checklist post validation and assigns the VSTS task back to the operations engineer who performed the deployment.
# 17. Operations Engineer Closes the Task
The operations engineer updates the deployment task with a comment and closes the task.
# 18. Operations Engineer Closes the Ticket
The operations engineer updates the iProcess/ServiceNow ticket with details and closes the ticket.
# 19. Automatic Notification Email to BL with Deployment Details
After the ticket is closed, an auto-notification email is sent to the BL with updates of the deployment.
# Operations Workflow
Note: For a full-size image, right click and select "Open image in new tab".
