Will Foster

> Super helpful to set expectations, thanks Will! Hey for sure, no problem. Better to set a target we're pretty sure we can hit and then start profiling and looking...

Hey Joe, this is how it'll likely work. > Thanks @grafuls -- so for our BM CPT we will focus on 2 paths I assume > > 1. Pass our...

Moving efforts here to `development` branch, first WIP patchset: https://review.gerrithub.io/c/redhat-performance/quads/+/1204959

We have started testing self-scheduling internally, please find us via the normal mechanisms if you'd like to try it out.

Released issues including upstream OpenShift uses: related: https://github.com/openshift/release/pull/61192 related: https://github.com/redhat-performance/quads/issues/568 related: https://github.com/redhat-performance/quads/issues/567 related: https://github.com/redhat-performance/quads/issues/460

Potentially in-scope RFE to support sliding window of self-scheduled assignment lifetime relative to a configured cut-off day - related: https://github.com/redhat-performance/quads/issues/571

For this to be implemented we need https://github.com/redhat-performance/quads/issues/452 completed first.

FWIW there's two additional ways to get this information, though I think the old functionality should be restored. * via `--ls-schedule` ``` quads --ls-schedule --host e33-h15-000-r650.rdu2.example.com | grep "Current cloud"...

So this has an added effect that if you typo something with `--host*` in it (like forgetting a sub-command for `--add-schedule) it return this too. ``` [root@quads2-stage ~]# quads --host-list...

Let's see if we can get a patchset into gerrit for the `APIv3` branch too. I see 1.1 series patchset is up for review here: https://review.gerrithub.io/c/redhat-performance/quads/+/1176267