action #12804
closed
[qe-core][functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :)
Added by okurz over 8 years ago.
Updated 8 months ago.
Category:
Enhancement to existing tests
- Description updated (diff)
- Category set to Enhancement to existing tests
- Subject changed from Do more easy to debug tests by using chroot installations to [sles][opensuse][installation] Do more easy to debug tests by using chroot installations
- Subject changed from [sles][opensuse][installation] Do more easy to debug tests by using chroot installations to [functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations
- Target version set to future
- Subject changed from [functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations to [functional][u][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :)
I think by now containers are the way to go :)
- Related to action #20246: [gsoc] Investigate/implement container-based backend added
- Target version changed from future to Milestone 21
Shortly discussed with slindomansilla. What we think might be feasible and useful is to conduct one of the existing test modules from openQA scenarios like "textmode" within a container. This would fit in somewhere between tests in OBS like https://build.opensuse.org/project/show/home:okurz:test-packagehub and the openQA installation scenarios. The quickmost dirty approach is probably when we boot any existing (older, stable) OS disk image, install docker in there, pull the latest published image of the product to test, add more current repos with SUSEConnect/zypper, register, install and conduct a simple test. However, this sounds a bit wasteful as we would need to boot a VM to conduct a container based test within. I feel we really should use gitlab CI instead. Maybe one micro-app that listens to AMQP OBS events and on new publications of the products we test trigger a container based CI test in a gitlab project.
- Target version changed from Milestone 21 to future
- Status changed from New to Workable
- Priority changed from Normal to Low
- Estimated time set to 42.00 h
- Subject changed from [functional][u][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :) to [qe-core][functional][sles][opensuse][installation] Do more easy to debug tests by using chroot installations … or containers :)
- Tags set to qecore-cleanup
- Status changed from Workable to Rejected
Like the idea of using containers when possible instead of full SLE installation. But when we sell the full SLE installation I feel like it should be fully tested. (Adding more containers test is a great idea, which I guess we have in public cloud squad).
Anyhow. This topic is rotting since 8 years. Please re-create one with updated info if you feel is still current
If you buy into the idea then please don't reject that ticket but update it to your liking.
Also available in: Atom
PDF