| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-03-09 | |||
| 14:41:38 | sean-k-mooney | dvo-plv: for now you could just use a custom trait and or comment it out | |
| 14:42:01 | bauzas | is it for helping to implement ? | |
| 14:42:07 | bauzas | or is it for us reviewing ? | |
| 14:42:31 | bauzas | if the former, nothing prevents you to test your patch against a running devstack which pulls ostraits from git | |
| 14:42:35 | sean-k-mooney | i.e more the request filter and traits reproting to a seocnd patch | |
| 14:43:13 | bauzas | if the latter, add a bit fat comment in the commit msg saying the CI is broken because of the missing release | |
| 14:43:26 | sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/876075/3/nova/scheduler/request_filter.py is just brekign things currently | |
| 14:43:35 | sean-k-mooney | since os_traits.COMPUTE_NET_VIRTIO_PACKED does not exist yet | |
| 14:43:54 | dvo-plv | yes, exactly | |
| 14:43:54 | bauzas | yeah got it | |
| 14:44:41 | bauzas | but again, nothing prevents you to test this filter with a devstack having a LIBS_FROM_GIT | |
| 14:45:16 | bauzas | once the spec is approved, we could move forward and release ostraits soon | |
| 14:45:22 | dvo-plv | I just wanted to be sure that all works properly with zull environment. But I will wait for approve and do best to fix all problems, what I will find locally | |
| 14:46:07 | bauzas | dvo-plv: if you really want to make yourself confident of your patch, then use a custom trait indeed | |
| 14:46:55 | bauzas | but this will have to be cleaned up before review time | |
| 14:48:21 | bauzas | gibi: a quick swing would be appreciated on https://review.opendev.org/c/openstack/nova/+/874515 | |
| 14:49:32 | gibi | bauzas: looks good | |
| 14:49:39 | bauzas | thanks | |
| 14:49:52 | bauzas | gibi: sean-k-mooney: I have a few other nitty changes in my gerrit that are overdue | |
| 14:50:00 | bauzas | stay around :) | |
| 14:53:20 | dvo-plv | btw, we already update and move packed virtqueue support spec file to the 2023/2 https://review.opendev.org/c/openstack/nova-specs/+/868377 | |
| 14:54:17 | sean-k-mooney | i need to go to the chemeyist and pick up my perscirption but ill be back in a while and can take a look then | |
| 14:55:04 | bauzas | dvo-plv: this week, I'm overbusy with PTL scrubbing tasks, but I'll give a round on reviews next week | |
| 14:55:10 | bauzas | (specs reviews I mean) | |
| 14:56:41 | dvo-plv | Thank you | |
| 18:41:21 | spatel | sean-k-mooney Quick question related nova-schedule not able to find sriov nodes. I do have this in nova - https://paste.opendev.org/show/bASaMtV2z9K8N24FZAk4/ | |
| 18:41:37 | spatel | I have created AZ group and added single compute node to that AZ | |
| 18:41:44 | opendevreview | Merged openstack/nova master: fup for power management series https://review.opendev.org/c/openstack/nova/+/874515 | |
| 18:41:55 | spatel | In flavor i didn't specify any properties | |
| 18:45:54 | spatel | Does placement has any entry of PCI_DEVICE? | |
| #openstack-nova - 2023-03-10 | |||
| 02:14:36 | opendevreview | melanie witt proposed openstack/nova master: testing: Fix and robustify archive_deleted_rows test https://review.opendev.org/c/openstack/nova/+/877055 | |
| 02:14:37 | opendevreview | melanie witt proposed openstack/nova master: database: Archive parent and child rows "trees" one at a time https://review.opendev.org/c/openstack/nova/+/877056 | |
| 09:15:35 | zigo | My first Antelope VM pings ! :) | |
| 09:20:38 | gibi | zigo: awesome \o/ | |
| 09:23:22 | bauzas | pong | |
| 10:05:41 | bauzas | gibi: sean-k-mooney: I would appreciate your comments on a PTL doc amendment https://review.opendev.org/c/openstack/nova/+/875730 | |
| 10:06:24 | bauzas | also, | |
| 10:06:43 | bauzas | gibi: sean-k-mooney: some operators would like to know which specs were implemented :) https://review.opendev.org/c/openstack/nova-specs/+/876887 | |
| 10:07:27 | bauzas | and eventually, a easy peasy for count_blueprints.py https://review.opendev.org/c/openstack/nova-specs/+/876888 | |
| 10:14:32 | bauzas | https://docs.openstack.org/infra/storyboard/gui/theory.html#the-rest-api looks like there is a REST API and a CLI, lovely | |
| 10:14:49 | bauzas | way better to play with than the web ui from what I've seen in the last 30 mins | |
| 10:35:28 | gibi | bauzas: I have only one small commment on the PTL guid patch | |
| 10:35:57 | bauzas | cool | |
| 10:36:20 | bauzas | btw. this isn't a simple task to leave Storyboard AFAIK | |
| 10:36:48 | bauzas | I'll need to discuss this with the infra folks and the storyboard team (if it still exists :) ) | |
| 10:47:43 | bauzas | gibi: that's fun but fwiw, I just noticed last week of takashi's diligence of creating those schedule wikipages every cyvcle | |
| 10:48:19 | gibi | :) | |
| 10:48:23 | bauzas | IMHO if we really want to add more nova-specific deadlines, we would need to stuff it into https://releases.openstack.org/bobcat/schedule.html | |
| 10:48:55 | bauzas | not sure a lot of us still checkouts the wiki besides the meeting agenda :) | |
| 10:49:14 | bauzas | (but don't get me wrong, I like the wiki for its convenience) | |
| 10:49:40 | bauzas | gibi: as you see, we can add project-specific deadlines https://releases.openstack.org/bobcat/schedule.html#project-specific-events | |
| 10:50:07 | gibi | cool that is then probably a better place than the wikipage | |
| 10:58:26 | bauzas | I'll then explain this in the PTL doc | |
| 10:58:35 | gibi | OK | |
| 10:58:57 | bauzas | and next week's meeting, I'll propose the usual times for spec freeze and feature freeze | |
| 10:59:09 | bauzas | so I could add them in the schedule page | |
| 12:02:19 | opendevreview | Sylvain Bauza proposed openstack/nova master: Update to the PTL guide https://review.opendev.org/c/openstack/nova/+/875730 | |
| 12:37:53 | opendevreview | Danylo Vodopianov proposed openstack/os-vif master: Openvswitch driver was extended https://review.opendev.org/c/openstack/os-vif/+/859574 | |
| 13:11:34 | zigo | Is it normal that the openstackclient now shows so many fields when doing "server show", with some fields looking like not useful at all?!? :) | |
| 13:11:50 | zigo | (many fields having no values at all...) | |
| 13:16:40 | zigo | (some being redondant too...) | |
| 13:25:55 | sean-k-mooney | thats more of a client question we dont really have any inflance over that | |
| 13:26:32 | sean-k-mooney | but on the otherhand some people might depend on some of the out put so it might not be wise to remove things | |
| 13:26:42 | sean-k-mooney | peopel will have differnt definitoin of userful | |
| 13:26:58 | sean-k-mooney | zigo: do you have an example out put | |
| 13:27:49 | zigo | sean-k-mooney: https://paste.opendev.org/show/b7FfjsIpFW6o5NS9slD9/ | |
| 13:28:08 | sean-k-mooney | this is what i get as an admin https://paste.opendev.org/show/bHaPZKj88T8mQ5uulgH7/ | |
| 13:28:25 | zigo | What's the point of accessIPv4, accessIPv6, access_ipv4, access_ipv6, private_v4, private_v6 for example? | |
| 13:28:40 | sean-k-mooney | that is not what i get with my version of osc | |
| 13:28:48 | zigo | I have a way more on my setup ... | |
| 13:29:08 | sean-k-mooney | accessIPv4, accessIPv6, are optional feilds that peopel can use to track the ip to use to access a vm | |
| 13:29:24 | sean-k-mooney | it just metadta on the instance that enduser can use it not used by nova | |
| 13:29:25 | zigo | Yeah, except that they are empty, and show twice ... | |
| 13:29:43 | sean-k-mooney | they are empty unless you set them in the server create/update | |
| 13:29:53 | sean-k-mooney | these used ot be used for nova-netowrks | |
| 13:30:27 | sean-k-mooney | what version of osc are you using | |
| 13:30:30 | sean-k-mooney | i was using 6.0.0 | |
| 13:30:39 | zigo | 6.1.0 | |
| 13:31:37 | zigo | The "location" field also looks weird ... | |
| 13:31:41 | sean-k-mooney | ok so ya i get the same now | |
| 13:31:43 | zigo | What's that Munch() thingy? | |
| 13:32:15 | sean-k-mooney | its a clase we use as part of the prtty prining of data | |
| 13:32:29 | sean-k-mooney | its part of how dicts are rendered using click/cliff | |
| 13:32:54 | zigo | All of this, I don't really mind much, but IMO, it's going to confuse users a lot ! | |
| 13:33:08 | sean-k-mooney | zigo: it kind of looks like someone wen through all the files that could be returned and rendered them by default | |
| 13:33:24 | sean-k-mooney | zigo: right but hte nova team is not really invovled in osc | |
| 13:33:26 | zigo | Also, why do we now have attached_volumes AND volumes_attached ? Do we need this *TWICE* ? :) | |
| 13:33:45 | sean-k-mooney | like we were not asked about any of these changes | |
| 13:34:41 | zigo | Ok. | |
| 13:35:19 | sean-k-mooney | https://github.com/openstack/python-openstackclient/commit/794334ec2405bcfe086b3a56c796a9b6c2f7c685 might be related | |
| 13:35:44 | sean-k-mooney | it may have incorectly resulting in --long effectilgy being always used | |
| 13:36:27 | sean-k-mooney | no its this https://github.com/openstack/python-openstackclient/commit/70dbb01ea3ed900a41092d46ed5ae1370d5771af | |
| 13:36:53 | sean-k-mooney | they swap to the sdk but they added a bunch of fields at the same time | |
| 13:39:53 | sean-k-mooney | i would proably have gated the sdk names behind a flag or somethign and doen it in two patchs | |
| 13:40:03 | sean-k-mooney | first just to swap to sdk with current behavior | |
| 13:40:42 | sean-k-mooney | also the client shoudl really use the names of the field n the api resopnce if possible | |
| 13:41:03 | sean-k-mooney | so im not sure we should use the sdk names at all | |
| 13:41:33 | sean-k-mooney | the ones that novaclient used are the ones form the api responce so i proably would have -1 that patch if we had been asked to review | |
| 13:41:49 | sean-k-mooney | stephenfin: ^ for awareness | |
| 13:42:55 | sean-k-mooney | give there have now been two release with that i assume its two late to revert it and disucss this with the wider nova team? | |