| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-09-08 | |||
| 17:29:04 | fungi | just making sure it's not slipped through the cracks | |
| 17:30:55 | sean-k-mooney | i need to readd the conflcit lines | |
| 17:31:07 | sean-k-mooney | but i have been swapped with downstream issues | |
| 17:31:29 | sean-k-mooney | so i have not had time to work on it | |
| 17:32:30 | fungi | no worries, take your time, i simply didn't want an exploitable vulnerability hanging out there any longer than necessary | |
| 17:32:42 | sean-k-mooney | ya fair | |
| 17:32:53 | sean-k-mooney | ill see if i can get to it but that all that is holding it up | |
| 17:33:07 | sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/806626/1//COMMIT_MSG#16 | |
| 17:33:09 | fungi | okay, cool. thanks again | |
| 19:03:37 | opendevreview | Elod Illes proposed openstack/nova stable/victoria: address open redirect with 3 forward slashes https://review.opendev.org/c/openstack/nova/+/806626 | |
| 19:06:49 | elodilles | sean-k-mooney: i've updated the commit message ^^^ please edit it if it is needed o:) | |
| 20:45:08 | mnaser | anyone by any chance the historical reasoning of instance_id_mappings table? | |
| 20:46:05 | mnaser | wait, they don't even match up | |
| 20:46:24 | mnaser | i mean, uuid = uuid, but id != id | |
| 21:38:22 | melwitt | mnaser: found this with git blame https://github.com/openstack/nova/commit/0dc32690fe158e4cb11c2c9bcc65acaf73b94a7a | |
| 21:39:11 | mnaser | melwitt: oooooooooh nice find | |
| 21:39:42 | melwitt | :) | |
| #openstack-nova - 2021-09-09 | |||
| 07:12:29 | gibi | good morning | |
| 07:56:48 | bauzas | gibi: good morning | |
| 07:57:12 | bauzas | was mostly off the grid yesterday due to a hell day with customer escalations | |
| 08:01:28 | gibi | not much happened upstream yestrday here either | |
| 08:10:30 | bauzas | gibi: in case you haven't seen it, i eventually found the problem with my prelude change | |
| 08:10:52 | bauzas | one single line was badly indented by one char | |
| 08:11:03 | bauzas | but not the one which was returning the error | |
| 08:11:08 | bauzas | ... | |
| 08:13:08 | gibi | yepp, I +2d the prelude yestearday. thank you for writing it | |
| 08:19:41 | kashyap | bauzas: Then how did you discover it? If it's not the line that caused the error :-) | |
| 08:20:10 | bauzas | kashyap: I still use my eyes in general | |
| 08:20:20 | kashyap | Hehe | |
| 08:20:29 | bauzas | automated coding isn't an option yet, I'm afraid | |
| 08:20:34 | bauzas | I should ask elon to propose it | |
| 08:23:27 | kashyap | bauzas: GitHUb has some ideas with their <clears-throat> "Copilot" | |
| 08:23:34 | kashyap | bauzas: But, look - https://www.techradar.com/news/github-autopilot-highly-likely-to-introduce-bugs-and-vulnerabilities-report-claims | |
| 08:23:57 | kashyap | "researchers discover that nearly 40% of the code suggestions by GitHub’s Copilot tool are erroneous, from a security point of view" | |
| 08:24:03 | kashyap | But LOL, as if that's a surprise! | |
| 08:24:50 | bauzas | kashyap: you get the same experience with Tesla Full Self Driving which was proposed since a while | |
| 08:25:12 | bauzas | the only difference being that a car bug leads to some injury :D | |
| 08:25:25 | kashyap | I don't drive; so ignore cars altogether :D I'm more interested in long-distance electric bikes :D | |
| 08:25:57 | bauzas | I switched 70% of my drives to be full electric, I'm chasing down the last 30% bits | |
| 08:26:15 | bauzas | but that will require hardware upgrade | |
| 08:26:53 | bauzas | kashyap: excellent choice, btw. do you have government incentives for this like in France ? | |
| 08:28:40 | kashyap | bauzas: I was told there are; but I need to dig in still | |
| 08:29:15 | kashyap | bauzas: I got more energized about it after my recent hiking in the Alps. | |
| 08:31:10 | bauzas | kashyap: sure, but mountain e-bikes are way different | |
| 08:31:18 | kashyap | bauzas: Oh, sure | |
| 08:31:46 | kashyap | I was not mixing them up. Just noticing how people were doing long-distance rides there w/ e-bikes made me think about it more | |
| 08:32:24 | bauzas | kashyap: https://mobilit.belgium.be/nl/mobiliteit/personenvervoer/fiets ;) | |
| 08:33:17 | kashyap | bauzas: Hehe, thank you. Yeah, NL and FR are treated as first-class citizens on most web pages | |
| 08:33:29 | kashyap | bauzas: I knew this existed, just didn't bother to investigate | |
| 08:36:14 | bauzas | kashyap: surprinsingly, most of the incentives seem to be only for the Brussels and the Wallony regions | |
| 08:36:28 | bauzas | afaicr, Ghent is in Flanders, right? | |
| 08:36:36 | kashyap | bauzas: Yes, it is | |
| 08:36:52 | kashyap | That's very odd, though. | |
| 08:36:58 | kashyap | bauzas: LOL, no, thank you | |
| 08:37:22 | bauzas | there is a fun fact here | |
| 08:37:54 | bauzas | if you want to buy an electric car, the gov gives you a discount of 7k€ if the car is below 45k€ | |
| 08:38:17 | kashyap | Nice, that's quite a chunky amount | |
| 08:38:39 | bauzas | but, if you live in the Marseille area, the local city gov gives you an extra 5k | |
| 08:39:34 | bauzas | so, lots of people are considering some way to address their primary location as some random Marseille place | |
| 08:40:50 | kashyap | Heh | |
| 08:40:58 | gibi | those are nice summs indeed | |
| 08:43:48 | gibi | here we have ~5k€ subsidise for full electric cars (and free parking) | |
| 08:44:21 | gibi | but for cars < 35k€ | |
| 08:47:45 | kashyap | I do hope people are taking advantage of it; I guess it's a win-win | |
| 08:48:50 | bauzas | kashyap: we do | |
| 08:49:21 | bauzas | we have two cars, one is full electric (a peugeot 208) and one is plugin-hybrid (a skoda superb) | |
| 08:49:52 | bauzas | even with the hybrid which has 40km+ electric range, we try to do 100% of our drives to be electric | |
| 08:50:09 | kashyap | Nice; /me learned first time of plugin-hybrid | |
| 08:50:33 | bauzas | as a consequence, we use the 208 (which is a compact car) for one-day drives around our region | |
| 08:50:58 | bauzas | and we only take the superb for trips above 200 kms which requires lots of leg space | |
| 08:51:31 | bauzas | I hate now refuelling | |
| 08:51:37 | bauzas | this is expensive and it stinks | |
| 08:52:24 | gibi | bauzas: if you feel the power, then could you please review https://review.opendev.org/c/openstack/placement/+/807014 I think (and CI thinks) it is good and fixing the transaction issue | |
| 08:52:31 | bauzas | hopefully next year, we'll change the superb to a new electric vehicle, because we tested long-range trips with intermediary recharges, and this works | |
| 08:52:47 | bauzas | gibi: excellent point, I need to look at this one | |
| 08:52:56 | bauzas | gibi: I also need to amend the vgpu doc | |
| 08:53:56 | gibi | and if you are at placement land then https://review.opendev.org/c/openstack/placement/+/807155 is simple and fixes a bug in consumer_types | |
| 08:53:59 | bauzas | gibi: I guess melwitt addressed your excellent concern ? | |
| 08:54:06 | songwenping_ | hi,team, is any entry to delete compute node except nova service-delete? | |
| 08:54:28 | gibi | bauzas: yes, she added a independent transaction for re-reading the rp data in the retry loop, and it seems to work well | |
| 08:54:34 | bauzas | songwenping_: you shouldn't delete the compute node entries | |
| 08:54:55 | bauzas | songwenping_: either the virt driver or the service deletion can do this | |
| 08:55:19 | songwenping_ | how virt driver works? | |
| 08:57:09 | kashyap | songwenping_: The bird's-eye view is this: | |
| 08:57:42 | kashyap | nova-api (in coordination with nova-scheduler) --> nova-compute (virt driver) --> launches libvirtd --> launches QEMU | |
| 08:57:55 | kashyap | But you have to be more specific for people to answer :) | |
| 08:59:01 | songwenping_ | no, i means which scenes virt driver delete the compute node? | |
| 09:16:15 | bauzas | songwenping_: sorry, I need to jump off for 30 mins | |
| 09:16:38 | bauzas | but basically, the virt driver gives the inventories and the compute nodes to the RT which creates the necessary records | |
| 09:16:43 | bauzas | RT : ResourceTracker | |
| 09:17:13 | bauzas | as the RT is run by the nova-compute service, you need to delete the service | |
| 09:17:50 | bauzas | there is a tight relationship between an RPC service (the nova-compute manager) and the compute node record | |
| 11:15:56 | songwenping_ | hi, team, anybody knows why placement check source node resource when evacuate VM? | |
| 11:19:19 | sean-k-mooney | how do you mean | |
| 11:19:29 | sean-k-mooney | as it it can include the source host in the set of host returned | |
| 11:21:03 | sean-k-mooney | that would be because we do not currently filter host but just up hosts | |
| 11:21:08 | sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/scheduler/request_filter.py#L241-L254 | |
| 11:21:16 | sean-k-mooney | we do filter hosts by there disabeld status however | |
| 11:21:39 | sean-k-mooney | so fi you had dissbled the host you are evacuatating form then it would not be included in the placment query | |
| 11:22:30 | sean-k-mooney | songwenping_: the source node will be elimiated by the scudler after the placment query so it does not really have a negitive impact to include it | |