coordination #119671
Updated by JERiveraMoya over 1 year ago
#### 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](https://openqa.suse.de/group_overview/448) 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 image for SLES for SAP 12 SP{4,5} **AC2**: Create AutoYaST test suites to create images run before migration directly chained 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