)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"8607a2f563836fd9b8a4102fde63091aba843d0f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7cc106cd_3bc44baa","updated":"2026-07-24 10:51:03.000000000","message":"@smooney@redhat.com Hello, please merge it, clean backport, thank you.","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"9d6ac39ea4dd5ec0dbc15489a7d6ca0e4231b184","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"02fd5b66_50e86886","updated":"2026-07-22 15:03:13.000000000","message":"Bug fix looks valid to me to be backported. Besides, clean cherry pick from master branch, where the patch has merged. LGTM.","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"edc3cc3a740a4fef103b2ce966fa6133960d6698","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"46a9057e_7f16ff84","updated":"2026-07-25 00:09:54.000000000","message":"Clean backport of a bug fix suitable for stable, LGTM","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"b0be783cf248b7e4a797c21ce6281a5546562685","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"91865a2c_2a9c61c2","updated":"2026-07-27 11:10:00.000000000","message":"as an aside there are 3-4 other patches that i have/am buildin gon top o fthis one to optimisze the startup time more. this patch is imporant in that effort but once the final few patches are merged ill follow up with a backport of the stack\n\nwith that said backportign this earlier is one less patch for me to wragle when we get to that point so im fine with this\n\nspecficly https://review.opendev.org/c/openstack/nova/+/990551 and the 3 patches that follow.\n\ntoday we are pulling all the instnace on a gven compute node twice on startup\n\nwith this patch we lazy load the flavor/image data in one of the two code paths\n\nwith https://review.opendev.org/c/openstack/nova/+/990552/5 we remove the second already optimiszed load entrily.\n\nhttps://review.opendev.org/c/openstack/nova/+/980676/7\nand\nhttps://review.opendev.org/c/openstack/nova/+/980679/4\nare much more imporant for ironic and perhaps vmware but every bit helps.","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"65025594866771be7788d452b2565f27c0ae0fcc","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4533d691_b320463b","in_reply_to":"4fbbec64_8d8a494d","updated":"2026-07-29 12:30:24.000000000","message":"that would be a new wishlist perfoermce bug or specless blueprint\n\ni think we could dicuss a simplar optimsation to https://review.opendev.org/c/openstack/nova/+/980679 but that i off topic of this current reivew\n\nnow hta twe have executors that we can dispatch work too as a normal part of nova\u0027s operation we can look for other optrunities to use them for background tasks like perfodic or instance startup on host reboot.\n\ni mentioned the other patches as i was orginlly plannign to try an backport them as a block of patches once the last two im workign on have merged we coudl fiel a bug for the instnace tstart perfeormace and tack that on top.","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"},{"author":{"_account_id":36998,"name":"Ilia Baikov","display_name":"Ilia Baikov","email":"ilia.baikov@ib.systems","username":"frct1"},"change_message_id":"bbdbf6df49ed5b5cb1b30dca6190fa9df5a5df6c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4fbbec64_8d8a494d","in_reply_to":"91865a2c_2a9c61c2","updated":"2026-07-29 11:33:42.000000000","message":"I\u0027ve been asked by one of OpenStack operators from community about instances that automatically restarting after host failure (conf option resume_guests_state_on_host_boot) and it seems today it is done sequentially. What do you think about implementing a sliding window logic parallelizing instance start? May be like booting 5 to 10 instances in parallel would significantly speed up host boot after a failure.","commit_id":"c9fc0d09d16e016ba5d7ccfc483ab20401e30715"}]}