OPDK version migration guidelines

[tgp]

Hi Team,

There is a proposal for the OPDK migration from current OPDK 4.50 to 4.52 latest version.

Current system have 500+ proxies.

What are the prerequisites, best practieces and guidelines need to be considered for pre and post migration?

And usually how it is being done for Apigee OPDK customers from Google side?

TIA.

[Denis_KALITVI]

quite broad question, is it your first upgrade? I suggest you hire Apigee partner or consultant that will build the plan for you, not sure if forum is the right place for such complicated question

[API-Evangelist · Accepted solution]

In general

Pre-req:

Check Release notes -> https://docs.apigee.com/release/notes/45200-edge-private-cloud-release-notes

Assess the Current State ->Conduct a comprehensive assessment of the current state of the API platform, including its architecture, infrastructure, configurations, policies, and customization.

Analyze Dependencies ->Analyze dependencies between the API platform and its upstream and downstream systems, such as backend applications, and third-party services. Identify any potential issues and determine how they will be addressed.

Identify Risks and Challenges -> Identify any potential risks and challenges that may arise during the migration, such as compatibility issues, performance degradation, data loss, or downtime.

Plan the Migration Strategy -> Develop a migration plan that outlines the sequence of migration, timelines, roles and responsibilities, communication plan, and testing strategy.

Validate the Migration Plan: Validate the migration plan with all stakeholders, including developer, and business owners. -- better be transparent.

Migration:

Use a Test Environment -> Perform the migration in a test environment to avoid any disruption to the production environment. This will allow you to test the migration plan and identify any issues before deploying to the production environment.

Backup and Restore: Backup all data before the migration and restore data in case of any data loss or corruption during the migration process.--> Practice this it helps in lower environment

Test and Validate -> Test and validate the migrated APIs to ensure that they function as expected. Use automated testing tools to identify any issues.

Monitor Performance -> Monitor the performance of the migrated APIs to identify any issues related to performance, such as increased latency or decreased throughput.

Work with support/community to report any issues 🙂

Once you have all things documented steps,issues/resolutions etc in place just plan on production migration..may be inform apigee support for any stand by support..

Post Migration Inform stakeholders to validate/monitor..

Ideally Apigee upgrade looks complex but you can achieve with less downtime (<15 min) if we practice and well document..

Good luck.

[tgp]

Thank you for your guidelines.