Add network isolation support
Les mainteneurs répondent en général sous 2 jours
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 25/100
- Type d'issue
- Fonctionnalité
- Clarté
- Plutôt claire
- Activité
- À l'abandon
- Stack technique
- rust
- Domaine
- infrastructure, networking
Piste de recherche
Start by reading the bcvk VM provisioning and networking code, especially the libvirt integration and the existing bcvk libvirt ssh path; the issue does not name specific files or tests. Determine how to block guest outbound access while preserving host-to-VM connectivity, and account for how staged resources could later be exposed. Done means the VM cannot reach arbitrary internet services while host SSH access still works; linked pull request #311 is already open.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
(This issue is meant to describe the problem, sketch out requirements, and propose one or more solution(s) in order to be fed into a LLM for initial implementation)
Currently bootc tmt integration tests run inside of a bcvk-provisioned VM. However, this VM has general network access to the outside world. That means the test environment can pull arbitrary data at execution time. We are currently trying to reduce the number of testing flakes in bootc CI. A common source of error is the tests pulling container images from quay.io from inside of the VM. This is problematic because it may be many hours into a CI run before a given test is run and encounters a flake, which invalidates the hours of testing that happened beforehand. It should be noted that although quay.io flakes are the most common, there are other flakes both known and unknown that can also occur from within network-enabled test runners.
The general idea then is to enable support in bcvk to disable as much network as possible. Probably it is sufficient to disable outbound routing from the VM, but other options such as manipulating firewall rules could be considered as well. Care must be taken to ensure connectivity between the host and VM is preserved; for example it should still be possible to bcvk libvirt ssh into the VM from the host, but once inside the VM it should not be possible to connect to arbitrary services on the internet.
A followup to this is to pre-stage any required resources on the test runner host (container images, packages, etc.) and expose those resources into the VM. The network isolation support implementation should take into consideration how those resources are exposed to the VM. I suspect that will likely be handled directly on the filesystem via virtiofs, but it could also be feasible to expose network resources from the host onto the VM. As an example, maybe container images are pulled into the host containers-storage, and then the host re-exports those to the VM via a container registry which is reachable via the local network.
This would make the test execution environment more hermetic and similar to something like mock where the inputs (source, spec, buildroot) are populated at the beginning, and then once the build executes it does not have network access.
This a forcing function to make sure all testing inputs are accounted for beforehand. It should greatly cut down on the number of network failures that happen deep into CI runs. If all needed resources are collected at the beginning of the CI pipeline, this means that any flakes or outages in dependent services will be encountered early and should hopefully cause the pipeline to fail on the order of minutes, instead of hours. It also gives us a common place to implement retry logic in order to tolerate transient network errors.
- Langage dominant
- Rust
- Étoiles
- 142
- Forks
- 40
- Merge moyen
- 2 j 22 h
- PR mergées (30 j)
- 10
Préparer son environnement
Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Aucun guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de bootc-dev/bcvk
-
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
Les mainteneurs répondent en général sous 2 jours
-
Image cache ignores --disk-sizeOuverte
Difficulté 3/5 Une demi-journée Accessibilité débutants 45/100
bootc-dev/bcvk#416 · 1 commentaire ·
Les mainteneurs répondent en général sous 2 jours
-
Difficulté 3/5 Une demi-journée Accessibilité débutants 50/100
Les mainteneurs répondent en général sous 2 jours
-
extend host testingOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 43/100
Les mainteneurs répondent en général sous 2 jours
-
Add `to-containerdisk`Ouverte
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 35/100
bootc-dev/bcvk#386 · 1 réaction ·
Les mainteneurs répondent en général sous 2 jours
Toutes les issues de bootc-dev/bcvk
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 62/100
eventflux-io/eventflux#203 ·
Les mainteneurs répondent en général sous 1 jour
-
bug ui
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
userFRM/egui-charts#4068 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 82/100
trezor/trezor-firmware#8357 ·
Les mainteneurs répondent en général sous 2 jours
-
fuzz-crash review-followup
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour