[tripleo][validations] new Validation Framework demos
Hey TripleO,
I have recorded three demos with the new Validation Framework (VF): 1st demo is similar to what Gael did few months ago but with the new code refactored (validations-libs/validations-common projects): https://asciinema.org/a/NRLULghjJa87qxRD9Nfq0FYoa
2nd demo is a use of the VF without any openstack/TripleO prerequisite, on a fresh and empty Ubuntu docker container, with only validations-libs and validations-common projects. It shows that only with a apt-get install git and python3-pip and with a basic python project installation we can run validations and use the framework: https://asciinema.org/a/2Jp9LZbN0xhJAR09zIpI6OpuB
So it can answer a few demands such as: How to run validations as prep undercloud installation ? How to run validations on a non-openstack project ? What are the bare minimum requirements for being able to run Validations on a system ? May I run Validation remotely from my machine ? etc...
The third one is mainly related to the deployment itself of TripleO. By using a simple PoC (https://review.opendev.org/#/c/724289/), I was able to make TripleO consuming the validations-libs framework and validation logging callback plugin. So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage. https://asciinema.org/a/344484 https://asciinema.org/a/344509
Mathieu.
On Wed, Jul 1, 2020 at 9:07 AM Mathieu Bultel mbultel@redhat.com wrote:
Hey TripleO,
I have recorded three demos with the new Validation Framework (VF): 1st demo is similar to what Gael did few months ago but with the new code refactored (validations-libs/validations-common projects): https://asciinema.org/a/NRLULghjJa87qxRD9Nfq0FYoa
2nd demo is a use of the VF without any openstack/TripleO prerequisite, on a fresh and empty Ubuntu docker container, with only validations-libs and validations-common projects. It shows that only with a apt-get install git and python3-pip and with a basic python project installation we can run validations and use the framework: https://asciinema.org/a/2Jp9LZbN0xhJAR09zIpI6OpuB
So it can answer a few demands such as: How to run validations as prep undercloud installation ? How to run validations on a non-openstack project ? What are the bare minimum requirements for being able to run Validations on a system ? May I run Validation remotely from my machine ? etc...
The third one is mainly related to the deployment itself of TripleO. By using a simple PoC (https://review.opendev.org/#/c/724289/), I was able to make TripleO consuming the validations-libs framework and validation logging callback plugin. So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage. https://asciinema.org/a/344484 https://asciinema.org/a/344509
Mathieu.
Thanks for posting these Mathieu! This helps to visualize some of the topics discussed at the PTG.
I like a lot of what I see here and I can see the value it will bring. I have some minor questions about the format of the logs.. like each task has TIMING in bold. Silly stuff like that. Looking forward to looking at this more in depth.
Thank you!
Hey Mathieu, others,
On Wed, Jul 1, 2020 at 11:07 AM Mathieu Bultel mbultel@redhat.com wrote:
So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage.
https://asciinema.org/a/344484
Thank you for running with this. Based on your work, I've put together a Vagrantfile to allow developers to get up to speed very quickly with a working validations environment. This is a minimal environment and is not TripleO dependent, meaning it's very light, and ready to go in seconds.
I can see that this might grow as we think of other tooling required to be productive, so does anyone have any interest in me pushing it ot a repo somewhere, and if so, where would be most suitable?
Cheers, David
On Mon, Sep 28, 2020 at 8:47 PM David Peacock dpeacock@redhat.com wrote:
Hey Mathieu, others,
On Wed, Jul 1, 2020 at 11:07 AM Mathieu Bultel mbultel@redhat.com wrote:
So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage.
https://asciinema.org/a/344484
Thank you for running with this. Based on your work, I've put together a Vagrantfile to allow developers to get up to speed very quickly with a working validations environment. This is a minimal environment and is not TripleO dependent, meaning it's very light, and ready to go in seconds.
I can see that this might grow as we think of other tooling required to be productive, so does anyone have any interest in me pushing it ot a repo somewhere, and if so, where would be most suitable?
Thank you very much David, I think you can push your work in validations-libs. I will probably push a DockerFile as well. Those kinds of files are really nice to allow people to hack the framework in a few minutes without getting a very huge and complex deployment.
Cheers, David
Hi Mathieu!
I just checked the demo videos and I have a quick question.
Is it possible to put them in somehow that we can upload them to the TripleO youtube channel?
Thanks, Carlos. On Tue, Sep 29, 2020 at 11:40 AM Mathieu Bultel mbultel@redhat.com wrote:
On Mon, Sep 28, 2020 at 8:47 PM David Peacock dpeacock@redhat.com wrote:
Hey Mathieu, others,
On Wed, Jul 1, 2020 at 11:07 AM Mathieu Bultel mbultel@redhat.com wrote:
So it shows in this demo how the deploy steps playbook can be logged, parsed and shown with the VF CLI. This can be improve, modify & so on of course... it's basic usage.
https://asciinema.org/a/344484 https://asciinema.org/a/344509
Thank you for running with this. Based on your work, I've put together a Vagrantfile to allow developers to get up to speed very quickly with a working validations environment. This is a minimal environment and is not TripleO dependent, meaning it's very light, and ready to go in seconds.
I can see that this might grow as we think of other tooling required to be productive, so does anyone have any interest in me pushing it ot a repo somewhere, and if so, where would be most suitable?
Thank you very much David, I think you can push your work in validations-libs. I will probably push a DockerFile as well. Those kinds of files are really nice to allow people to hack the framework in a few minutes without getting a very huge and complex deployment.
Cheers, David
On Tue, Sep 29, 2020 at 5:31 AM Mathieu Bultel mbultel@redhat.com wrote:
I can see that this might grow as we think of other tooling required to be
productive, so does anyone have any interest in me pushing it ot a repo somewhere, and if so, where would be most suitable?
I think you can push your work in validations-libs. I will probably push a DockerFile as well. Those kinds of files are really nice to allow people to hack the framework in a few minutes without getting a very huge and complex deployment.
Thanks - excelllent - done.
https://review.opendev.org/#/c/754975/
I also added a section to the readme to highlight - not sure if that's appropriate there but I figure usage wouldn't hurt and that's a home for future bootstrapping items like Dockerfiles etc.
Thanks
participants (4)
-
Carlos Camacho Gonzalez
-
David Peacock
-
Mathieu Bultel
-
Wesley Hayutin