Configure migration activities in Jira project

Anuradha Yadav June 10, 2021

Hi Team,

We have a Migration activity to come. And we have tasks/activities to perform to achieve the same.

Please help with some suggestions how do we configure these activities in Jira cloud project?

 

Task Name

GT Cloud Migration Programme

   SOW and Sign Off

      SOW Agreed & Approved

      PO Raised

   SOW and Sign Off Received

   Project Initiation

      Kick Off Presentation

         Prepare Kick Off Presentation

         Review Kick Off Presentation with stakeholders

         Execute Kick Off Presentation with GT

      Successfully Completed Kick Off Presentation

      Project Plan Preparation

         Create Draft Project Plan

         Review Project Plan internally

         Incorporate the Changes

         Project Plan review with GT

         Incorporate Project Plan Changes

         Project Plan agreed and Sign Off

   Project Initiation Completed

   Planning and Requirement Gathering Phase

       Discovery and Assessment Phase

          Discovery

             Create Customer network access to the project resources

             Share the Azure Migrate Discovery tool pre-requisites with GT

             Enable access to GT environment through VDI/VPN

             Download Azure Migrate Discovery appliance(OVA file) in GT environment

             Install and configuration of Azure Migrate Discovery Appliance

             Gather the required baseline information for discovery from various sources like CMDB/Infrastructure sheet

            Anaylses of Vcentre IP details from the CMDB sheet

             Get the credentials for in-scope devices to initiate discovery

            Verify Appliance connectivity with environment and Azure

            Monitoring of Azure migrate appliance for full scan

             Initiate extended scan(4 weeks) to capture dependencies between servers

             Analyze all the discovered components data for each hosts

             Prepare standard reports with the discovered data and review the data with stakeholders

             Add if there are any hosts missed from CMDB/discovery data

          Application Survey

             Finalize survey question template based on GT environment

             Review and share template with app owners for completing application survey

             Gather Application owners with their contact information for respective applications

             Organize meetings with App owners to identify the dependencies and fill the survey

          Assessment activities

             Import discovery template(in CSV) into IntelliAssess

             Submit survey response from Application owner on to IntelliAssess portal

             Run assessment for application and Infra

             Populate the Discovery and assessmet metrics on to IntelliAssess dashboard

             Finalize App to Infra mapping

             R-lane re-confirmation for remote office locations.

             Prepare initial assessment report and Update MGL

             Update MGL and Final Assessment Report and submit for Sign-off

      Discovery and Assessment Phase Completed

      On Prem and Target Cloud Readiness

         Planning Workshop with GT

         Existing inventory of applications, databases and infrastructure that are targeted for migration to cloud.

         GT to provide inventory of Remote Offices for Discovery and Assessment.

         Software Assurance - Investigate Azure adoption of license from on-prem - GT confirmed Hybrid benefits to be used

         Azure Resource Group access to be provided to Wipro Team - Owner / Contributor access - To check with Raja

         Naming Convention of migrated Servers - Raja confirmed servers will be migrated with the same host name.

         Connectivity to Azure is established - Confirmed by Raja

         GT Environment servers RDP access to be granted for Wipro Project members.

         GT RSA Token / VPN access

         Collect OnPrem and Target Environement HLD and LLD

         Network Design of On Prem and Target Cloud - Max and Raja to cover

          Identify the target Azure region to be migrated (Primary) - Azure East US2

         Read only access to be provided to Wipro at Subscription Level

          Confirmation on for Firewall ports opening & validation

         Verify & Validate: N/W connectivity between On-Prem & Target Environment - Its established

          NSG/ASG configuration - Raja confirmed it will be done by GT

          Create Target Storage Account - Raja to confirm

         VM Tagging information to be provided - Raja to confirm

          Create Application gateway/Load balancer ( based on requirment ) - Raja to confirm

         Verify the network bandwidth for migration & replication activity - 1 GBPS confirmed by Raja

          Identifying Azure cloud resources & Infra T-shirt sizing for the applications to be migrated

         Wipro team will understand the technical requirements including High Availability & DR requirements, Type and size of VM, Storage and share with Grant Thornton for final sign-off on the architecture.

      On Prem and Target Cloud Readiness Deep Dive Completed

   Planning and Requirement Gathering Phase Completed

   Design Phase

      Design Template

         Creating Draft HLD/LLD Template

         Internal Review of HLD/LLD Template

         Update HLD/LLD Template

         Sharing HLD/LLD Template for GT Approval

         Updating HLD/LLD Template based on GT Feedback

         Design Template Signed-off

         Design Template Completed

      Design Document Creation

         HLD/LLD Doc Structure Creation

         HLD/LLD Workshop - Infra + Network

         HLD/LLD Workshop - Security

         HLD/LLD document creation based on the inputs

         HLD/LLD Release for GT Review

         Design Review HLD/LLD with Microsoft

         HLD/LLD joint discussion with GT

         HLD/LLD Update & Release for GT Review

         Document Finalization with any remaining comments

         Design Document Creation Completion and Sign-off

   Design Phase Completed

   Migration Wave Plan Readiness Phase

      Migration Charter Readiness

       Prepare and Finalize the Move group plan per application according to assesment report with application owner sign off

       Application owner signoff for cut over activities and estimated downtime

      Create RFC requirements in ADO

      Raise Change Request # and get approval

      Raise Change Tasks are created to respective teams

      CAB meetings on Wednesdays Central Time

       Prepare and ensure comm matrix implemented to enable required ports with GT app and network team

      Provide cut over tasks and downtime for cutover

      Prepare the technical Runbook with Migration approach steps

   Migration Wave Completed

   Migration - PreRequisites Validation

       Setup Target Environment validation

       Provide cut over tasks and downtime for cutover

       Prepare and submit communication matrix to enable required ports and approval

       Configure maintenance mode and provide access to cloud support admin team

       Check if proxy is enabled for the servers and if this is required to be kept enabled post migration (if applicable)

       Check and confirm the On Prem Server OS patch level (if applicable)

       Collect data on business criticality with the indiviual GT Application owners

       Check the road blocks to proceed with Migration planning

       Validate Migration approach for workloads

       Migration Charter Readiness and Sign off

       Raise Change Request # and get approval

       Raise Change Tasks for respective teams

   Pre-MIgration Plan

      Raise a request to back up the on-prem server

      Create Azure Migrate Project (or validate if already created)

      Validate Appliances are registered to Migrate Project

      Create Server Groups in Azure Migrate for Migration

      Replicated Servers to Target Environment

      Go/No Go checkpoint call

   Test Migration

       Initiate Fail Over process with latest RPO, select the target Azure network to which Azure VMs will be connected after failover occurs

       Complete the test failover

       Sanity Test -Infra prespective

      Handover the server to App owners for testing and confirm

      Test Migration Sign off by App owner

      Clean up of the test migrated server

      Go/No Go checkpoint call

   Migration Readiness

      Stakeholders to provide confirmation for final migration

       Confirm application, network, security and AD team availability for cut over and communication to business and user groups

       Go/No Go Decisions

   Migration and Cutover

       Cut-over - Share the bridge details to all stakeholders and Support teams to join on the day of cut-over

      Intiate Migration to Target Environment after replication

      Verfiy the data disk size and type

       Run IP config/all & nslookup commands

       Tracert for next hoping and telnet to check the ports

       Check for DNS configuration & SMTP relay

       Shutdown the application, DB & VM on source DC to ensure zero data lost in case roll back is invoked

       Initiate Fail Over process with latest RPO, select the target Azure network to which Azure VMs will be connected after failover occurs

       Check the disk standards and configuration

       Handover the server to App owners for testing

       Change the Disk drives as per standard C: Premium or Standard SSD, Data Drive : Premium or Standard SSD

       Ensure that the disks are allocated for the intended DC and Resource Group

       RDP the VM via IP and flush the DNS entry

       Add support team AD group at OS and DB level permission

       Uninstall Vmware tools on Target [while on the cloud]and Restart the Server

       Resource Health Check

       Infra level sanity test

       App team Functionality check

       Remove temporary NIC from Azure console post assigning new NIC to VM

       VM tagging in Azure

       Release the server to Application Owner to execute UAT

       App Owner to provide migration signoff after UAT is executed successfully and application is healthy

       Go/No Go checkpoint call for final sign off

       Gracefully initiate the complete migration

   Validation and Go Live

      Azure instance to be accessed remotely

      Provide new IP Address into Tivoli for patching

      Validation of backup config details

      Confirm the antivirus agents are running on the new instances

      Validate the Azure monitoring parameters

      Start the application & DB services

      Perform Application & Business functionality testing as agreed

   Hypercare and Handover to BAU Support

      Migrated systems in Warranty period for 2 weeks

      Knowledge Transfer Sessions to BAU

      Handover the systems to BAU team and Signoff

   Closure Reports

Project Completion Sign Off

 

Regards,

Anuradha

1 answer

1 accepted

0 votes
Answer accepted
Sadeesh Narendran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2021

@Anuradha Yadav Start top most as Initiative - GT Cloud Migration Programme

then next sub item as Epic -    SOW and Sign Off,    Project Initiation

then sub items under Epic as Stories -       SOW Agreed & Approved, PO Raised

Items under Story as Task / Subtask.....

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events