| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-02-10 | |||
| 10:25:40 | bauzas | but I used to love playing RTS | |
| 10:28:28 | elodilles | bauzas: SC1 or SC2? :D | |
| 10:28:59 | bauzas | elodilles: dude, I'm 42, what do you expect ? | |
| 10:29:57 | elodilles | bauzas: 'same applies here' ;) | |
| 10:30:07 | gibi | SC1 2vs2 battle net was nice | |
| 10:30:36 | gibi | we tried SC2 2vs2 but it does not felt the same. (we probably got old) | |
| 10:30:37 | sean-k-mooney | its much simpler to get into a productive flow with factorio | |
| 10:31:06 | sean-k-mooney | that said did you know there are prometious exporters for factorio s you can visualise your factory in graphana | |
| 10:31:12 | bauzas | and when I say C&C, I really mean C&C 1 | |
| 10:31:16 | bauzas | and Red Alert | |
| 10:31:22 | bauzas | (mostly Red Alert actually) | |
| 10:31:29 | elodilles | :) | |
| 10:31:57 | bauzas | gibi: LAN parties with Starcraft 2x2 were gorgeous indeed | |
| 10:32:29 | elodilles | I'm so old that i time to time play WarCraft1 campaign just for "fun" >:D | |
| 10:32:32 | sean-k-mooney | peopel have litrally confiruted really monitoring systems to monitor there virtual factory and raise alerts when you run out of ore.... that is more investment then i can put into any game | |
| 10:32:57 | bauzas | sean-k-mooney: oh man, that's way too much addictive | |
| 10:33:38 | sean-k-mooney | bauzas: you should play it its fun | |
| 10:34:03 | sean-k-mooney | just make sure you have good posture when you do because you might blink and realise its been 3 hours without moving | |
| 10:38:18 | gibi | sean-k-mooney: if we loose bauzas on factortio then you need to be the next nova PTL as a punishment :) | |
| 10:38:36 | sean-k-mooney | lol | |
| 10:39:01 | sean-k-mooney | surpisingly that does not narrow it down much | |
| 10:40:50 | bauzas | Ogame, got it | |
| 10:41:14 | bauzas | that one stole too much of my free time | |
| 10:49:25 | bauzas | gibi: about https://review.opendev.org/c/openstack/nova/+/821228/6/nova/virt/libvirt/host.py#745 I wonder whether we really need to call *again* getCPUMap() | |
| 10:49:43 | bauzas | gibi: the existing logic just considers to return the cpu blindless | |
| 10:49:48 | bauzas | blindly | |
| 10:50:27 | bauzas | but I see your point | |
| 10:50:32 | bauzas | nevermind | |
| 10:51:24 | gibi | bauzas: you probably still need to differentiate between non existent cpu ids in the dedicated_set and existing but offined cpus | |
| 10:52:00 | bauzas | yeah, I'm about adding a get_available_cpus() which will return all CPUs for the map | |
| 10:53:23 | gibi | yeah that will work | |
| 10:59:45 | kashyap | bauzas: What exactly does getCPUMap() fetch? The docs only say "Get node CPU information" | |
| 11:00:12 | kashyap | Ah, it maps to `virsh cpu-stats` | |
| 11:00:57 | bauzas | yup | |
| 11:01:01 | kashyap | Oh, interesting. When I run `virsh cpu-stats` on my Fedora 36 VM for a guest, it gives me: | |
| 11:01:05 | bauzas | https://libvirt.org/html/libvirt-libvirt-host.html#virNodeGetCPUMap | |
| 11:01:12 | kashyap | $> sudo virsh cpu-stats 1 | |
| 11:01:13 | kashyap | error: Operation not supported: operation 'getCpuacctPercpuUsage' not supported for backend 'cgroup V2' | |
| 11:01:13 | kashyap | error: Failed to retrieve CPU statistics for domain 'el8-vm1' | |
| 11:01:25 | bauzas | [sbauza@sbauza temp]$ python | |
| 11:01:26 | kashyap | bauzas: Yeah, was reading. It looks like there's some accounting to be done w.r.t CGroups version | |
| 11:01:26 | bauzas | >>> conn = libvirt.open('qemu:///system') | |
| 11:01:26 | bauzas | >>> import libvirt | |
| 11:01:26 | bauzas | Type "help", "copyright", "credits" or "license" for more information. | |
| 11:01:26 | bauzas | Python 3.11.1 (main, Jan 6 2023, 00:00:00) [GCC 12.2.1 20221121 (Red Hat 12.2.1-4)] on linux | |
| 11:01:27 | bauzas | >>> conn.getCPUMap() | |
| 11:01:29 | bauzas | (8, [True, True, True, True, True, True, True, True], 8) | |
| 11:01:55 | kashyap | Yep | |
| 11:10:42 | sean-k-mooney | you can also just get the online cores form sysfs | |
| 11:11:18 | sean-k-mooney | if this is an issue but im fine with using libvirt's api for this | |
| 11:16:12 | bauzas | I'm done with the new rev, just updating the upper patch now | |
| 11:24:22 | sean-k-mooney | my steamdeck is charging so im currently still at my work laptop.(playing factorio) so gibi if your happy to review bauzas serise and it looks good to you ping me when your done and i can then do a final pass over it quickly and we can likely merge that today. with that said i have a doctors apointmen in a littel over 3 hours so ill be away after that. | |
| 11:24:38 | bauzas | that's a love | |
| 11:24:52 | auniyal | O/ | |
| 11:24:57 | gibi | sean-k-mooney: ack | |
| 11:25:04 | auniyal | in devstack is there a way to see nova-manage logs | |
| 11:25:20 | bauzas | I'm honestly torn, I don't know whether we should really pay attention to ignoring errors | |
| 11:25:36 | bauzas | and whether we should be cautious | |
| 11:25:55 | bauzas | honestly, we create a temp dir, so I don't except problems besides the full disk problem | |
| 11:26:11 | sean-k-mooney | you should not get any now with the way the fixture works | |
| 11:26:17 | bauzas | so I'll turn into using the .cleanup() method | |
| 11:26:22 | bauzas | and meh | |
| 11:26:30 | bauzas | meh to ignoring errors | |
| 11:26:42 | gibi | I'm fine ignoring errors | |
| 11:26:49 | gibi | during delete of a temp dir | |
| 11:27:00 | gibi | we will never reuse the temp dir as it has a random postfix | |
| 11:27:05 | sean-k-mooney | the flag is only there in 3.10 | |
| 11:27:09 | gibi | if my /tmp fills up that is on me | |
| 11:27:10 | sean-k-mooney | and we need to support 3.8 | |
| 11:27:17 | gibi | aah | |
| 11:27:21 | bauzas | gibi: that's the problem | |
| 11:27:26 | sean-k-mooney | so its fine for it to error | |
| 11:27:28 | sean-k-mooney | it wont | |
| 11:27:29 | gibi | ahh | |
| 11:27:30 | bauzas | we can't say 'ignore errors' if we use cleanup | |
| 11:27:38 | bauzas | hence me torn | |
| 11:27:41 | gibi | I'm fine both ways | |
| 11:27:41 | sean-k-mooney | i could have errored when we had the copy of sysfs because of some permision | |
| 11:27:51 | sean-k-mooney | but now its just normal files owned by us | |
| 11:27:54 | bauzas | correct | |
| 11:28:00 | gibi | if it starts failing on cleanup then we will switch to shutil | |
| 11:28:01 | sean-k-mooney | so it wont error unless there is a disk issue which si out of scope | |
| 11:28:08 | bauzas | yup, this ^ | |
| 11:28:09 | sean-k-mooney | +1 | |
| 11:28:44 | bauzas | I'll add a comment explaining the risk and how to mitigate it if we see it in CI | |
| 11:29:39 | gibi | cool | |
| 11:39:48 | bauzas | sean-k-mooney: gibi: I haven't yet written the docs patch as it requires a bit of effort, so I'll keep your comments on it unresolved but don't misunderstand me, surely I'll do it in a subsequent patch once I'm done (monday morning hopefully) | |
| 11:39:58 | bauzas | I just wanna give chance to other people to get reviewed | |
| 11:40:14 | gibi | bauzas: sure, doc is OK after FF | |
| 11:40:22 | sean-k-mooney | ya it can be a seperate patch | |
| 11:40:47 | bauzas | the core #0 note is actually very important | |
| 11:40:49 | bauzas | TIL about it | |
| 11:41:13 | bauzas | but yeah that makes sense from an OS perspective | |
| 11:41:21 | bauzas | you always rely on that core to be available | |
| 11:41:50 | bauzas | that's the most portable assumption | |
| 11:42:04 | sean-k-mooney | ya it generally need one core that can always be used to handel interupts and you know turn on the others | |
| 11:43:14 | sean-k-mooney | bauzas: that is why there is no online file in /sys/bus/cpu/devices/cpu0/ | |
| 11:43:24 | sean-k-mooney | but there is in all the rest | |
| 11:44:07 | bauzas | ooooooooh | |
| 11:44:39 | bauzas | but you can write an online file and set 0 into it for core #0, right ? | |