| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-02-28 | |||
| 16:48:55 | bauzas | I have to go errand in a sec | |
| 16:49:52 | bauzas | looks not | |
| 16:49:54 | bauzas | if so | |
| 16:49:56 | bauzas | thanks all | |
| 16:50:02 | bauzas | #endmeeting | |
| 16:50:02 | opendevmeet | Meeting ended Tue Feb 28 16:50:02 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:50:02 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.html | |
| 16:50:02 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.txt | |
| 16:50:02 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-02-28-16.02.log.html | |
| 16:50:12 | elodilles | thanks o/ | |
| 17:21:12 | stephenfin | Weird one. Anyone have any idea why this doesn't work as expected? https://paste.opendev.org/show/bpzDcEI75QIIb9QuGFb8/ | |
| 17:21:45 | stephenfin | If I run that, it prints out "Exception: Method 'baz' is not allowed" instead of "Exception: Method 'foo' is not allowed" as expected (baz instead of foo) | |
| 17:22:23 | stephenfin | It's a reproducer for bug in Keystone tests. I've fixed the tests but I can't yet grok why it was happening. | |
| 17:31:15 | gmann | dansmith: sean-k-mooney bauzas : on skip-level job. as 2023.2 is NON_SLURP so we will not run skip-level job right | |
| 17:31:37 | gmann | in 2023.3 cycle we will run it from 2023.1 to 2023.3 upgrade on jammy | |
| 17:31:41 | dansmith | gmann: I want nova to stick to testing N-2->N even in non-slurp releases | |
| 17:32:06 | dansmith | gmann: perhaps I should just clone grenade-skip-level to grenade-skip-level-continuous and update that to be z->b ? | |
| 17:32:11 | dansmith | or z->master | |
| 17:32:26 | gmann | dansmith: ohk | |
| 17:32:48 | gmann | so that will be on focal right as zed is tested on focal as testing runtime | |
| 17:33:04 | gmann | zed (focal) -> 2023.2 (focal ?) | |
| 17:33:17 | gmann | but 2023.2 on focal is not tested | |
| 17:33:24 | dansmith | I thought zed was both? | |
| 17:33:42 | dansmith | ah, I see, it wasn't.. dang | |
| 17:33:43 | gmann | 2023.1 was both, let me check | |
| 17:34:04 | dansmith | yeah, zed was just 20.04 | |
| 17:34:16 | dansmith | well, I can try it and if it doesn't work I guess we can pung | |
| 17:34:17 | gmann | https://governance.openstack.org/tc/reference/runtimes/zed.html | |
| 17:34:18 | dansmith | *punt | |
| 17:34:18 | gmann | yeah | |
| 17:34:28 | dansmith | because sean-k-mooney wants to bump the minimum libvirt version | |
| 17:34:41 | gmann | as 2023.1 starting was tested ion jammy so zed might work | |
| 17:34:46 | gmann | ohk | |
| 17:35:18 | gmann | in 2023.2 right? or bump in 2023.1 ? | |
| 17:35:54 | dansmith | sean-k-mooney: wants to bump in 2023.2, but presumably to still include what would be needed for 2023.1 | |
| 17:36:08 | dansmith | i.e. jammy | |
| 17:39:31 | gmann | but is not that will be covered in normal grenade job from 2023.1 to 2023.2 ? or we want N-2 thing also due to libvirt bump ? and so does zed on jammy just because of grenade testing but main purpose is to check zed->2023.2 libvirt bump work fine or not? | |
| 17:40:38 | dansmith | not to test the libvirt bump specifically | |
| 17:40:53 | dansmith | but rather to keep us with a working N-2->N even though we don't *have* to support it | |
| 17:41:11 | dansmith | if we end up breaking something and have to drop the job, then fine, but I would rather highlight what breaks N-2 upgrades if we can | |
| 17:41:33 | gmann | ok | |
| 17:42:27 | gmann | i think it should work as zed was the edge when we move to jammy | |
| 17:42:38 | dansmith | yeah, will see | |
| 17:43:06 | opendevreview | Dan Smith proposed openstack/nova master: Add continuous skip-level job for nova https://review.opendev.org/c/openstack/nova/+/875773 | |
| 17:43:46 | gmann | so for that I will not filter out the 2023.2 from here (we filter out NON-SLURP here) which I do while release time https://github.com/openstack/grenade/blob/master/.zuul.yaml#L392 | |
| 17:44:16 | opendevreview | Dan Smith proposed openstack/nova master: Add continuous skip-level job for nova https://review.opendev.org/c/openstack/nova/+/875773 | |
| 17:44:31 | stephenfin | Got it. It's late binding https://stackoverflow.com/q/3431676/ Sigh, TIL | |
| 17:45:02 | dansmith | gmann: oh hmm, that's just the thing that prevents it from running on stable right? | |
| 17:45:20 | gmann | yeah | |
| 17:45:42 | gmann | because it is in integrated gate template also | |
| 17:45:54 | dansmith | yeah, so that's okay for now right? we only care about master | |
| 17:47:11 | gmann | yes, we can adjust the integrated template not to run it for other projets does not want to run and keep generic job able-to-run-everywhere | |
| 17:48:01 | gmann | and that is good so that project can control if they want to run or skip instead of we stop it for everyone | |
| 17:48:04 | dansmith | gmann: well, I just inherited it for nova ^ | |
| 17:48:39 | dansmith | if other projects want to do the same, we can add it to grenade and not the integrated jobs, but if not, we might as well keep it in nova for now right? | |
| 17:49:10 | gmann | dansmith: ohk it need to run on jammy otherwise default one will run on focal | |
| 17:49:20 | dansmith | right | |
| 17:51:01 | gmann | dansmith: in that case let me filter out the base job for 2023.2 not to run so that it does not run by default as part of integrated gate and you can override 'branches' variant in nova inherited job to run on 2023.2 (master) | |
| 17:53:05 | dansmith | gmann: yeah I assumed that was what you would do once 2023.2 opens right? | |
| 17:53:35 | gmann | dansmith: yeah | |
| 17:55:39 | dansmith | gmann: ubuntu-jammy is not the right nodeset? | |
| 17:56:49 | opendevreview | Dan Smith proposed openstack/nova master: Add continuous skip-level job for nova https://review.opendev.org/c/openstack/nova/+/875773 | |
| 17:56:51 | gmann | dansmith: openstack-single-node-jammy in devstck set the controller things more than just ubuntu-jammy so for devstck based job openstack-single-node-jammy will work | |
| 17:57:04 | dansmith | okay | |
| 17:57:06 | gmann | https://github.com/openstack/devstack/blob/master/.zuul.yaml#L11 | |
| 17:57:58 | dansmith | I copied from tempest-tox-plugin-sanity-check which I guess is not a devstack job | |
| 17:58:13 | opendevreview | Sylvain Bauza proposed openstack/nova master: DNM (yet) Update min support for Bobcat https://review.opendev.org/c/openstack/nova/+/875621 | |
| 17:58:50 | bauzas | dansmith: sean-k-mooney: just updated the next-after-rc1 patch for make grenade-skip-level voting on both check and gate pipes | |
| 18:04:15 | opendevreview | Sylvain Bauza proposed openstack/nova master: Add service version for Antelope https://review.opendev.org/c/openstack/nova/+/874932 | |
| 18:04:15 | opendevreview | Sylvain Bauza proposed openstack/nova master: DNM (yet) Update min support for Bobcat https://review.opendev.org/c/openstack/nova/+/875621 | |
| 18:04:31 | bauzas | sean-k-mooney: dansmith: and did the cleanups for the antelope patch | |
| 18:49:56 | sean-k-mooney | "Nova does now currently support the | |
| 18:49:58 | sean-k-mooney | coexistence of N and N+2 or greater | |
| 18:50:00 | sean-k-mooney | " | |
| 18:50:05 | sean-k-mooney | that a little clunky | |
| 18:52:20 | sean-k-mooney | """ As of OpenStack 2023.1 (Antelope), Nova enables the | |
| 18:52:22 | sean-k-mooney | coexistence of N and N-2 (zed) | |
| 18:52:24 | sean-k-mooney | """ | |
| 18:52:33 | sean-k-mooney | ill comment that inline but this is how i woudl write that. | |
| 18:53:08 | sean-k-mooney | however while we are treating this as a dress rehersal im not sure i agree with avocating this. | |
| 18:53:30 | sean-k-mooney | we expect it to work | |
| 18:53:46 | sean-k-mooney | but i dont know if we want to comit to fixing issues with yoga to antelope | |
| 18:54:08 | sean-k-mooney | i think we should consider it experimental rather then something you should use in production in general | |
| 18:54:24 | dansmith | I haven't reviewed yet, but agree, we should make it clear that it's a best-effort thing, but I'd also be in favor of just explaining that we don't *fail* on N-2, but not go so far as saying we support it or that it's a good idea | |
| 18:57:39 | sean-k-mooney | bauzas: comments inline https://review.opendev.org/c/openstack/nova/+/874932/4/doc/source/admin/upgrades.rst | |
| 20:28:10 | opendevreview | Merged openstack/nova master: Fix logging in MemEncryption-related checks https://review.opendev.org/c/openstack/nova/+/873388 | |
| #openstack-nova - 2023-03-01 | |||
| 08:45:02 | bauzas | morning folkks | |
| 09:27:19 | opendevreview | Sylvain Bauza proposed openstack/nova master: Add the 2023.1 Antelope prelude section https://review.opendev.org/c/openstack/nova/+/875380 | |
| 09:35:51 | sean-k-mooney | bauzas: https://review.opendev.org/c/openstack/nova/+/875380/2..3/releasenotes/notes/antelope-prelude-4a99907b00e739f8.yaml is still tecnilaly not correct | |
| 09:36:09 | sean-k-mooney | 2024.1 is the first SLURP release offically for all project | |
| 09:36:12 | bauzas | no | |
| 09:36:37 | sean-k-mooney | yes | |
| 09:36:40 | bauzas | see the TC resolution | |
| 09:37:18 | bauzas | 2023.1 is the first 'SLURP release' but upgrade from yoga is considered a test | |
| 09:37:41 | bauzas | we indeed need to guarantee 2023.1 to 2024.1 upgrades | |
| 09:37:50 | bauzas | but both are 'officially' SLURP releases | |
| 09:38:02 | sean-k-mooney | calling it a SLURP release imples its supproted by all project form yoga | |
| 09:38:06 | sean-k-mooney | which was never a requirement | |
| 09:38:19 | bauzas | the resolution is clear about the requirements | |
| 09:38:41 | bauzas | but there is a TC meeting today, we can clarify the resolution there | |