Running gather scripts in background

[OdedViner]

The collection scripts can be executed in parallel to save time when running the MG.

Process:
1.Running gather scripts in parallel
2.Waiting for the subprocesses to finish execution.

Release note:

[kubevirt-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sradco for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: OdedViner
Once this PR has been reviewed and has the lgtm label, please assign sradco for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @OdedViner. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nunnatsa]

What is the reason for this change? Could you please add more details?

My concern is that running the scripts on parallel on very large clusyers, with 100s of VMs, my causr unexpected results.

[OdedViner]

What is the reason for this change? Could you please add more details?

My concern is that running the scripts on parallel on very large clusyers, with 100s of VMs, my causr unexpected results.

Hi @nunnatsa,
What is the reason for this change? -->I want to reduce the MG runtime.
My concern is that running the scripts on parallel on very large clusyers, with 100s of VMs, my causr unexpected results. --> I agree with you. we need to test it.

I created a private image quay.io/oviner/ocs-must-gather:kubevirt_mg to test it.

We can compare the must-gather runtime like here openshift/must-gather#399

time oc adm must-gather --image=quay.io/kubevirt/must-gather -- /usr/bin/gather
....
time oc adm must-gather --image=quay.io/oviner/ocs-must-gather:kubevirt_mg -- /usr/bin/gather

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale