Project 204 : CDR Modernization – Migration from OnPrem to Azure Cloud

Tasks & Timelines

COMMON Tasks :
    *. Create a DL/Group Of Approvers  – PR_Approvers group created but PENDING to add final list of approvers.
    *. Enable Build Policy to get PR_Approvers group added as Reviewrs. – Done for Echolocate & PENDING for GMLC & OOkla
    –     Q) Should the whole group approves to proceed to Complete Merge ? or one approval among the grp is enough ?
    *. Set Notification & test Notification – DONE
    *. Deny contribute access to “Deny merge to master” group under Repo > Branching > master > branch security.
    *. Monitoring & Testing
    * Update Documents (Design & Architecture, Runbook & MOP)

    Pending Tasks 
    1. Setup Nexus for GMLC & Ookla (Injestion)
        1.1 Get the pipeline run on Azure VM –     DONE for GMLC, Pending for Ookla
        1.2 update pom.xml with Nexus url & details – DONE for GMLC, Pending for Ookla
             Nexus path  http://10.92.139.24:8081/nexus/content/repositories/quantum-dev-releases/ 

    2. Rename jar file for Echolocate – PENDING
    3. build Ookla_Echolocate ETL Pipeline with “sbt clean assembly”  – PENDING
    4. Make the artifact publish to Nexus even the same version exists.  – PENDING

    GMLC

    *. Create Pre_Prod Branch to maintain two branches as per the branching Strategy – DONE
    *. Create Build Pipelines for Pre_Prod – DONE
    *. Create Release Pipeine for Pre_Prod – DONE
    *. Create Build Pipelines for Prod – DONE
    *. Create Release Pipeine for Prod – DONE
    *. Create a feature branch and push to Remote Repo.  – DONE
    *. Test Build pipline for Pre_Prod – DONE
    *. Test Release pipeline Pre_Prod – DONE
    *. Enable auto-trigger for Build & Release Pipelines of Pre_prod & Prod – DONE
    *. Branching Security for upstrem Repo master – PENDING
    *. Publish artifacts to Nexus.                                – PENDING
        – Add entries for Nexus in pom.xml
        – Folder in Nexus need to be created for GMLC NPE & Prod.
        – Test

    OOkla 


    *. Create Pre_Prod Branch to maintain two branches as per the branching Strategy – DONE
    *. Create Release Pipeine for Pre_Prod – PENDING
    *. Create Build Pipelines for Prod – PENDING
    *. Create Release Pipeine for Prod – PENDING
    *. Create a feature branch and push to Remote Repo.  – PENDING
    *. Test Build pipline for Pre_Prod – PENDING
    *. Test Release pipeline Pre_Prod – PENDING
    *. Enable auto-trigger for Build & Release Pipelines of Pre_prod & Prod – PENDING
    *. Branching Security for upstrem Repo master – DONE
    *. Create a DL/Group Of Approvers 

    Echolocate 


    2. Create Pre_Prod Branch to maintain two branches as per the branching Strategy – DONE
    3. Create Build Pipelines for Pre_Prod – DONE
    *  Get his build command updated in all build Pipelines : sbt clean assembly publish
    *. Create Release Pipeine for Pre_Prod – DONE
    *. Create Build Pipelines for Prod – PENDING
    *. Create Release Pipeine for Prod – PENDING
    *. Create a feature branch and push to Remote Repo.  – PENDING
    *. Test Build pipline for Pre_Prod – PENDING
    *. Test Release pipeline Pre_Prod – PENDING
    *. Enable auto-trigger for Build & Release Pipelines of Pre_prod & Prod – PENDING
    *. Branching Security for upstrem Repo master – DONE
    *. Create a DL/Group Of Approvers 



Implimentation Steps

        1.1 Get the pipeline run on Azure VM –     DONE for GMLC, Pending for Ookla

Get the pipeline run on Azure VM

  1. Added below code to add the Azure VM as Agent

pool:
  name: cicd_pool
  demands:
    – agent.name -equals AzDevOps-WIN2019-CICD-02

2. Installed dependecis on Azure VM

Dependencies are Maven 3 software & Java Version

Java 1.8 is already in place

Downloaded Maven 3 solftware from Apachi Maven website https://maven.apache.org/download.cgi

Copied the software from download location to > Program Files

copied the location of the software and had set the path in Environment Variables.

3. Stopped Azure Agent servie and started with the command run

Agent in the Agent pool automatically got updated with new changes on the server.

Pipeline ran successfully.

Recording Link : https://myfuturehub.sharepoint.com/sites/MFHDevOpsSupport-SreekanthA/Shared%20Documents/General/Recordings/General-20230105_202627-Meeting%20Recording.mp4?web=1

1 thought on “Project 204 : CDR Modernization – Migration from OnPrem to Azure Cloud”

  1. Devops Client Project – Invite

    Schedule : 8:30 PM IST, 06-Jan-23

    Client : T-Mobile, USA

    Agenda
    1. Setup Nexus for GMLC & Ookla (Injestion)
            1.1 Get the pipeline run on Azure VM –     DONE for GMLC, Pending for Ookla
            1.2 update pom.xml with Nexus url & details – DONE for GMLC, Pending for Ookla
                 Nexus path http://10.92.139.24:8081/nexus/content/repositories/quantum-dev-releases/
           
        2. Rename jar file for Echolocate – PENDING
        3. build Ookla_Echolocate ETL Pipeline with “sbt clean assembly”  – PENDING
        4. Make the artifact publish to Nexus even the same version exists.  – PENDING

    Cloud : Azure

    Reply

Leave a Comment

MFH IT Solutions LLP

Consultation & project support organization.

Contact

MFH Devops Consulation
NAD Kotha Road, Opp Bashyam School, Butchurajupalem, Jaya Prakash Nagar Visakhapatnam, Andhra Pradesh – 530027