| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-01-10 | |||
| 16:14:09 | gmann | gibi: yes. | |
| 16:14:11 | sean-k-mooney | ya so we just need to pin the branch in that line which is posible | |
| 16:14:14 | gibi | OK I got it | |
| 16:14:21 | elodilles | as i remember constraints from master also caused issues on stable branches (in placement) | |
| 16:14:30 | bauzas | sean-k-mooney: yeah, my point is that if the tox developers don't verify the behaviours of tox.ini and rather say they just verify the toml ones, then I'm a bit afraid | |
| 16:14:47 | sean-k-mooney | bauzas: its not related to that | |
| 16:15:14 | sean-k-mooney | bauzas: openstack is quite differnt form ontehr python project in how we use setuptools/pbr and the idea of a constratis file | |
| 16:15:23 | gmann | all other stable branches gate are good. I tested them after pin | |
| 16:15:32 | gibi | bauzas: tox4 was a rewrite, and they are not intending to keep all the tox3 behavior (I learned yesterday) | |
| 16:15:43 | bauzas | sean-k-mooney: sure I'm not saying we should create a pyproject.toml filze | |
| 16:15:50 | gibi | gmann: thanks! | |
| 16:16:06 | bauzas | sean-k-mooney: but I was wondering why nobody was finding the problem until we told them | |
| 16:16:08 | sean-k-mooney | bauzas: well that has been discussed and we might want to eventually but we should lop back to one topic | |
| 16:16:25 | sean-k-mooney | bauzas: because constrait files is baicaly an openstack thing | |
| 16:16:44 | bauzas | sean-k-mooney: we didn't had only problems with constraints | |
| 16:16:45 | clarkb | sean-k-mooney: openstack is the primary user in the wild probably but it is a normal pip functionality | |
| 16:16:53 | sean-k-mooney | we are the comunity that drove that in pip | |
| 16:17:10 | sean-k-mooney | but yes its is a pip capablity | |
| 16:17:11 | bauzas | gibi: ack, good to know | |
| 16:17:14 | clarkb | bauzas: fwiw I'm helping to move zuul and opendev projects to nox | |
| 16:17:33 | sean-k-mooney | isnit that a pti issue | |
| 16:17:41 | sean-k-mooney | dont we specify tox explictly | |
| 16:17:43 | clarkb | (because there are lots of little tox changes and when I file issues upstream the resposne is often "why would you do that?" and the answer is well because v3 supported it so ya...) | |
| 16:17:51 | clarkb | sean-k-mooney: yes for openstack. I personally think openstack should change too | |
| 16:17:56 | clarkb | but it is work | |
| 16:18:03 | sean-k-mooney | perhaps a good ptg topic | |
| 16:18:10 | gmann | +1 | |
| 16:18:12 | dansmith | I'm not super keen on the nox thing | |
| 16:18:13 | sean-k-mooney | how to evovle pti | |
| 16:18:14 | bauzas | not only for our project | |
| 16:18:21 | dansmith | so I'd like to have a real discussion about it | |
| 16:18:33 | bauzas | should be a cross-project discussion honestly | |
| 16:18:34 | dansmith | (I'm also not super keen on tox destroying the world for fun and profit) | |
| 16:18:37 | sean-k-mooney | right i was thinking comuity/cross project topic | |
| 16:18:45 | bauzas | dansmith: me too | |
| 16:18:50 | gmann | right | |
| 16:19:11 | sean-k-mooney | ok so looping back. we need to pin placment on stable branches fo osc-placment | |
| 16:19:11 | bauzas | honestly, I'd have preferred to continue using tox3 until we test all the modifications they did | |
| 16:19:19 | bauzas | but, this is done | |
| 16:19:30 | sean-k-mooney | and we have unbolcked the other "nova" gates | |
| 16:19:42 | sean-k-mooney | with followups for the install_commands changes correct? | |
| 16:19:54 | gmann | sean-k-mooney: gibi: ok for pin but I was thinking we have to test latest placement there? I do not know reason just want to confirm | |
| 16:20:21 | sean-k-mooney | gmann: git+https://opendev.org/openstack/placement.git#egg=openstack-placement line on master | |
| 16:20:27 | sean-k-mooney | is so we get the latest placement fixture | |
| 16:20:32 | bauzas | and the fact that tox developers just rewrite their tox.ini by what they want without continuing to support the existing (and without deprecating them at least) let me think about any new major tox versions we'd have | |
| 16:20:38 | sean-k-mooney | so we can test when new feture are addded | |
| 16:20:38 | gibi | gmann: I don't know the reason either | |
| 16:20:38 | gmann | so we need to test latest placement in master gate only | |
| 16:21:17 | gmann | sean-k-mooney: right but that we do not need on stable osc-placement version right? | |
| 16:21:41 | sean-k-mooney | gmann: correct it can and should use the stable version | |
| 16:21:52 | gmann | I was hesitating to pin placement there as I do not know the original reason ot use latest placement there | |
| 16:21:54 | sean-k-mooney | they do need to be kept in sync however | |
| 16:22:06 | sean-k-mooney | its caputed in teh comme messange here https://github.com/openstack/osc-placement/commit/da8cd4d68b06399c607776db2a704b4578146996 | |
| 16:22:18 | gmann | ack | |
| 16:22:48 | gmann | thanks | |
| 16:24:33 | sean-k-mooney | ok i think we have covered those topics and can move on | |
| 16:24:42 | bauzas | I was about to ask | |
| 16:24:49 | bauzas | ok, let's move on then | |
| 16:24:54 | gmann | yeah | |
| 16:25:00 | bauzas | #topic Release Planning | |
| 16:25:04 | bauzas | #link https://releases.openstack.org/antelope/schedule.html | |
| 16:25:07 | bauzas | #info Antelope-3 is in 5 weeks | |
| 16:25:16 | bauzas | (and featurefreeze... :) ) | |
| 16:25:21 | bauzas | #info As a reminder, Nova SpecFreeze deadline is this Thursday https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031636.html | |
| 16:26:08 | bauzas | I'll modify launchpad's https://blueprints.launchpad.net/nova/antelope once we're done with reviewing specs | |
| 16:26:58 | bauzas | I have then a question | |
| 16:27:07 | bauzas | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html I guess we'll want to have a virtual PTG again ? | |
| 16:27:07 | bauzas | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html I guess we'll want to have a virtual PTG again ? | |
| 16:27:39 | bauzas | for the Bobcat planning :) | |
| 16:27:55 | bauzas | (man, haven't but should have voted this time...) | |
| 16:28:02 | sean-k-mooney | can we create teh 2023.2 specs repo after spec freeze | |
| 16:28:19 | sean-k-mooney | i dont recall seeing a vote email go out | |
| 16:28:24 | bauzas | there was one | |
| 16:28:28 | sean-k-mooney | i tought this was selected by the foundation | |
| 16:28:51 | bauzas | nope, sent during your holidaus | |
| 16:28:56 | sean-k-mooney | ok well the foundation has never consicidently sent me vote urls anyway | |
| 16:28:58 | bauzas | hence why you haven't probably seen it | |
| 16:29:01 | gmann | format will be 1 virtual PTG + 1 in-person PTG per year. in-person PTG will be aligned to summit+release | |
| 16:29:36 | bauzas | gmann: any chance to have those physical attendances (I don't like the PTG naming) to be at the start of the release time ? | |
| 16:29:46 | bauzas | for Vancouver, ship is sailed | |
| 16:30:25 | dansmith | sean-k-mooney: I didn't get one either | |
| 16:30:50 | gmann | bauzas: yeah, that is what foundation staff updated that they will try to aligned it with summit and openstack relaese but let's see as it can be challenging too | |
| 16:30:52 | bauzas | dansmith: sean-k-mooney: https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031551.html | |
| 16:31:10 | dansmith | oh, to the list | |
| 16:31:19 | bauzas | 70% of the list was probably on PTO | |
| 16:31:24 | sean-k-mooney | but that vote url is a personal one | |
| 16:31:28 | sean-k-mooney | not one everyone can use right | |
| 16:31:33 | gmann | for vancouver, yes as event is in between of cycle it needs to be that time | |
| 16:31:44 | sean-k-mooney | you are ment to get one to your personal email for all votes | |
| 16:31:56 | bauzas | sean-k-mooney: good point, again, I haven't voted so I haven't tested it | |
| 16:32:31 | gmann | sean-k-mooney: I think it is public vote so anyone can vote with that url but one per IP or so | |
| 16:32:37 | bauzas | anyway, this is done anyway | |
| 16:32:42 | gmann | if I am remembering public vote things correctly | |
| 16:32:46 | bauzas | gmann: fun fact is, voting isn't closed AFAICS | |
| 16:33:02 | sean-k-mooney | perhaps in the tool but the name has been released | |
| 16:33:14 | bauzas | yup, another ship sailed | |
| 16:33:18 | sean-k-mooney | in anycase i can create a 2023.2 folder in the spec repo | |
| 16:33:20 | gmann | ohk :) honestly saying I have not given mush attention to release naming :) | |
| 16:33:28 | gmann | sean-k-mooney: +1 | |
| 16:33:33 | bauzas | sean-k-mooney: wait for the spec freeze | |