Project

General

Profile

Actions

coordination #119671

closed

[epic] Improve SAP migrations using auto-installation

Added by JERiveraMoya almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-11-01
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

In similar way that we improved HA migrations using AutoYaST, we want to improve SAP migrations using auto-installation.
Main motivation are two:
(1) To be able to reproduce all the steps of the installation and avoid the lack of this information in bugs when we only have an image stored in openQA created 'in some way, manually or automatically'.
(2) Save time patching the system during migration

Currently in openQA job group Migration: SAP we run these migration and they are not running anywhere else (in any SAP job group) as was considered stable enough and not required too much SAP expertise for Yam squad to have the ownership for these test suites. In that sense it would differ from the work done for HA that we SAP/HA squad doesn't need to link their SAP migration with our standalone one, because in this case we run all the test suite and they will not really be standalone installation, as they would run a few test modules after the installation (see about about that in the subtasks), but at least they are not running a cluster, which was one of the main impediments for HA.

Acceptance criteria

AC1: Create AutoYaST test suite to create images for SLES for SAP 12 SP{4,5}
AC2: Create AutoYaST test suites to create images for SLES for SAP 15 SP{2,3,4} and to run before migration directly chained for PowerVM.
AC3: Provide AutoYaST installation for horizontal migrations
AC4: Enable SLES for SAP migrations using AutoYaST installations
AC5: Rename all test suites used to start with sap_* in order to locate them easily


Subtasks 6 (0 open6 closed)

action #119683: Use AutoYaST installation to create images for SLES for SAP 12 SP{4,5}ResolvedJRivrain2022-11-01

Actions
action #119698: Use AutoYaST installation to create images for SLES for SAP 15 SP{2,3,4}Resolvedjgwang2022-11-01

Actions
action #119707: Use existing AutoYaST gnome installation for SLES for SAP Horizontal migrations for arch x86_64Resolvedshukui2022-11-01

Actions
action #120076: Setup migration for SLES for SAP Apps 12 SP{4,5} using auto-installationsResolvedshukui2022-11-08

Actions
action #120088: Setup migration for SLES for SAP Apps 15 SP{2-4} using auto-installationsResolvedjgwang2022-11-08

Actions
action #122230: Document mapping of new migration and existing ones for SLES for SAPResolvedtinawang1232022-12-20

Actions

Related issues 2 (0 open2 closed)

Related to qe-yam - action #116164: test fails in patch_sle - too slow ppc64le workers?Rejected2022-09-02

Actions
Related to qe-yam - coordination #121957: [saga] Consolidation of test coverage in Yam squadResolvedJERiveraMoya2022-03-25

Actions
Actions #1

Updated by JERiveraMoya almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by JERiveraMoya almost 2 years ago

  • Description updated (diff)
Actions #3

Updated by JERiveraMoya almost 2 years ago

  • Description updated (diff)
Actions #4

Updated by JERiveraMoya almost 2 years ago

  • Related to action #116164: test fails in patch_sle - too slow ppc64le workers? added
Actions #5

Updated by JERiveraMoya almost 2 years ago

  • Description updated (diff)
Actions #6

Updated by JERiveraMoya almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #7

Updated by JERiveraMoya almost 2 years ago

  • Subject changed from [Epic] Improve SAP migrations using auto-installation to [epic] Improve SAP migrations using auto-installation
Actions #8

Updated by JERiveraMoya almost 2 years ago

Actions #9

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by JERiveraMoya over 1 year ago

  • Status changed from Resolved to In Progress
Actions #11

Updated by JERiveraMoya over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF