| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-02-04 | |||
| 19:55:01 | sean-k-mooney | the are ok to keep IMO | |
| 19:55:35 | mikal | I should let you escape. I'll take a swing at the version checks today. | |
| 19:56:01 | sean-k-mooney | ack. i may or may not be back briefly later but if not ill try and review again tomorrow | |
| 19:56:10 | sean-k-mooney | mikal: did you see the nova meeting conversation | |
| 19:56:29 | mikal | About the order of landing the API changes? Yes, that made me happy to be completely honest. | |
| 19:57:03 | sean-k-mooney | cool, ya so hopefully we can get at least the first 3 patches and perhaps all 5 merged this week if others have time to review | |
| 19:57:26 | mikal | I appreciate you handholding me along the way. Thank you. | |
| 19:57:47 | mikal | I think that gaming company probably still want the USB one at least, so it would be nice to get all of them in, but I understand we're starting to run out of time. | |
| 19:58:29 | sean-k-mooney | we still ahve 3 weeks so it think its doabel if we get the first 3 this week | |
| 19:58:46 | mikal | This makes me happy. | |
| 19:58:57 | mikal | Well, I'll let you get on with your life. | |
| 19:58:59 | sean-k-mooney | i think there name was shadow https://shadow.tech/ i think | |
| 19:59:55 | mikal | Yeah, that's them. | |
| 20:00:21 | mikal | Maxime Lubin was commenting on the USB patch at one point, but I haven't seen anything recently. | |
| 20:31:26 | frickler | sean-k-mooney: gibi: fyi we (infra-root) noticed some weird activity by that account earlier and we disabled it yesterday | |
| 20:32:02 | sean-k-mooney | frickler: ack, i was not sure it was the same account but i did see those strange comments | |
| #openstack-nova - 2025-02-05 | |||
| 08:22:37 | opendevreview | Rajesh Tailor proposed openstack/nova master: Add support for showing image properties in server show response https://review.opendev.org/c/openstack/nova/+/939649 | |
| 09:15:20 | mikal | melwitt: I only just saw your comments on https://review.opendev.org/c/openstack/nova/+/924844 -- I'll work through them tomorrow. | |
| 09:51:46 | andrewbonney | Morning. If anyone has time I'd appreciate a review of the bug fix in https://review.opendev.org/c/openstack/nova/+/919961 | |
| 10:03:01 | opendevreview | Michael Still proposed openstack/nova master: libvirt: direct SPICE console database changes https://review.opendev.org/c/openstack/nova/+/926877 | |
| 10:03:01 | opendevreview | Michael Still proposed openstack/nova master: libvirt: direct SPICE console object changes https://review.opendev.org/c/openstack/nova/+/926876 | |
| 10:03:02 | opendevreview | Michael Still proposed openstack/nova master: libvirt: Add extra spec for sound device. https://review.opendev.org/c/openstack/nova/+/926126 | |
| 10:03:02 | opendevreview | Michael Still proposed openstack/nova master: libvirt: allow direct SPICE connections to qemu https://review.opendev.org/c/openstack/nova/+/924844 | |
| 10:03:03 | opendevreview | Michael Still proposed openstack/nova master: Protect older compute managers from sound model requests. https://review.opendev.org/c/openstack/nova/+/940770 | |
| 10:03:03 | opendevreview | Michael Still proposed openstack/nova master: libvirt: Add extra specs for USB redirection. https://review.opendev.org/c/openstack/nova/+/927354 | |
| 10:03:34 | mikal | sean-k-mooney: https://review.opendev.org/c/openstack/nova/+/940770 is a first attempt at the compute service version bump thing as discussed this morning. | |
| 14:20:24 | opendevreview | Balazs Gibizer proposed openstack/nova master: Bump InstanceNUMACell version after data migration https://review.opendev.org/c/openstack/nova/+/940604 | |
| 14:25:31 | gibi | sean-k-mooney: dansmith: add the extra tests cases and extended the logic to handle the half migrated cases ^^ | |
| 14:35:52 | MengyangZhang[m] | <sean-k-mooney> "Mengyang Zhang: i suspect the..." <- Since Libvirt introduced these burst parameters in 2.4.0, which was released in 2016, do we still have to worry about this? Nova needs to support n-2 versions, but all versions should already support this burst feature. | |
| 14:39:41 | dansmith | gibi: personally I'd prefer that as two patches, even though I know it's more backport work, but I'll defer to the others | |
| 14:42:01 | gibi | OK I can split it | |
| 14:48:04 | dansmith | gibi: wait for the others to opine, I'm just saying that's _my_ opinion | |
| 14:48:21 | sean-k-mooney | MengyangZhang[m]: its not about the libvirt verion. its about the nova compute version deployed on each host | |
| 14:49:00 | sean-k-mooney | MengyangZhang[m]:in 2025.1 we need to supprot a mix of comptue with (2024.1, 2024.2 and 2025.1) because its a skip level upgrade release | |
| 14:49:24 | sean-k-mooney | in 2025.2 we only need to suprot a mix of 2025.1 and 2025.2 nova computes | |
| 14:49:39 | sean-k-mooney | we need to make sure cold/live migration works acorss those mixed versions | |
| 14:50:36 | sean-k-mooney | so we need a min compute service version check to prevent using the feature until the cloud is fully upgraded or explcit schduler supprot to make sure the isntance only get deploy to the upgraded nodes | |
| 14:57:15 | MengyangZhang[m] | understood, make sense | |
| 14:58:05 | gibi | dansmith: understood | |
| 14:59:16 | sean-k-mooney | the min compute service check is simpler todo, in either case cinder need to be prepared for nova to reject the attachment of a volume with brust qos if the compute node is too old. i belive that is already the case however so that does not really change the existing workflow | |
| 16:58:46 | opendevreview | Sylvain Bauza proposed openstack/nova master: Add a new ImagePropertiesWeigher https://review.opendev.org/c/openstack/nova/+/940642 | |
| 17:07:45 | gmann | bauzas: this is ready, rbac job cleanup we talked yesterday https://review.opendev.org/c/openstack/nova/+/940737 | |
| 17:08:58 | gibi | there is an easy review (just adding more spice to the nova-next job) https://review.opendev.org/c/openstack/nova/+/937275 | |
| 17:11:30 | bauzas | gibi: gmann: reviewing your meats | |
| 17:15:12 | gibi | thanks folks | |
| 17:44:41 | gmann | gibi: if you are around, please chekc this https://review.opendev.org/c/openstack/nova/+/940737 | |
| 17:45:32 | gmann | gibi: bauzas and very trivial typo one https://review.opendev.org/c/openstack/nova/+/937744 | |
| 17:48:16 | gibi | done and done :) | |
| 17:50:39 | gmann | thanks guys | |
| 18:34:15 | mikal | Morning. | |
| 18:48:17 | mikal | sean-k-mooney: I'm taking a look at tempest just now based on melwitt's comments on https://review.opendev.org/c/openstack/nova/+/924844/21. Is it just me or are there now SPICE tempest tests at all? https://github.com/openstack/tempest/blob/master/tempest/config.py#L541 | |
| 18:48:28 | mikal | s/now/no/ | |
| 18:49:45 | melwitt | mikal: there are not and when I looked it looked like they were removed in the past https://github.com/openstack/tempest/commit/d5bda712599a329acb865f9a9a41ad55824b1781 I don't know if it | |
| 18:50:24 | mikal | Hmmm, I wonder why the test cases were removed. | |
| 18:50:28 | melwitt | *if it's realistic and/or reasonable to test spice there but it was something I was curious about | |
| 18:51:08 | dansmith | yeah, the justification for removal in those seems weird, although I'm not sure if they were testing spice itself or just that we could get a spice url from the api | |
| 18:51:09 | mikal | sean-k-mooney and I have have gone back and forth on this a bit. I would like to add tempest tests, but its hard to test much meaningfully there right now -- we'd be basically testing if a TCP port was open I think. | |
| 18:51:45 | dansmith | we have (or used to have?) a VNC test that would at least try to connect and get the RFB00 banner from the socket to make sure it was at least plausibly running | |
| 18:51:53 | mikal | I think I could write meaningful tests by having a simple python spice client, but I haven't managed to find the time to do that yet and it would take longer than I have before the feature freeze this cycle. | |
| 18:52:54 | melwitt | yeah I was thinking of vnc as well, for example https://github.com/openstack/tempest/blob/a552cb93aea10fd62648f1b8d74b16a7b3e801dc/tempest/api/compute/servers/test_novnc.py#L28 | |
| 18:53:58 | mikal | Yeah, it seems a bit websockety, but it is checking for a header: https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_novnc.py#L195 | |
| 18:54:32 | sean-k-mooney | dansmith: ya that still exits as shown above ^ | |
| 18:54:52 | sean-k-mooney | we dont currently have spice in any of our nova jobs btu we could add it to any of them | |
| 18:55:08 | sean-k-mooney | the issue woudl be testing with kerbside really | |
| 18:55:17 | mikal | Where are the tempest config options set? Somewhere in the nova repo? | |
| 18:55:22 | dansmith | I think the benefit of such a test should not be understated.. there's a lot of plumbing that is verified by merely confirming that banner string | |
| 18:55:23 | sean-k-mooney | my understainding is mikal has developed kolla-ansible supprot | |
| 18:55:29 | sean-k-mooney | but we dont have devstack support | |
| 18:56:12 | mikal | Yeah, I have a prototype deployer for kolla-ansible (prototype because I am fairly sure I got HA wrong but I don't have enough machines in the lab to test right now). | |
| 18:56:13 | sean-k-mooney | dansmith: that testing is really testing the nova-spiceproxy | |
| 18:56:20 | sean-k-mooney | which is unused with spice direct | |
| 18:56:35 | sean-k-mooney | that siad i guess we coudl write the test to conenct directly to spice | |
| 18:56:41 | sean-k-mooney | like kerbside would | |
| 18:56:51 | dansmith | ...I mean, there's still spice at the other end right? | |
| 18:56:55 | sean-k-mooney | that woudl confirm the data we include in teh api is correct | |
| 18:56:56 | melwitt | would spice direct not present a html login page or something like vnc does or? | |
| 18:56:57 | mikal | I can give that a go, but I'd probably need some hand holding. | |
| 18:57:17 | sean-k-mooney | melwitt: the kerbside proxy might | |
| 18:57:22 | sean-k-mooney | but nothign in nova will | |
| 18:57:32 | mikal | melwitt: no, spice-direct just gives you connection details to the TCP ports on the hypervisor. There is then a proxy which sits in front which is not currently proposed in openstack land. | |
| 18:57:39 | melwitt | ok, i see what you're saying now | |
| 18:57:59 | gmann | we do have devstack support ? but it is not tested anywhere i think https://github.com/openstack/devstack/blob/master/lib/nova#L719 | |
| 18:58:02 | sean-k-mooney | so we can test that those conenction detail are right as an admin/service user in tempest | |
| 18:58:08 | mikal | spice-direct by itself meets shadow.tech's needs (I hope), and then I have a whole bunch of other bits to propose later once this first bit lands. | |
| 18:58:21 | sean-k-mooney | gmann: that only for spice with nova-spiceproxy | |
| 18:58:35 | sean-k-mooney | its enouch to test part of it | |
| 18:58:51 | sean-k-mooney | jsut not the kerbside part wich is probaly ok | |
| 18:59:21 | sean-k-mooney | mikal: shadow.tech can actully work with the nova-spiceproxy too | |
| 18:59:38 | sean-k-mooney | they dont actully need spice-dicret they want teh sound and usb supprot your adding at the end | |
| 19:00:27 | sean-k-mooney | they need the usb ports to do rediectoin so gaming periferals to the vm which works over the nova websocket proxy | |
| 19:00:39 | sean-k-mooney | they have there own custom spice client that can work with that | |
| 19:01:28 | sean-k-mooney | spice-direct is proably faster so they might move to that in the future, they currently deploy one nova-spice proxy per compute node to keep latency down | |
| 19:01:50 | mikal | Huh. | |
| 19:03:28 | mikal | Well, I'll go spelunking in tempest today and see what I can work out. | |
| 19:04:00 | mikal | sean-k-mooney: I'm a bit confused about your comments on the sound model patch. I am not sure if I should read them as saying that https://review.opendev.org/c/openstack/nova/+/940770/1 isn't actually needed any more. | |
| 19:04:04 | sean-k-mooney | anyway i think that off topic. the minium useful tempets test would use the new api microverion to get the connecction info kerbside would use adn then check the banner | |
| 19:04:53 | sean-k-mooney | it looks like i didt push my late set of comemtns one sec | |
| 19:05:15 | sean-k-mooney | ok i ment to push them this morning | |
| 19:05:35 | sean-k-mooney | mikal: that is still needed | |
| 19:05:44 | sean-k-mooney | it shoudl be merged into the previous change | |