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
IS had a request to test some Z LPAR or VM instancecs using testflinger. It's not a common use case but we probably should have some Z assets accessible via testflinger too. This is not something we can set up using the cert lab testflinger, as that resides in a completely different VLAN and infrastructure.
We'll need, at minimum:
1: A testflinger agent setup running nearby to control Z LPAR and zVM instances
2: a connector that can manage Z assets to start, stop, and deploy them.
To manage the Z instances I expect that access would be needed to the machine that manages the Z stuff as well
The text was updated successfully, but these errors were encountered:
IS had a request to test some Z LPAR or VM instancecs using testflinger. It's not a common use case but we probably should have some Z assets accessible via testflinger too. This is not something we can set up using the cert lab testflinger, as that resides in a completely different VLAN and infrastructure.
We'll need, at minimum:
1: A testflinger agent setup running nearby to control Z LPAR and zVM instances
2: a connector that can manage Z assets to start, stop, and deploy them.
To manage the Z instances I expect that access would be needed to the machine that manages the Z stuff as well
The text was updated successfully, but these errors were encountered: