You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a scenario where the test must be run on multiple HMC console, one such example is LPAR migration from soruce HMC to destination HMC and it requires op-test framework to handle multi HMC console thread to migrate lpar from cec1 in hmc1 to cec2 in hmc2 and viceversa
the current op-test implmentation takes one HMC input details as part of system configuration and we need enhancement to make sure multiple hmc threads are created to perform cross hmc tests which will pave way to add more corss HMC testcases into optests
My initial take to solve this is to first explore if same hmc code can be resued at the test code to create separate HMC console obj and use it to monitor LPM
Or
Enhance op-test configuration to accept both source and destination HMC inputs
This feature request is opened to solve this in a best possible way, all suggestions are welcome if any ?
The text was updated successfully, but these errors were encountered:
In a scenario where the test must be run on multiple HMC console, one such example is LPAR migration from soruce HMC to destination HMC and it requires op-test framework to handle multi HMC console thread to migrate lpar from cec1 in hmc1 to cec2 in hmc2 and viceversa
the current op-test implmentation takes one HMC input details as part of system configuration and we need enhancement to make sure multiple hmc threads are created to perform cross hmc tests which will pave way to add more corss HMC testcases into optests
My initial take to solve this is to first explore if same hmc code can be resued at the test code to create separate HMC console obj and use it to monitor LPM
Or
Enhance op-test configuration to accept both source and destination HMC inputs
This feature request is opened to solve this in a best possible way, all suggestions are welcome if any ?
The text was updated successfully, but these errors were encountered: