)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"140a62767e2b68ecb9b779f4060fdfabf00ad58b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e059e51a_44b574d8","updated":"2026-11-04 05:54:33.000000000","message":"Thank you for describing the proposed design with highlighting how existing bugs are also getting addressed.","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ec724d44a8212552c8eadb0a4633590c7d43f511","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a7546af8_5a8b2a5a","updated":"2026-11-06 18:00:38.000000000","message":"as with the parent im not seeing any outstanding objectsion or question.\n\ni will add this to the adjenda for the next irc meeting and we will aim to merge this next week if there are no outstadning concerns","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"d5daeee0d270604fd57a5f9a648d7a49d5cf0da9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7c96b0b7_0b08bb4d","updated":"2026-11-02 12:01:29.000000000","message":"lgtm, the changes are clearly explained. The spec has grown in scope since it was originally introduced, but the differences are well described in the history table and throught the text","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"691e0f07ed156cbee7330ca35cdecbf557aa95a8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"61598f2b_480cb212","in_reply_to":"7c96b0b7_0b08bb4d","updated":"2026-11-02 15:43:39.000000000","message":"yes my over all plan is to fix the bugs first then resumt the feature from that baseline after we implemnt the ovo inderction api.\n\nso the patch order is going to be 3 bug fixs then ovo indirection then the managed mode will build on top of that foundation so the feature itself is proably the same size but i have now identifet the tech debt we need to adress first and layed that out in the spc","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"}],"specs/2027.1/approved/support-vfio-variant-driver-managed-mode.rst":[{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"140a62767e2b68ecb9b779f4060fdfabf00ad58b","unresolved":true,"context_lines":[{"line_number":158,"context_line":"* As an operator, I would like to retain my existing PCI configuration"},{"line_number":159,"context_line":"  during the 2027.1 upgrade because I need time to adopt ``device_spec``"},{"line_number":160,"context_line":"  before the old-name fallback is removed in 2027.2."},{"line_number":161,"context_line":"* As a Nova developer, I would like to know whether a device is stateful"},{"line_number":162,"context_line":"  because resize and cold-migration safety decisions depend on whether"},{"line_number":163,"context_line":"  its data needs preservation or transfer."},{"line_number":164,"context_line":"* As a Nova developer, I would like device NUMA locality information"},{"line_number":165,"context_line":"  because future guest topology support needs to describe device locality"},{"line_number":166,"context_line":"  without treating that reporting as an affinity constraint."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ac3e86a6_796fcb1b","line":163,"range":{"start_line":161,"start_character":0,"end_line":163,"end_character":42},"updated":"2026-11-04 05:54:33.000000000","message":"+1 for including the usecase for stateful devices.","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ec724d44a8212552c8eadb0a4633590c7d43f511","unresolved":true,"context_lines":[{"line_number":158,"context_line":"* As an operator, I would like to retain my existing PCI configuration"},{"line_number":159,"context_line":"  during the 2027.1 upgrade because I need time to adopt ``device_spec``"},{"line_number":160,"context_line":"  before the old-name fallback is removed in 2027.2."},{"line_number":161,"context_line":"* As a Nova developer, I would like to know whether a device is stateful"},{"line_number":162,"context_line":"  because resize and cold-migration safety decisions depend on whether"},{"line_number":163,"context_line":"  its data needs preservation or transfer."},{"line_number":164,"context_line":"* As a Nova developer, I would like device NUMA locality information"},{"line_number":165,"context_line":"  because future guest topology support needs to describe device locality"},{"line_number":166,"context_line":"  without treating that reporting as an affinity constraint."}],"source_content_type":"text/x-rst","patch_set":1,"id":"2d4dea87_45beec47","line":163,"range":{"start_line":161,"start_character":0,"end_line":163,"end_character":42},"in_reply_to":"ac3e86a6_796fcb1b","updated":"2026-11-06 18:00:38.000000000","message":"we briefly discussed this in the ptg wrap up.\n\nit technially could be doen seprately but i was ok to incldue it in this spec.\n\nif we feell like it shoudl be its won microversion ectra i could change it but ill resovle this thread for now unless other have concerns with the scope increase.","commit_id":"e8247aef1ebd3c0bb8efeb0a4b98c429562b3e20"}]}
