ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update nexus: fix conflicts and sync local changes

Browse Source
This commit is contained in:
Shen Wei
2026-04-26 12:06:50 +08:00
parent 191797c01b
commit f09834b5a5
2443 changed files with 254323 additions and 255154 deletions
Download Patch File Download Diff File Expand all files Collapse all files

84
Archived/Work/2025 ITOM Cloud Knowledge Transfer/ESM Upgrade Strategy & Plan.md
View File

@@ -1,42 +1,42 @@
---
title:
source:
author: shenwei
published:
created:
description:
tags: []
---
## Review R&D Major Release Plan & Patch Plan
- ESM RTE: Mihaela Claudia Chis <mchis@opentext.com>
- PI Planning Readout Slides
- ESM Patch Release Owner: Tanuj Raja Vunnava <tvunnava@opentext.com>
- Patch Release Kick Off email
- Other requirement about upgrade strategy
- Demo/PoC Request
- Customer commitment etc.
## Prepare Cloud Upgrade Plan
### Design Tool
### Plan Strategy
- US2 Dev Farm Upgrade Validation - 1~2 days prior MR release date
- Shared Service - ITOM Aviator US30 staging, EU30 production, EU32 production need to be upgraded first before other consume farm upgrade
- EU3/US7 Trial/PoC Farm Upgrade - 1~ 2 weeks after GA release date, Upgrade on Monday (working day)
- US2/US24 Opentext Internal Customer Production Farm - 1st Wave Production Farm Upgrade (Maintenance Window)
- US26 - SalesForce customer need alternative upgrade date this can be negotiated with CSM and customer
- US26/US6/AP10/CA16 External Customer Production Farm - 2nd Wave Production Farm Upgrade (Maintenance Window)
- EU8/EU18/EU28/BR14/JP12 External Customer Production Farm - 3nd Wave Production Farm Upgrade (Maintenance Window)
- If ESM farm enable Operation Platform, need to upgrade Operation Platform first before upgrade ESM farm
- Considering the 1st patch release, we can consider to adopt patch upgrade direct in the upgrade maintenance window (Need to clarify the dependencies)
- Try to avoid upgrade window before key teams public holiday. Usually some critical issues will be reported on Monday/Tuesday after version upgrade. Need people standby to support troubleshooting
### Publish and Notify the ESM Cloud Upgrade Plan
- ESM Cloud Upgrade Plan Wiki Page: https://confluence.opentext.com/display/ICSD/ESM+Cloud+Ops+Change+Calendar
- ESM Cloud Ops Change Calendar: https://opentextcorporation.sharepoint.com/sites/MFI-SMAXSaaSDevOps/Lists/ESM%20Cloud%20Calendar/calendar.aspx
- Internal Communication About ESM Cloud Upgrade Plan (Sample Email)
### Continuous to adjust the plan according to the changes
- Cancel/Postpone the upgrade according to critical defects
### Rollback the upgrade
---
title:
source:
author: shenwei
published:
created:
description:
tags: []
---
## Review R&D Major Release Plan & Patch Plan
- ESM RTE: Mihaela Claudia Chis <mchis@opentext.com>
- PI Planning Readout Slides
- ESM Patch Release Owner: Tanuj Raja Vunnava <tvunnava@opentext.com>
- Patch Release Kick Off email
- Other requirement about upgrade strategy
- Demo/PoC Request
- Customer commitment etc.
## Prepare Cloud Upgrade Plan
### Design Tool
### Plan Strategy
- US2 Dev Farm Upgrade Validation - 1~2 days prior MR release date
- Shared Service - ITOM Aviator US30 staging, EU30 production, EU32 production need to be upgraded first before other consume farm upgrade
- EU3/US7 Trial/PoC Farm Upgrade - 1~ 2 weeks after GA release date, Upgrade on Monday (working day)
- US2/US24 Opentext Internal Customer Production Farm - 1st Wave Production Farm Upgrade (Maintenance Window)
- US26 - SalesForce customer need alternative upgrade date this can be negotiated with CSM and customer
- US26/US6/AP10/CA16 External Customer Production Farm - 2nd Wave Production Farm Upgrade (Maintenance Window)
- EU8/EU18/EU28/BR14/JP12 External Customer Production Farm - 3nd Wave Production Farm Upgrade (Maintenance Window)
- If ESM farm enable Operation Platform, need to upgrade Operation Platform first before upgrade ESM farm
- Considering the 1st patch release, we can consider to adopt patch upgrade direct in the upgrade maintenance window (Need to clarify the dependencies)
- Try to avoid upgrade window before key teams public holiday. Usually some critical issues will be reported on Monday/Tuesday after version upgrade. Need people standby to support troubleshooting
### Publish and Notify the ESM Cloud Upgrade Plan
- ESM Cloud Upgrade Plan Wiki Page: https://confluence.opentext.com/display/ICSD/ESM+Cloud+Ops+Change+Calendar
- ESM Cloud Ops Change Calendar: https://opentextcorporation.sharepoint.com/sites/MFI-SMAXSaaSDevOps/Lists/ESM%20Cloud%20Calendar/calendar.aspx
- Internal Communication About ESM Cloud Upgrade Plan (Sample Email)
### Continuous to adjust the plan according to the changes
- Cancel/Postpone the upgrade according to critical defects
### Rollback the upgrade