Investigation of moving B@D to containers
Issue Background
kernelci has docker containers for kernelci and LAVA there needs to be an investigation of moving our B@D environment to these containers
Issue description
Changes necessary
-
In lava-docker, substitute our own health check getting the build location from the kernelci container -
In lava-docker, install expect and provide our own login script -
Provide required versions of utilities (I need to get docker-compose from pip) -
Script the means of installing the api token in kernelci-build (it needs changing each time the container is started. -
Document how to add the builds to kernelci if the container is restarted (eg if the host is rebooted) - does this affect the above point? -
Solve the network breaking during the provisioning (not sure this is necessary if next point is addressed) -
Merge lava-docker into kernelci-docker's swarm -
Add licence headers to most of the files -
Provide overall script to start both containers (git submodules?) -
Provide means of building initramfs - buiild on host and copy into kernelci-docker at provisioning. -
Merge FILE_SERVER_URL fix into kernelci so getting the builds works. -
Create mechanism for updating health check to use the most recent build of kernel - needs to behave differently(?) depending on whether lava-docker is running or not (though if we're always running both docker images this may not be true!) -
Give lava-docker a history as kernelci-docker has? -
Consider how to handle email notifications.
Edited by Robert Marshall