action #33226
opencoordination #28630: [qe-core] setup for LPAR installation (manual + automatic)
coordination #28869: [epic] Automated installation on s390x LPAR through zHMC & integration into openQA
Add a simple testsuite which uses the planned LPAR backend
0%
Description
User story¶
After the backend is implemented we want to add a first simple testsuite on OSD which makes use of it.
This is the preparation for poo#33232
Acceptance criteria¶
- AC1: OSD executes a simple test
Suggestions¶
- Take ideas, documentation and potential "scratch WIP code changes" from #33916 and include the necessary code changes in a proper, clean way within os-autoinst-distri-opensuse
- Abort the test with success as far as we can reach in a normal flow
Updated by mgriessmeier almost 7 years ago
- Follows action #33223: [sle][functional][virtualization][s390-kvm][s390x][tools][u][research] Learn how to use snipl to install and configure an LPAR added
Updated by mgriessmeier almost 7 years ago
- Follows action #33232: Execute useful LPAR installation testcases in the QE core job group added
Updated by mgriessmeier almost 7 years ago
- Follows deleted (action #33232: Execute useful LPAR installation testcases in the QE core job group)
Updated by mgriessmeier almost 7 years ago
- Precedes action #33232: Execute useful LPAR installation testcases in the QE core job group added
Updated by mgriessmeier almost 7 years ago
- Due date changed from 2018-05-22 to 2018-04-10
- Start date changed from 2018-04-25 to 2018-03-28
Updated by riafarov over 6 years ago
- Assignee set to mgriessmeier
@mgriessmeier, I believe this is an epic, could you please split it and we will schedule first part for the next sprint? Or if you think we can deliver it in the next sprint, set it workable.
Updated by nicksinger over 6 years ago
- Copied to action #33916: Implement simple backend which uses snipl/qnipl for automated LPAR installation added
Updated by nicksinger over 6 years ago
- Copied to deleted (action #33916: Implement simple backend which uses snipl/qnipl for automated LPAR installation)
Updated by nicksinger over 6 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u] Adapt the backend and add a simple testsuite which is able to interact with our zHMC and can control a LPAR via snipl cli to [sle][functional][virtualization][s390-kvm][s390x][tools][u] Add a simple testsuite which uses the "new" LPAR backend
- Description updated (diff)
- Due date changed from 2018-04-10 to 2018-04-24
- Assignee deleted (
mgriessmeier)
Updated by nicksinger over 6 years ago
- Precedes deleted (action #33232: Execute useful LPAR installation testcases in the QE core job group)
Updated by nicksinger over 6 years ago
- Precedes action #33232: Execute useful LPAR installation testcases in the QE core job group added
Updated by nicksinger over 6 years ago
- Follows action #33916: Implement simple backend which uses snipl/qnipl for automated LPAR installation added
Updated by nicksinger over 6 years ago
- Due date changed from 2018-05-08 to 2018-04-24
Updated by mgriessmeier over 6 years ago
riafarov wrote:
@mgriessmeier, I believe this is an epic, could you please split it and we will schedule first part for the next sprint? Or if you think we can deliver it in the next sprint, set it workable.
splitted into two tickets, made this one workable and planned for this sprint
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u] Add a simple testsuite which uses the "new" LPAR backend to [sle][functional][virtualization][s390-kvm][s390x][tools][u][medium] Add a simple testsuite which uses the "new" LPAR backend
- Description updated (diff)
- Due date changed from 2018-04-24 to 2018-05-08
- Status changed from New to Workable
Probably we won't be able to finish the precursor within S14 so shifting this one back a bit further, mgriessmeier is fine with that - he did not become emotionally attached, yet ;)
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-05-08 to 2018-05-22
- Start date changed from 2018-04-11 to 2018-04-25
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-05-22 to 2018-06-19
- Start date changed from 2018-04-25 to 2018-05-23
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 15 to Milestone 17
- Start date deleted (
2018-05-23)
see preceeding ticket
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-06-19 to 2018-07-17
- Start date changed from 2018-06-06 to 2018-07-04
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-07-17 to 2018-07-31
- Start date changed from 2018-07-04 to 2018-07-18
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-07-31 to 2018-08-28
- Start date changed from 2018-07-18 to 2018-08-15
due to changes in a related task
Updated by okurz over 6 years ago
- Due date changed from 2018-08-28 to 2018-11-06
- Start date changed from 2018-08-15 to 2018-10-24
due to changes in a related task
Updated by okurz over 6 years ago
- Target version changed from Milestone 18 to Milestone 20
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-11-06 to 2018-03-28
- Start date changed from 2018-10-24 to 2018-03-15
due to changes in a related task
Updated by okurz about 6 years ago
- Due date deleted (
2018-11-06) - Target version changed from Milestone 20 to future
Updated by okurz about 6 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
-> #33916
Updated by okurz almost 6 years ago
- Start date changed from 2018-10-24 to 2020-01-01
due to changes in a related task
Updated by okurz over 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by SLindoMansilla over 4 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][u][medium] Add a simple testsuite which uses the "new" LPAR backend to [sle][functional][virtualization][s390-kvm][s390x][tools][medium] Add a simple testsuite which uses the "new" LPAR backend
Updated by okurz about 4 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][tools][medium] Add a simple testsuite which uses the "new" LPAR backend to [sle][functional][virtualization][s390-kvm][s390x][medium] Add a simple testsuite which uses the "new" LPAR backend
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 mgriessmeier 6 months ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][medium] Add a simple testsuite which uses the "new" LPAR backend to Add a simple testsuite which uses the planned LPAR backend
(updated subject)