)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"fa049ec3fedf990ae7c0a6a57e4ba077b0cebd5d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d590faf9_ed62541c","updated":"2023-04-12 08:15:00.000000000","message":"I agree on the deprecation signal, but I\u0027m afraid of the backport we may do for Antelope.\nSince it will only be released by a minor stable version, we won\u0027t have it in the main 27.0.0 release notes so operators could miss it.","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"e2dacfb22ec5eac4644ecf2daa8d406da2194b01","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fb74e98d_7ee431cd","updated":"2023-04-12 01:01:51.000000000","message":"I am ok with this and also backport to reflect the reality. But explicitly using \u0027Deprecated\u0027 term on this release onwards can be more clear.","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bed8d71625fca01c8d1634109274e66c447e4786","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1e9c0f6b_479b72f4","updated":"2023-04-11 19:46:52.000000000","message":"In TC, we are checking if we need to retire the winstacker project (os-win) and it we end up retiring that then we need to remove HyperV driver itself? In that case, we should mark it \u0027Deprecated\u0027 explicitly ?","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"eb523f07993d1b000b3444c0f7ccb1d93b362be1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b8ec966d_5b755b5c","updated":"2023-04-12 08:18:38.000000000","message":"Putting a procedural hold since I\u0027d want the Nova community to agree on the deprecation by the next nova team meeting.","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"de4099739282569a71d9308d724d8af46e3f8385","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"792aaf0a_02515742","updated":"2023-04-19 09:19:53.000000000","message":"recheck unrelated failure","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"df7c0c03f3052ee1d1ac8a5e92f259ec89cd9439","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7fe89a50_9133cfa4","updated":"2023-04-11 19:49:20.000000000","message":"we missed doing this in the antelope release and i think we should not only do this but we should backport it to antelope in like of https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044.html","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"09ffc277a0df2d8a6c30b6af53771771f289686b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9875f26b_e0064d18","in_reply_to":"36b4d5df_b02edbab","updated":"2023-04-18 17:09:11.000000000","message":"We eventually captured an agreement on IRC [1]\nI\u0027ll write it here as a comment to clarify :\n\n- we agree on deprecating the hyperv driver in 2023.2.\n- we agree on backporting the deprecation to the 2023.1 branch which will only be seen in a minor stable release (probably 27.1.0)\n- we agree on exceptionnally mentioning the deprecation in the 2024.1 release notes (well, this thing will be done by myself, who then puts a huge responsibility on his shoulders but eventually agrees with some kind of reluctance)\n\nMy personal preference would have been to delay the deprecation to the next SLURP release, but given this patch is more a signal asking and begging for help rather than a technical thing, I surely understand the need and I fully accept it.\n\n\n[1] https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2023-04-18.log.html#t2023-04-18T16:57:46","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bbf8526cfafaf9ea3a002c20babc6983db81e41c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"36b4d5df_b02edbab","in_reply_to":"d590faf9_ed62541c","updated":"2023-04-13 20:25:52.000000000","message":"this is not best situation but if we see the situation here, I now agree with Sean idea of backporting to Antelope is best possible way:\n\n1. if os-win is retiring in this cycle (high possibility) then HyperV driver code is not usable as it has hard deps on os-win.\n\n2. Best way in this situatin is to remove HyperV driver in this or at least in next cycle.\n\n3. If we backport warning to Antelope then at least we will be notifying operator about it in at least one SLURP release.","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"}],"nova/virt/hyperv/driver.py":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"a4f39f5cceb9b4fdd62a3d68097b5651770654e2","unresolved":true,"context_lines":[{"line_number":151,"context_line":"            \u0027does it have clear maintainer(s) and thus its quality can not be \u0027"},{"line_number":152,"context_line":"            \u0027ensured. It should be considered experimental and may be removed \u0027"},{"line_number":153,"context_line":"            \u0027in a future release. If you are using the driver in production \u0027"},{"line_number":154,"context_line":"            \u0027please let us know via the openstack-discuss mailing list.\u0027"},{"line_number":155,"context_line":"        )"},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"        self._serialconsoleops.start_console_handlers()"}],"source_content_type":"text/x-python","patch_set":1,"id":"3d5353b0_425e850c","line":154,"updated":"2023-04-11 20:37:00.000000000","message":"Same argument as the vmware one. The interesting thing is that the 2022 user survey indicates that 2% of users are running the hyperv driver. However, I suspect that\u0027s actually the out-of-tree one, and not this one.","commit_id":"9baade7ea16d8273c6cd139d6a0c4cdb9de716f7"}]}