KubevirtCI rewrite draft

[aerosouund]

What this PR does / why we need it:

Which issue(s) this PR fixes

https://github.com/kubevirt/kubevirtci/issues/1185

Checklist

• [ ] Design: A design document was considered and is present (link) or not required
• [x] PR: The PR description is expressive enough and will help future contributors
• [x] Code: Write code that humans can understand and Keep it simple
• [x] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• [ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• [ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• [ ] Community: Announcement to kubevirt-dev was considered

[kubevirt-bot]

Hi @aerosouund. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) 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 davidvossel 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](https://github.com/kubevirt/kubevirtci/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[dhiller]

/uncc /cc @alicefr @xpivarc

Since you folks were pinged on the issue, I suspect you have been talking to @aerosouund .

[dhiller]

/uncc @davidvossel

[alicefr]

/cc @acardace

[dhiller]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• c907392 Network (Fix argument passing to qemu process #1)
• 3c11b47 ignore vendor
• 18c3a41 ignore vendor
• f4f7e83 dont diff vendor
• 469d3ff delete vendor directory
• 35aaeaa add vendor dir
• b57a472 no changes to vendor

@aerosouund we only accept signed commits. You need to rework each of the commits to have proper signing.

[alicefr]

@aerosouund on top of what Daniel said, please try to split the code in clean separated commits with some explanation. Even if this is a draft, it is, otherwise, difficult to review and understanding what you are doing.

[aerosouund]

@dhiller Of course, i am just keeping this as a pull request where you guys can just see the code. eventually i will clean up everything properly @alicefr will do

[kubevirt-bot]

PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.