| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-24 | |||
| 14:35:08 | kashyap | #qemu, OFTC | |
| 14:35:16 | zigo | Will try. | |
| 16:03:32 | bauzas | tmazur: so you want to have a cross-project session for Horizon ? | |
| 16:08:02 | tmazur | bauzas: it would be nice, but we do not insist. We would like to just clarify things about potential implementation python bindings. It's pretty clear that osc-placement is not the right place for them anyway, and you pointed it in the etherpad. Is something like python-placementclient coming in any reasonable future? | |
| 16:16:20 | vishalmanchanda | bauzas: hello, Can we have a 20-25 mins nova-horizon cross-project session on Tuesday, March 28 at 15 UTC? | |
| 16:17:15 | vishalmanchanda | bauzas: or please suggest some other time slots? | |
| 16:17:25 | bauzas | vishalmanchanda: tmazur: unfortunately Tues 15UTC is already taken https://etherpad.opendev.org/p/nova-bobcat-ptg#L39 | |
| 16:17:26 | vishalmanchanda | that works for nova team | |
| 16:18:02 | vishalmanchanda | Is any other time slot available on Tuesday? | |
| 16:18:24 | bauzas | vishalmanchanda: we could do it ealier, say 1400UTC | |
| 16:18:34 | bauzas | if it takes 30 mins, that would suit | |
| 16:19:57 | vishalmanchanda | bauzas: works for me. tmazur what about you? | |
| 16:21:46 | tmazur | Works for me | |
| 16:24:09 | vishalmanchanda | bauzas: ok, then, please book Tuesday, March 28 at 1400UTC slot for the horizon cross-project session. | |
| 16:24:42 | bauzas | vishalmanchanda: did it : https://etherpad.opendev.org/p/nova-bobcat-ptg#L42 works for you to use our room ? (diablo) | |
| 16:25:27 | bauzas | vishalmanchanda: tmazur: agenda for our x-p session is https://etherpad.opendev.org/p/nova-bobcat-ptg#L103 | |
| 16:25:27 | vishalmanchanda | bauzas: yeah, horizon team can joins nova room, thanks | |
| 16:25:32 | bauzas | all set then | |
| 16:25:42 | bauzas | thanks folks | |
| 16:25:51 | vishalmanchanda | bauzas: great. | |
| 16:25:54 | tmazur | Thanks! | |
| 16:26:02 | vishalmanchanda | thanks:) | |
| 16:26:23 | bauzas | np | |
| 16:26:28 | bauzas | happy to help | |
| #openstack-nova - 2023-03-26 | |||
| 09:43:25 | opendevreview | Takashi Natsume proposed openstack/placement master: Move implemented specs for Xena and Yoga release https://review.opendev.org/c/openstack/placement/+/853730 | |
| 09:43:40 | opendevreview | Takashi Natsume proposed openstack/placement master: Fix a wrong assertion method https://review.opendev.org/c/openstack/placement/+/861489 | |
| 09:44:15 | opendevreview | Takashi Natsume proposed openstack/nova master: Update contributor guide for 2023.2 Bobcat https://review.opendev.org/c/openstack/nova/+/876447 | |
| #openstack-nova - 2023-03-27 | |||
| 11:50:50 | bauzas | fwiw, I'll attend the publicclould vPTG sessions today | |
| 12:51:07 | bauzas | gibi: sean-k-mooney: we need a second core, please https://review.opendev.org/c/openstack/nova/+/875621 | |
| 12:52:00 | sean-k-mooney | we are pas the RC phase so sure. | |
| 12:54:49 | sean-k-mooney | bauzas: by the way we know what az the instance is on in the hostmanager but on in the filters | |
| 12:55:01 | sean-k-mooney | bauzas: that is why we need the new filed | |
| 12:55:34 | bauzas | sean-k-mooney: tbh, before discussing about it, I'd prefer to have a spec | |
| 12:55:41 | bauzas | because I don't understand about the usecase | |
| 12:55:57 | bauzas | (I mean AZ soft affinity) | |
| 12:56:16 | sean-k-mooney | bauzas: mnaser was the first to bring it up | |
| 12:56:18 | bauzas | but ok, if we need to create a field, meh then | |
| 12:56:43 | sean-k-mooney | bauzas: basically the use the cross_az attach option in the vexhost public cloud | |
| 12:56:51 | bauzas | for example, if you see, people don't even know about all the existing config options | |
| 12:57:02 | sean-k-mooney | but they dont force user to set an az when the vm is created | |
| 12:57:05 | bauzas | even if we document it in the config option | |
| 12:57:16 | sean-k-mooney | and then if the user does a rezie it can fail and get reschedulerd | |
| 12:57:26 | bauzas | sean-k-mooney: I think we said before that the fact that Cinder uses AZs is different from Nova | |
| 12:57:46 | sean-k-mooney | thats not true however and also not the problem | |
| 12:57:54 | bauzas | so I'm a bit not happy with the cross_az_attach option | |
| 12:58:13 | sean-k-mooney | the propbelm is we have a config cross_az_attach that changes api/sechduler beahvior in a non discofverable way | |
| 12:58:20 | bauzas | maybe we would rather need to discuss with Cinder what we could do if so | |
| 12:58:42 | sean-k-mooney | right so this is a very very similar situration to the routed networks issue | |
| 12:59:27 | sean-k-mooney | we have an addtional constratint when cross_az_attach=false (like the ip aviablity) which is not currently consider by placement or the schduler | |
| 12:59:44 | bauzas | anyway, going to the vPTG now | |
| 12:59:53 | sean-k-mooney | the correct longterm fix would be too model cinder volume backend avaibality as placmenet aggreates | |
| 13:00:01 | bauzas | sean-k-mooney: yeah, so we should discuss this with Cinder | |
| 13:00:07 | bauzas | indeed | |
| 13:00:13 | bauzas | I agree with ^ | |
| 13:00:32 | sean-k-mooney | ya so that woudl be good to do and i have a usecasue related to this that i would like us to also do | |
| 13:00:37 | sean-k-mooney | ill add it to the adgenda | |
| 13:02:08 | sean-k-mooney | clip notes version is, when using iamges_type RBD i would like to create an aggreate usign the ceph FSID and recored the fsid of cluster the instance is using in the instnace_system_metadta so that we can automatically sechdule ot those in teh came ceph cluster wehn moving RBD backed vms | |
| 13:02:58 | sean-k-mooney | right now we have exactly the same problem that we can select hosts that do not have accces to the cluster based on there local confg | |
| 13:03:12 | sean-k-mooney | so the live migration can succed but thten a hard reboot will fail | |
| 13:03:32 | sean-k-mooney | its a differnt but simiarl probelm casue by the fact we dont model network storage in placment | |
| 13:03:57 | sean-k-mooney | so there is both a cinder and nova only varient of the same issue | |
| 13:56:17 | bauzas | gibi: you're listening to the publiccloud SIG session ? | |
| 13:56:42 | bauzas | fwiw, they're discussing about interop flavors | |
| 14:14:39 | gibi | bauzas: I try to follow but pretty distracted | |
| 14:16:42 | sean-k-mooney | bauzas: i am not currently on that but i left a comment in the ether pad | |
| 14:17:15 | bauzas | sean-k-mooney: tl;dr they have a pretty solid usecase about filtering flavors on attributes | |
| 14:17:26 | bauzas | operator-defined attributes | |
| 14:17:47 | sean-k-mooney | filtering yes but that is an interop issue if they are custom | |
| 15:08:05 | opendevreview | Eric Harney proposed openstack/nova master: mypy: Fix implicit optional usage https://review.opendev.org/c/openstack/nova/+/878693 | |
| 15:16:46 | bauzas | bim bam boom | |
| 15:16:48 | bauzas | https://07de6a0c9e6ec0c6835f-ccccbfab26b1456f69293167016566bc.ssl.cf2.rackcdn.com/875621/10/gate/openstack-tox-pep8/e50f9f0/job-output.txt | |
| 15:16:52 | bauzas | huzzah, mypy issue | |
| 15:17:17 | bauzas | related to https://review.opendev.org/c/openstack/requirements/+/872065 | |
| 15:17:33 | bauzas | gibi: sean-k-mooney: ^ | |
| 15:18:09 | bauzas | working on a fix with no_implicit_optional=False | |
| 15:25:41 | gibi | bauzas: I'm fine with https://review.opendev.org/c/openstack/nova/+/878693 as a fix for ^^ | |
| 15:28:20 | sean-k-mooney | i agree with the mypi fix in nova | |
| 15:29:19 | bauzas | gibi: damn, I was jinxed :) | |
| 15:29:34 | bauzas | I was working on a patch | |
| 15:29:38 | bauzas | anyway +Wd | |
| 15:29:47 | kashyap | bauzas: Are there meeting minutes from the public-cloud WG? | |
| 15:29:49 | bauzas | and sent an mail to -discuss to prevent rechecks | |
| 15:29:51 | kashyap | Or Etherpad nodes | |
| 15:30:11 | bauzas | kashyap: https://etherpad.opendev.org/p/march2023-ptg-publiccloud | |
| 15:30:50 | bauzas | tl;dr: most of the discussion was about flavors API | |
| 15:31:04 | bauzas | and how filtering extra specs is a need | |
| 15:31:33 | bauzas | + some can of worms about some possible discoverable mechanism for describing a flavor | |
| 15:31:55 | bauzas | they'll write a backlog spec so we'll nitpick over it | |
| 15:45:03 | frickler | bauzas: regarding mypy, does it make sense to add nova pep8 job to reqs repo? I hope we will get more frequent updates again in the future, after getting almost none in the last cycle | |
| 15:47:00 | bauzas | frickler: good question, I dunno what to say here | |
| 15:47:13 | bauzas | because we use the pep8 tox target for mypy | |
| 15:47:36 | bauzas | so either the pep8 openstack one should also use mypy or maybe we should use a different tox job | |
| 15:47:54 | bauzas | I just don't want to test again pep89 twice | |
| 15:48:42 | frickler | bauzas: I'm not sure I understand that, I was talking about adding cross-nova-pep8 to requirements repo. currently there only is cross-nova-py310 | |
| 15:49:14 | bauzas | frickler: ok, then +1 | |
| 15:51:29 | frickler | o.k., I'm feeling a bit guilty about having pushed the u-c updates yesterday, so I'll try to set that up as compensation ;-) | |
| 15:52:13 | gibi | ^^ +1 from me as well | |
| 15:58:22 | gmann | frickler: +1 | |
| 16:05:17 | frickler | does any of you know why this files filter is only in place in gate and only for nova+placement? https://opendev.org/openstack/requirements/src/branch/master/.zuul.d/project.yaml#L126-L129 | |
| 16:32:58 | bauzas | frickler: good question, I dunno https://opendev.org/openstack/requirements/commit/91eaa0cd7f75f5f1b93226e4bb2de64aa4fed2b3 | |