Hi All, Following the demo session presented today, here you can find the 'OST 101' presentation: https://docs.google.com/presentation/d/1zMhiKHQaA5VPtgGl7lDiqamAkFqIf3rjMWRT-BhE-Rw/edit?usp=sharing
Feel free to share your feedback/comments with me. *Regards,* *Shani Leviim* On Tue, Jul 27, 2021 at 4:44 PM Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > > On 27. 7. 2021, at 14:53, Arik Hadas <aha...@redhat.com> wrote: > > > > On Tue, Jul 27, 2021 at 2:57 PM Michal Skrivanek < > michal.skriva...@redhat.com> wrote: > >> Hi, >> we worked for a while on removing our dependency on lago that has been >> more or less abandoned for a long time now. We got to the minimal feature >> set that is simple to replace with bunch of virsh commands, and most of the >> advanced logic is implemented in pytest. We’ve just merged the last patches >> that freed us up from lago for local and beaker CI runs. >> >> There’s a new ost.sh wrapper for the simple operations of running the >> suite, inspecting the environment and shutting it down. >> Hopefully it’s self explanatory…. >> >> ./ost.sh command [arguments] >> >> run <suite> <distro> [<pytest args>...] >> initializes the workspace with preinstalled distro ost-images, >> launches VMs and runs the whole suite >> add extra repos with --custom-repo=url >> skip check that extra repo is actually used with >> --skip-custom-repos-check >> status >> show environment status, VM details >> shell <host> [command ...] >> opens ssh connection >> console <host> >> opens virsh console >> destroy >> stop and remove the running environment >> > >> Right now lago and run_suite.sh still works and it is still used by the >> mock-based jenkins.ovirt.org runs. It will go away in future. >> > > nice > so if run_suite.sh is deprecated, how about replacing it in the > documentation with that new thingy? > > > yeah yeah, sure. it’s not gone yet, it’s now just two (almost) same > configs and run methods > > > >> >> Thanks, >> michal >> _______________________________________________ >> Devel mailing list -- devel@ovirt.org >> To unsubscribe send an email to devel-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WJMNDQR5QNRQIJ64KUGTS3NXZJTA2MGN/ > > > _______________________________________________ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JSNKLB3GPPCK2PMOWDTPF7Z2V2MHEXAB/ >
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XB4YSP3VQ2ENYP6ZF7AEGHCVHYNYGM6K/
