c7ebfeadc6
Often our tests are based on kuryr/demo. That image used to be based on
python and alpine and was taking a very long time to pull for already
slow tests. This change makes this repository have the authoritative
version of the kuryr/demo build.
The way it is built is just by running mkrootfs.sh. But that only needs
to be run if we change the version of curl or modify server.go.
Otherwise, to run test it just needs:
docker build -t kuryr/demo . -f Dockerfile
This build will not need to go to Docker Hub for anything so we also
eliminate one source of flakiness.
Depends-On: https://review.openstack.org/#/c/547390/
Change-Id: Iab5799e22c3b353a4f2adbaa280ab4a9904ecd95
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
1.8 KiB
Kuryr Testing container infrastructure
This directory is the official source for building Docker hub's kuryr/demo images.
The build consists on two parts:
Builder container
The builder container is based on the musl compiled Alpine distribution. In the process of building the image, it downloads and compiles:
- busybox
- musl
- curl and its dependencies
It also includes golang so that we can use it in our test web server:
- server.go
Everything that is to be included in the kuryr/demo image is put in:
/usr/src/busybox/rootfsThe reason for this is that this build is based on Docker's busybox build system and the rootfs won't have any library, so all you want to add must be statically compiled there.
kuryr/demo container
This is the actual container used in the tests. It includes:
- Busybox: It gives us a very lightweight userspace that provides things like the ip command, vi, etc.
- curl: Useful for testing HTTP/HTTPS connectivity to the API and other services.
- helloserver: An HTTP server that binds to 8080 and prints out a message that includes the hostname, so it can be used to see which pod replies to a service request.
When and how to build
builder container + kuryr/demo
You should only need to build the whole set if you want to change the library app version of something in kuryr/demo or add another tool like bind9 dig.
The way to do this is:
sudo ./mkrootfs.shkuryr/demo
Everytime you want to run the tests, you should build the kuryr/demo container locally to avoid pulls from dockerhub to make sure you run the latest authoritative version.
Note that the kuryr-tempest-plugin devstack will build it for you.