Context

Tezt-cloud setup relies mostly on docker images running SSH servers. While this setup has proved to be very powerful, this is not suited for production or to test other setups relying on: systemd, docker-compose, docker swarm, ...

Besides, following the work conducted by the DAL team, the orchestrator run by tezt-cloud has some limitations like too verbose.

People

@baugr

Deliverables

• Tezt-cloud can run processes on a VM without going through a docker image
• Tezt-cloud integrates logrotate
• Tezt-cloud should be ready for running processes under systemd
• Tezt-cloud is more resilient

Work breakdown

• (@Saroupille @baugr , days) Names of agents are now static !16121 (merged)
• (@Saroupille, @baugr, hours) Move the configuration into its own datatype (!16130 (closed), !16252 (merged))
• (@baugr , days) Prometheus process export in Tezt-cloud !15997 (closed) !16220 (merged) - depends on !16319 (merged)
• (@baugr) Provisionning via ssh (!16747 (closed))
• (@baugr) Tezt-cloud integrates logrotate (!17166 (merged))
• (@baugr) add manual provisioning for docker containers
• [ ] progressively delete requirement on terraform, handling state
• (@Saroupille @baugr , days) Introduce a configuration file for tezt-cloud !16143 (closed)
• (@baugr, hours) Introduce predefined deployment scenario
• (@Saroupille @baugr , days) Provisioning is not docker by terraform anymore !16117 (closed)
• [ ] (@baugr , days) Use terraform refresh to repair the terraform state
• (@baugr, days) Backend of tzkt is in tezt-cloud
• (@baugr) add raw execution (without docker)

2025-02-27: updated timeline and breakdown