action #33916
opencoordination #28630: [qe-core] setup for LPAR installation (manual + automatic)
coordination #28869: [epic] Automated installation on s390x LPAR through zHMC & integration into openQA
Implement simple backend which uses snipl/qnipl for automated LPAR installation
Added by nicksinger over 6 years ago. Updated 24 days ago.
0%
Description
User story¶
There is a cli tool called snipl (Simple Network IPL), which can be used to communicate with the zHMC from the console.
We already did a field tests of this tool and are ready now to implement a first, small openQA backend similar to the spvm backend.
Acceptance criteria¶
- AC1: Simple backend which interacts with given LPARs
- AC2: Upstream documentation of this backend
Updated by nicksinger over 6 years ago
- Copied from action #33226: Add a simple testsuite which uses the planned LPAR backend added
Updated by nicksinger over 6 years ago
- Copied from deleted (action #33226: Add a simple testsuite which uses the planned LPAR backend)
Updated by nicksinger over 6 years ago
- Project changed from openQA Tests to 46
- Category deleted (
Infrastructure) - Target version deleted (
Milestone 15) - Parent task set to #28869
Updated by nicksinger over 6 years ago
- Precedes action #33226: Add a simple testsuite which uses the planned LPAR backend added
Updated by mgriessmeier over 6 years ago
not touched this sprint, due to unforeseen Issues and reduced capacity
Updated by mgriessmeier over 6 years ago
- Due date changed from 2018-04-10 to 2018-04-24
Updated by okurz over 6 years ago
- Due date changed from 2018-04-24 to 2018-05-22
- Target version changed from Milestone 15 to Milestone 16
not enough capacity in S15 nor S16
Updated by mgriessmeier about 6 years ago
okurz wrote:
not enough capacity in S15 nor S16
same for S17, suggesting to move to a date after SLE15 is released
Updated by okurz about 6 years ago
- Due date changed from 2018-05-22 to 2018-06-05
- Start date deleted (
2018-03-28)
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-06-05 to 2018-07-03
- Target version changed from Milestone 16 to Milestone 17
Updated by okurz about 6 years ago
- Due date changed from 2018-07-03 to 2018-07-17
Let's try to do this after #33340 for powerVM which we see related.
Updated by riafarov about 6 years ago
- Due date changed from 2018-07-17 to 2018-08-14
Updated by okurz about 6 years ago
- Target version changed from Milestone 17 to Milestone 18
Updated by okurz about 6 years ago
- Due date changed from 2018-08-14 to 2018-10-23
- Target version changed from Milestone 18 to Milestone 20
We do not have ressources available. We expect the new mainframe to be available after 2018-08 and let's plan after next vacations.
Updated by okurz almost 6 years ago
@mgriessmeier WDYT, how does the mainframe frontline look like as of now?
Updated by mgriessmeier almost 6 years ago
- Due date deleted (
2018-10-23) - Target version changed from Milestone 20 to Milestone 22
we've got available resources last week, so there is at least one lpar which can be used for this purpose.
Updated by mgriessmeier over 5 years ago
- Subject changed from [sle][functional][virtualization][s390-kvm][s390x][hard][u] Implement simple backend which uses snipl/qnipl for automated LPAR installation to [sle][functional][virtualization][s390x][hard][u] Implement simple backend which uses snipl/qnipl for automated LPAR installation
deleted [s390-kvm] from title
Updated by okurz over 5 years ago
- Blocked by coordination #37339: [qe-core][functional][saga][epic][ipmi] Stable testing on IPMI backend including x11 tests added
Updated by okurz over 5 years ago
- Status changed from Workable to Blocked
- Assignee changed from mgriessmeier to okurz
Updated by xlai over 5 years ago
@okurz, as you may know, leon is also working on automating virtualization tests on s390x. However he is blocked by the situation that the svirt backend on s390 does not support to get serial output, so assert_script_run, script_output apis are not supported -- quoted leon, please correct me if I am wrong.
So he is looking for other backend. Do you think this planned new backend can support the need to get output from sut?
Updated by okurz over 5 years ago
xlai wrote:
@okurz, would you please help to explain why s390 task blocked by ipmi backend issue ?
[…] So he is looking for other backend. Do you think this planned new backend can support the need to get output from sut?
I think with this we might have an explanation for the "blocking" ;) I set the "blocked" status considering that to my understanding we need to solve the same problems properly for all backends. Based on my priority assessment I planned within the team QSF to solve our requirements for IPMI first in a proper way and then extend it for s390x. We appreciate any help to cleanup the current implementation according to the chain of tickets. However, the perfectly valid alternative is to go further with this ticket here regardless of the status of IPMI.
Updated by xlai over 5 years ago
okurz wrote:
xlai wrote:
@okurz, would you please help to explain why s390 task blocked by ipmi backend issue ?
[…] So he is looking for other backend. Do you think this planned new backend can support the need to get output from sut?
I think with this we might have an explanation for the "blocking" ;) I set the "blocked" status considering that to my understanding we need to solve the same problems properly for all backends. Based on my priority assessment I planned within the team QSF to solve our requirements for IPMI first in a proper way and then extend it for s390x. We appreciate any help to cleanup the current implementation according to the chain of tickets. However, the perfectly valid alternative is to go further with this ticket here regardless of the status of IPMI.
Thanks for the explanation of "block", reasonable from this way then.
Would you please also answer the other question that whether this planned new backend can support the need to get output from sut?
Updated by okurz over 5 years ago
xlai wrote:
Would you please also answer the other question that whether this planned new backend can support the need to get output from sut?
Yes, I consider this a mandatory part of the backend. If not part of this ticket then at least within the parent ticket saga #28630
Updated by xlai over 5 years ago
okurz wrote:
xlai wrote:
Would you please also answer the other question that whether this planned new backend can support the need to get output from sut?
Yes, I consider this a mandatory part of the backend. If not part of this ticket then at least within the parent ticket saga #28630
Great! Thank you! Look forward to this new special backend for s390x automation test.
Updated by okurz over 5 years ago
- Priority changed from High to Normal
- Target version changed from Milestone 22 to Milestone 25+
Blocker #37339 is not expected to be done before M25 so delaying this one accordingly
Updated by mgriessmeier over 5 years ago
Updated by mgriessmeier about 5 years ago
- Target version changed from Milestone 25+ to Milestone 26
Updated by okurz about 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 mgriessmeier almost 5 years ago
- Target version changed from Milestone 26 to Milestone 29
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 29 to Milestone 35+
Updated by SLindoMansilla about 4 years ago
- Subject changed from [sle][functional][virtualization][s390x][hard][u] Implement simple backend which uses snipl/qnipl for automated LPAR installation to [sle][virtualization][s390x][hard] Implement simple backend which uses snipl/qnipl for automated LPAR installation
Updated by szarate about 2 years ago
- Target version changed from Milestone 35+ to future
Updated by mgriessmeier 24 days ago
- Subject changed from [sle][virtualization][s390x][hard] Implement simple backend which uses snipl/qnipl for automated LPAR installation to Implement simple backend which uses snipl/qnipl for automated LPAR installation
(updated subject)