coordination #28869
opencoordination #28630: [qe-core] setup for LPAR installation (manual + automatic)
[epic] Automated installation on s390x LPAR through zHMC & integration into openQA
Added by mgriessmeier about 7 years ago. Updated 6 months ago.
25%
Description
Acceptance criteria¶
- AC1: LPARs are integrated in openQA and can be installed automatically
Further details¶
- use a tool named snIPL which can be found in SLE15 repos to interact with the zHMC via command line
- probably we need at least one, maybe two additional consoles in openQA which can handle the zHMC over cli and fetch Operating System Messages from it
Updated by cachen about 7 years ago
- Subject changed from [sle][functional][virtualization][tools][s390x] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390x][tools] Automated installation on LPAR & integration to openQA
Updated by xlai about 7 years ago
- Subject changed from [sle][functional][virtualization][s390x][tools] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390-kvm][s390x][tools] Automated installation on LPAR & integration to openQA
Updated by mgriessmeier almost 7 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390-kvm][s390x][tools][u] Automated installation on LPAR & integration to openQA
- Target version changed from Milestone 16 to Milestone 15
Would like to have this done in M15, please consider during Milestone planning
Updated by okurz almost 7 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390-kvm][s390x][tools][u][epic] Automated installation on LPAR & integration to openQA
If you like to have it, sure. But I fear it's an epic. At least so far. Needs further refinement.
Updated by okurz almost 7 years ago
- Due date set to 2018-04-24
- Assignee set to mgriessmeier
@mgriessmeier I guess w/o you pushing forward this is not being groomed into stories
Updated by mgriessmeier almost 7 years ago
okurz wrote:
If you like to have it, sure. But I fear it's an epic. At least so far. Needs further refinement.
okay, but it's already subtask of an epic, so I will refine this further and set the parent ticket to [saga]
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-04-10 to 2018-04-24
due to changes in a related task
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-04-24 to 2018-05-22
due to changes in a related task
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-05-22 to 2018-07-03
due to changes in a related task
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-07-03 to 2018-05-22
due to changes in a related task
Updated by mgriessmeier almost 7 years ago
Ticket refined,
- added 3 subtasks planned for sprint13, sprint14 and sprint15
- changed parent ticket to [saga]
Updated by nicksinger almost 7 years ago
- Related to coordination #21838: [functional][u][saga] PowerVM backend added
Updated by nicksinger almost 7 years ago
- Due date changed from 2018-05-22 to 2018-06-05
due to changes in a related task
Updated by nicksinger almost 7 years ago
- Due date changed from 2018-06-05 to 2018-06-19
due to changes in a related task
Updated by nicksinger almost 7 years ago
- Due date changed from 2018-06-19 to 2018-06-05
due to changes in a related task
Updated by nicksinger almost 7 years ago
- Due date changed from 2018-06-05 to 2018-05-08
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-05-08 to 2018-05-22
due to changes in a related task
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-05-22 to 2018-06-05
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-06-05 to 2018-07-03
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 15 to Milestone 17
critical chain now depends on #33232 (M17)
Updated by okurz over 6 years ago
- Due date changed from 2018-07-03 to 2018-06-20
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-06-20 to 2018-07-03
due to changes in a related task
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-07-03 to 2018-07-31
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-07-31 to 2018-08-14
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 17 to Milestone 18
it's M18 actually
Updated by riafarov over 6 years ago
- Due date changed from 2018-08-14 to 2018-09-11
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 18 to Milestone 19
that's actually M19
Updated by okurz over 6 years ago
- Due date changed from 2018-09-11 to 2018-11-20
due to changes in a related task
Updated by okurz about 6 years ago
- Target version changed from Milestone 19 to Milestone 20
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-11-20 to 2018-04-11
due to changes in a related task
Updated by okurz about 6 years ago
- Due date changed from 2018-11-20 to 2018-11-07
due to changes in a related task
Updated by okurz about 6 years ago
- Target version changed from Milestone 20 to Milestone 25+
-> #33916
Updated by okurz almost 6 years ago
- Due date changed from 2018-03-27 to 2020-01-02
due to changes in a related task
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25+ to Milestone 26
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 26 to Milestone 29
pvm has higher prio, lpar still covered manually
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 29 to Milestone 35+
Updated by SLindoMansilla over 4 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u][epic] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390-kvm][s390x][tools][epic] Automated installation on LPAR & integration to openQA
Updated by okurz about 4 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][epic] Automated installation on LPAR & integration to openQA to [sle][functional][virtualization][s390-kvm][s390x][epic] Automated installation on LPAR & integration to openQA
I don't see the need for the SUSE QA Tools team (which ignored that issue so far anyway) so far. I am sure you will be able to find us in case of specific backend problems where you need support :)
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Blocked to New
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by szarate over 2 years ago
- Target version changed from Milestone 35+ to future
Updated by mgriessmeier 6 months ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][epic] Automated installation on LPAR & integration to openQA to [epic] Automated installation on s390x LPAR through zHMC & integration into openQA
- Category set to Feature requests
(updated description)
as follow-up of https://bugzilla.suse.com/show_bug.cgi?id=1226215 - this task should be revisited and re-evaluated