On Mon, 2018-03-26 at 21:12 +0200, Bastian Blank wrote: > On Sun, Mar 25, 2018 at 10:15:49PM +0200, Tomasz Rybak wrote: > > What do you mean by that? > > I've recently been thinking about how to test our images, > > and how to integrate test we've been working on during > > the spring; haven't come to any solutions yet, though. > > Okay, let's outline my solution, which I didn't test yet. For the > official builds all this stuff runs in kvm instances with nested-vmx > on > casulana. > > - Each test runs in a disposable Docker environment. > > This means we have a completely scripted test environment. This > means > less chance that documentation and implementation gets out of sync. > Or just work against someone changing stuff by hand. > > - It sets up a complete network: > - a bridge, > - some NAT for pretty controlled access to the outside, > - dns, dhcpv4 and dhcpv6 server (lets see if dnsmasq works > properly), > - a mock metadata server for the tested plattform. > > - It starts the image with kvm. > > - It can then run the rest of the tests. Seems reasonable. OK, it's time to start thinking about integrating our tests. It looks like now we have 3 testing solutions: 1. yours 2. one by Thomas (zigo) 3. one that we were working on during last sprint: https://salsa.debian.org/cloud-team/debian-cloud-tests Have you written some code already? If so, where is it? I'll try to gather all the information about our existing testing solutions and send some summary to the list. Best regards. -- Tomasz Rybak, Debian Developer GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C
Attachment:
signature.asc
Description: This is a digitally signed message part