Prashanth Kasoju

Responsibilities:

Worked with different Dev teams to understand their requirement and coordinated with them to Onboard their projects to DevOps tool set.

Understanding the clients existing legacy tool design and promoted and implemented CI/CDdepending on their requirement to eliminate existing manual

Deployment process.

Educated the Dev Teams on DevOps technologies by conducting Cohurt Trainings within the Organization on Jenkins/Git/Nexus.

Designed the confluence documentation on Jenkins for Dev Teams to speedup for onboarding into DevOps tools.

Provided the access and helped dev teams to configure the jobs in Jenkins Sandbox environments.

Configured The Project specific folders for Dev Teams in Jenkins Dev Master to build/deploy jobs

Configured multiple Jenkins slaves(linux/Windows) for multiple projects using Jenkins-Distributed Execution .

Handled various issues with Jenkins slave agents during project execution.

Created Free style projects and configured Jenkins Pipelines for Build/Deploy.

Configured Jenkins files to automate and manage Executors,Labels,Node_ownersas a self -service job for Dev teams.

Recommended Dev teams to follow Best practices for Build/Deploy Pipeline.

Worked with Dev teams and Promoted Jobs from Lower environments like Sandbox to Dev/Prod/HA environment.

Worked with Dev team to follow standard Artifact Promotion Job and as well as Jenkins Job promotion Process to higher environments.

Installed Various Plugins eg:Amazon Ec2, Castlite, CloudBees Label Throttling Plugin ,HPE Application Automation Tools, Junit Plugin, Nunit Plugin, Performance Plugin on Jenkins Sandox,Dev Masters.

Worked with Dev teams and coordinated and upgraded/downgradedPlugins based on the requirement and promoted the pluigns to Jenkins Masters.(SBX->DEV->PRD)

Worked with Cloud Bees Support team and created Cloud Bees Support tickets for maintaining various masters on CJOC.

Worked with Dev teams and resolved outage issues in DEV/PRD Environments by raising the bridge and coordinated and engaged with Clous BEES support.

Worked as a DevOps support system for various Jenkins slave/Configuration/Build/Deploy issues and helped various Dev teams.

Project: (BEES): Broadridge Exception Event System is proposed to be standard Exception aggregator system that sits over key Broad ridge processing engines and related applications (Gloss, IMPACT, BPS, Ascendis, Proactive and similar) and consolidates exceptions across systems for Operations users to have a one single view to act upon and for the end clients to get a view or extract reports on the exceptions and status. It will provide a universal view of all exceptions across all clients, automate client report generation and provide the initial Client & Associated Portals the BPO needs to action exceptions.

Overall solution is Java/JEE based

Onboarding: Any external team/individual wants to use DevOps deployment platform (Jenkins, Git, Nexus) they need access to these DevOps tools. To get access to these tools, first step is to

onboard their project. Part of this onboarding, DevOps COE team will provide access to these tools.

As part of the Onboarding process, E-mail-enabled security groups will be setup for each team. These groups will be used to manage access to the DevOps platform. A Development contact will be identified as the list owner(Dev primary contact) for each of these groups.

Example of E-mail enabled security groups created for “BEES” project

BEES_DevOps_GitLab_Users

BEES_DevOps_Jenkins_Users

BEES_DevOps_Nexus_Users

Jenkins :

Broadridge uses CJOC(Cloudbees Jenkins Operation Center).

CJOC is used for managing multiple Jenkins Masters.

Currently we have Four Jenkins Masters on CJOC.

Master #1 - Sandbox / Prototyping: Used for Project POC ‘s.

Master #2 -Development / Build Server (incl. Continuous Activities):Actual Dev Sever where your development and Integration environments are available.

Note : Developers spend 90% of time on Dev Jenkins Master for Build/Deploy/Test activities.

Master #3 - Production / Deployments (for QA/UAT/PROD): This Master is used for On Prem deployments for Higher environments Eg: QA/UAT/PROD.

Master #4 - AWS PSS Production Deploy: Used for AWS Deployments.

• Primarily developers spend most of the time on Jenkins Dev master for Build,deploy and testing there jobs .

• Jenkins Dev Master has more than 400 Agents installed and acting as Jenkins Slaves .

• More than 188 Projects are on boarded to Jenkins .

• DevOps treat Jenkins Dev Master as a Production System and Provides an extensive Support for any issues.

Access Management:

• Access is Managed using Active directory and uses LDAP authentication.

• Users should use BSG credentials to login into Jenkins Masters.

• Access is provided to the members using Email enabled Security groups which was covered as part of On Boarding.

• Dev team has complete access w.r.t Project to configure/build/delete/view Jobs.

• For Higher environments Dev team is expected to have only read access so that they can able to see the Jenkins logs during deployment.

• Only Service Delivery/Deployment Team has Buildaccess to run the Jobs on higher environments.

• For Updating Secrets/passwords in the higher environments we will provide credential manager access.

Project: (BEES): Broadridge Exception Event System is proposed to be standard Exception aggregator system that sits over key Broad ridge processing engines and related applications (Gloss, IMPACT, BPS, Ascendis, Proactive and similar) and consolidates exceptions across systems for Operations users to have a one single view to act upon and for the end clients to get a view or extract reports on the exceptions and status. It will provide a universal view of all exceptions across all clients, automate client report generation and provide the initial Client & Associated Portals the BPO needs to action exceptions.

Overall solution is Java/JEE based

Onboarding: Any external team/individual wants to use DevOps deployment platform (Jenkins, Git, Nexus) they need access to these DevOps tools. To get access to these tools, first step is to

onboard their project. Part of this onboarding, DevOps COE team will provide access to these tools.

As part of the Onboarding process, E-mail-enabled security groups will be setup for each team. These groups will be used to manage access to the DevOps platform. A Development contact will be identified as the list owner(Dev primary contact) for each of these groups.

Example of E-mail enabled security groups created for “BEES” project

BEES_DevOps_GitLab_Users

BEES_DevOps_Jenkins_Users

BEES_DevOps_Nexus_Users

Jenkins :

Broadridge uses CJOC(Cloudbees Jenkins Operation Center).

CJOC is used for managing multiple Jenkins Masters.

Currently we have Four Jenkins Masters on CJOC.

Master #1 - Sandbox / Prototyping: Used for Project POC ‘s.

Master #2 -Development / Build Server (incl. Continuous Activities):Actual Dev Sever where your development and Integration environments are available.

Note : Developers spend 90% of time on Dev Jenkins Master for Build/Deploy/Test activities.

Master #3 - Production / Deployments (for QA/UAT/PROD): This Master is used for On Prem deployments for Higher environments Eg: QA/UAT/PROD.

Master #4 - AWS PSS Production Deploy: Used for AWS Deployments.

• Primarily developers spend most of the time on Jenkins Dev master for Build,deploy and testing there jobs .

• Jenkins Dev Master has more than 400 Agents installed and acting as Jenkins Slaves .

• More than 188 Projects are on boarded to Jenkins .

• DevOps treat Jenkins Dev Master as a Production System and Provides an extensive Support for any issues.

Access Management:

• Access is Managed using Active directory and uses LDAP authentication.

• Users should use BSG credentials to login into Jenkins Masters.

• Access is provided to the members using Email enabled Security groups which was covered as part of On Boarding.

• Dev team has complete access w.r.t Project to configure/build/delete/view Jobs.

• For Higher environments Dev team is expected to have only read access so that they can able to see the Jenkins logs during deployment.

• Only Service Delivery/Deployment Team has Buildaccess to run the Jobs on higher environments.

• For Updating Secrets/passwords in the higher environments we will provide credential manager access.

Client: Cisco

Role: OBIEE Developer

• Have good knowledge and experience in the areas of Data Warehousing Concepts & Report development.
• Hands on Experience in OBIA, such as developing data models. RPD and reports.
• Extensive expertise at developing and scheduling ad-hoc and canned Analytics Reports using OBIEE/OBIA Answers, Dashboards.
• Responsibilities included Building of RPD application design for Physical, Logical, and Presentation layers, configuration of those layers, development of Reports, Dashboards, and testing, and deployment in Unix Environment
• Done End to End Implementation in the Project(Such as Loading Data into Source tables provided by Users on by the user On monthly basis and Loading into EDW tables and verifying the data in Reports).
• Developed various reports based on different Views in OBIEE and SAP BO and developed Dashboards.
• Handled different tasks like Maintenance and enhancements of the OBIEE reports and BO.
• Responsible for debugging, Defect Tracking and Data Verification.
• Resolved priority Incidents/issues ( P2/P3) reported by the Business with in the time limits by providing the code fixes.

· Implementation of object level and Data level security.

· Working experience on Informatica.

· Monitored ETL data load using DAC and Dollar U Environments..

a) Project Description

Cisco Capital is a wholly-owned subsidiary of Cisco Systems, specializing in providing innovative financing for Cisco solutions worldwide. More than just a finance company, Cisco Capital is uniquely positioned to provide the most flexible and competitive financing for your acquisition of Cisco technologies. Cisco Capital delivers financing solutions designed to support your business goals and technology needs, both today and in the future.

a) Contribution

· Provided the Basic L1 Support for the Business such as Providing Access to the new users using ADOM.

· Analysis of the issues raised in the form of cases.

· Effort estimation for minor enhancements.

· Impact analysis during CR’s.

· Provided the Root Cause information to the Business for the data related issues in EDW Vs Source system.

· Streamlining the support process with effective implementations of IT for IT activities.

· Requirements gathering with direct interaction with Cisco business.

· Provided Support to Business regarding Ad-Hoc Reporting issues and renaming

· The columns according to Business requirement.

Project Description

US Steel, headquartered in Pittsburgh is the largest fully integrated steel producer in the United States. It has major production operations in the United States and Central Europe spanning various market segments like Automotive, Construction & SCEA. United States Steel Corporation (USS) is implementing an ERP system, Oracle eBusiness Suite, to streamline production and business operations in the areas of Manufacturing, Accounting, and Human Resources, Procurement and Order to Cash

b) Contribution

• Defect fixing for the previous builds.
• Resolved severe and critical defects.
• RPD and Web Catalog migrations.
• Daily interaction with Clients and gathering requirements.
• Developed Technical design documents
• Developing Data models and Building Reports for Financial Transactions and Procurement and Spend.
• Designed reports with multiple views like Pivot table, Ticker and narrative views etc.
• Prepared ETL testing document, Rpd testing document and BUT testing documents.
• Worked on Informatica Mappings (SDE, SIL and PLP)
• Hands on Experience on DAC