Before publishing a vizier release, there is a set of checks performed to acceptance test a pre release. A subset of these can be seen in the screenshot below:
It would be great if a portion of these steps could be automated to reduce the time it takes to release a new vizier.
One option for automating this is to leverage the perf_tool used for testing Pixie's performance. It has primitives for automating the deployment of a vizier, workloads to stress Pixie and pxl scripts for validation.
I believe that this framework is flexible enough to create workloads that would cover portions of the release checklist and would reduce the manual work to test a pre release.
Before publishing a vizier release, there is a set of checks performed to acceptance test a pre release. A subset of these can be seen in the screenshot below:
It would be great if a portion of these steps could be automated to reduce the time it takes to release a new vizier.
One option for automating this is to leverage the perf_tool used for testing Pixie's performance. It has primitives for automating the deployment of a vizier, workloads to stress Pixie and pxl scripts for validation.
I believe that this framework is flexible enough to create workloads that would cover portions of the release checklist and would reduce the manual work to test a pre release.