opendevreview | Ghanshyam proposed openstack/manila master: DNM: testing grenade fix https://review.opendev.org/c/openstack/manila/+/879117 | 02:43 |
---|---|---|
opendevreview | Ghanshyam proposed openstack/manila stable/xena: DNM: testing grenade fix https://review.opendev.org/c/openstack/manila/+/879095 | 05:04 |
opendevreview | Goutham Pacha Ravi proposed openstack/python-manilaclient master: Deprecate "manila" CLI client https://review.opendev.org/c/openstack/python-manilaclient/+/879130 | 06:16 |
opendevreview | Stephen Finucane proposed openstack/manila master: db: Migrate "share group", "share group type" APIs to enginefacade https://review.opendev.org/c/openstack/manila/+/856467 | 15:53 |
opendevreview | Stephen Finucane proposed openstack/manila master: db: Migrate 'share_resources_host_update' helper API to enginefacade https://review.opendev.org/c/openstack/manila/+/872157 | 15:53 |
opendevreview | Stephen Finucane proposed openstack/manila master: db: Replace all usage of 'get_session' https://review.opendev.org/c/openstack/manila/+/872158 | 15:53 |
opendevreview | Stephen Finucane proposed openstack/manila master: db: Don't use strings to indicate relationship names https://review.opendev.org/c/openstack/manila/+/872171 | 15:53 |
opendevreview | Stephen Finucane proposed openstack/manila master: db: Use 'model_query' consistently https://review.opendev.org/c/openstack/manila/+/872170 | 15:53 |
opendevreview | Ghanshyam proposed openstack/manila master: Move skip level job to manila-grenade-skip-level-always https://review.opendev.org/c/openstack/manila/+/879194 | 16:07 |
gmann | carloss: gouthamr: as new cycle started, update for grenade skip level job. I am making it *-skip-level-always job, let me know what you think https://review.opendev.org/c/openstack/manila/+/879194 | 19:55 |
carloss | ack - thanks gmann! | 19:56 |
carloss | will take a look | 19:56 |
gmann | thanks | 19:56 |
gouthamr | gmann++ thanks! do we care to set the job to voting in stable/2023.1? | 19:58 |
gmann | gouthamr: not as required in 2023.1 but in 2024.1 (next SLURP) we need to have it voting to make sure 2023.1(first SLURP) - > 2024.1 upgrade work fine | 19:59 |
gmann | and if we keep it voting in non SLURP (2023.2) also then this is best we do for smooth upgrade :) | 19:59 |
gouthamr | gmann: ack; that makes sense.. we can set this to voting and hold ourselves to a high standard.. | 20:00 |
gmann | but any time you see this is failing in non-SLURP release you can make non voting but at least you will get to know what upgrade impact we have introduced between SLURP releases | 20:01 |
gouthamr | ++ totally | 20:01 |
gmann | gouthamr: exactly | 20:01 |
gmann | I am going to write some guidelines on those for other projects but this is what Nova did and I am proposing it for Manila. Neutron decided to keep it in periodic for non-SLURP. | 20:02 |
gmann | but neutron will also keep eyes on it even as part of periodic run | 20:02 |
gouthamr | ah i see, on our part, we've not been very disciplined about periodic jobs :( | 20:03 |
gouthamr | so we peeled off any we used to maintain as well | 20:03 |
gouthamr | i'll watch for those guidelines; i've indicated i'm okay switching it to voting on the review... | 20:05 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!