Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Lessons Learned from Migrating 3,000 Apps From PCF to OpenShift

As Kubernetes has emerged as the standard for Container orchestration, many Pivotal Cloud Foundation (PCF) customers are evaluating moving to a mature Kubernetes platform. Other factors for driving this decision include the VMware acquisition, concerns regarding product support/commitment and Pivotal's late entry into a Kubernetes based platform. Even Pivotal themselves is moving away from their original core platform.

In this webinar, Cedrus will presented how Pivotal Cloud Foundation customers can systematically approach migrating to OpenShift and how to come the migration challenges. Additionally, Cedrus also presented the lessons learnt from a PCF migration engagement with a large healthcare payer.

Who Should Attend: Developers and Architects eager to understand how to migrate from PCF to OpenShift.

Part 1: Considerations for Migration
Migration challenges per persona(PCF Developer, PCF Architects, PCF CI/CD pipeline engineers, PCF Operation, Executives)
Migration tool to capture dependencies

Part 2: Migration Methodology

Part 3: Customer Success Story:

Engagement Overview
PCF Vs. OpenShift Infrastructure gap analysis
PCF Application dependencies list
PCF Vs. OpenShift CI/CD Pipeline

Presented by Ashraf Souleiman - Partner, Cloud Native Practice VP - Cedrus Digital

  • Be the first to comment

Lessons Learned from Migrating 3,000 Apps From PCF to OpenShift

  1. 1. Ashraf Souleiman Partner, Cloud VP @ Cedrus Digital Migrating 3,000 Applications from PCF to OpenShift: Lessons Learned from Helping a Large Healthcare Payer 1
  2. 2. 2 Accelerate your journey to Kubernetes with the Konveyor Community A community of people passionate about helping others modernize and migrate their applications to the hybrid cloud by building tools and best practices on how to break down monoliths, adopt containers, and embrace Kubernetes.
  3. 3. Watch The Presentation
  4. 4. 4 What we’ll discuss today... ▸ Introduction: Overview of the Session, Speakers, and Cedrus ▸ Part 1: Considerations for Migration - Challenges per persona ▸ Part 2: Migration Methodology ▸ Part 3: Customer Success Story ・ Customer Profile ・ PCF Application Dependencies ・ PCF vs Openshift Infrastructure gap analysis ・ PCF vs Openshift CI/CD Pipeline
  5. 5. 5 Cedrus Digital Overview
  6. 6. 6 Cedrus - Cloud Native Practice Overview
  7. 7. 7 Part 1: Migration Challenges per Persona
  8. 8. 8 Customer Profile ● Large Healthcare payer ● 3000 Applications and 7 PCF clusters ● Home grown app manager and status tool ● Multiple CI/CD pipelines were migrated ● OpenShift clusters were configured on-prem ● Automated Code analysis to identify dependencies and complexity in minutes ● The migration plan included: Pilot phase Dependencies migration + code migration ● 18 Months including testing ● Savings of over $10M in licensing
  9. 9. 9 Migration Challenges Per Persona Challenges ● PCF Developer/Architects: ○ Change is always slow and hard ○ Need to learn the minimal to deploy to OpenShift ○ Do not have time for refactoring code ○ Do not want to touch orphan code ○ Provide new release of the code ○ Architects: changing the architecture paradigm is challenging for them so they intend to complicate To-Be Solution ○ No current charge back model to Development teams ● PCF CI/CD pipeline Engineers ○ Eager to learn new tool but their key challenge is lacking OpenShift Knowledge/Experience How to Address ● Refactor the first version of the code on their behalf ● Provide adequate documentation and help to support them moving forward ● Train them on OpenShift ● Provide a timeline for the migration and stick to it ● Augment them with experienced OpenShift engineers ● Provide adequate documentation and help to support them moving forward
  10. 10. 10 Migration Challenges Per Persona (Cont.) Challenges ● PCF Operation: ○ Often owns the platform but does not own the applications ○ Struggles to have some of the development teams to maintain even the latest versions of dependencies ○ Normally has accumulated a lot of technical debt from past projects ○ Needs to maintaining PCF environment until the migration is done which might include H/W refreshing and SW license cost ● Executive Sponsors ○ Save on PCF cost ○ Consolidate operations ○ Achieve a Cloud First Strategy ○ Migrate without business impact How to Address ● Provide a timeline for the migration and stick to it ● Provide adequate documentation, resources and help to support them moving forward ● Enforce the migration plans and stick to the timeline ● Stand up a parallel migration team ● Augment the team with the missing skills ● Train the staff to take ownership
  11. 11. 11 Part 2: Migration Methodology
  12. 12. 12 Migration Approach
  13. 13. 13 Assessment Phase ● Bottom-Up Analysis of Platform Usage for All Apps using Cedrus Migration tool ● Identify platform gaps and augment​ ● Analyze app dependency / config​ ● ​Modify app if needed​ ● Translate configuration to OpenShift config files ● Configure CI / CD Pipeline (S2I)​ ● Test and Deploy
  14. 14. 14 Cedrus Migration Tool is Open Source Now
  15. 15. 15 Part 3: Assessment Phase Findings
  16. 16. 16 PCF Platform Dependencies
  17. 17. 17 Mapping Services to OpenShift Environment
  18. 18. 18 PCF CI/CD Pipeline
  19. 19. 19 OpenShift CI/CD Pipeline
  20. 20. Join the Konveyor Community Chat with us on Slack
  21. 21. Thank you! 21 Ashraf Souleiman Partner - Cloud Native VP