)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"29a29584de2577208c9ff8a52e69c3098e015b00","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8e9d4e75_6c0bf43d","updated":"2022-10-20 12:39:25.000000000","message":"I\u0027ll be AFK from 2022-10-24 to 2022-11-01, but all your input is welcome and I\u0027ll be addressing your comments when I\u0027m back.","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"}],"specs/2023.1/ovs-tx-steering.rst":[{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"6e0cbb8ef7efb3428f0a564d1f1c4f4deabbee1c","unresolved":true,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"``port-hints`` adds a new port attribute: ``hints``.  Its default"},{"line_number":31,"context_line":"policy is ``admin_only``.  Its value is a dict (by default empty)."},{"line_number":32,"context_line":"The dict is keyed by the standard mechanism driver aliases as in [4]_."},{"line_number":33,"context_line":"The value for a mechanism_driver is possibly a complex structure, but at"},{"line_number":34,"context_line":"least a dict on the top level.  In this spec we only partially define its"},{"line_number":35,"context_line":"format - introducing one hint. This is marked by the second extension"}],"source_content_type":"text/x-rst","patch_set":1,"id":"509e6d96_7cb73c07","line":32,"range":{"start_line":32,"start_character":25,"end_line":32,"end_character":58},"updated":"2022-11-02 10:14:18.000000000","message":"Isn\u0027t that too general? That list contains a lot of fake and test agents, and l3 also. I would only allow OVS and OVN, or for l2 mech drivers only.","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"e6bdeff58cc2928057526243f7b59d9a3e624124","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"``port-hints`` adds a new port attribute: ``hints``.  Its default"},{"line_number":31,"context_line":"policy is ``admin_only``.  Its value is a dict (by default empty)."},{"line_number":32,"context_line":"The dict is keyed by the standard mechanism driver aliases as in [4]_."},{"line_number":33,"context_line":"The value for a mechanism_driver is possibly a complex structure, but at"},{"line_number":34,"context_line":"least a dict on the top level.  In this spec we only partially define its"},{"line_number":35,"context_line":"format - introducing one hint. This is marked by the second extension"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a8cd64c8_8eb18181","line":32,"range":{"start_line":32,"start_character":25,"end_line":32,"end_character":58},"in_reply_to":"509e6d96_7cb73c07","updated":"2022-11-03 10:21:40.000000000","message":"Done","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"6e0cbb8ef7efb3428f0a564d1f1c4f4deabbee1c","unresolved":true,"context_lines":[{"line_number":33,"context_line":"The value for a mechanism_driver is possibly a complex structure, but at"},{"line_number":34,"context_line":"least a dict on the top level.  In this spec we only partially define its"},{"line_number":35,"context_line":"format - introducing one hint. This is marked by the second extension"},{"line_number":36,"context_line":"``port-hint-ovs-tx-steering``.  Definition of other hints is left to"},{"line_number":37,"context_line":"future specs. Here consider this partial body for a create port request:"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bae71b87_77a0524e","line":36,"range":{"start_line":36,"start_character":2,"end_line":36,"end_character":27},"updated":"2022-11-02 10:14:18.000000000","message":"Could you draft out how you plan the extensions will look like? especially port-hint-ovs-tx-steering? will it be only a shim exptension?","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"e6bdeff58cc2928057526243f7b59d9a3e624124","unresolved":false,"context_lines":[{"line_number":33,"context_line":"The value for a mechanism_driver is possibly a complex structure, but at"},{"line_number":34,"context_line":"least a dict on the top level.  In this spec we only partially define its"},{"line_number":35,"context_line":"format - introducing one hint. This is marked by the second extension"},{"line_number":36,"context_line":"``port-hint-ovs-tx-steering``.  Definition of other hints is left to"},{"line_number":37,"context_line":"future specs. Here consider this partial body for a create port request:"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a5d3b2b0_d229ef0f","line":36,"range":{"start_line":36,"start_character":2,"end_line":36,"end_character":27},"in_reply_to":"bae71b87_77a0524e","updated":"2022-11-03 10:21:40.000000000","message":"Done","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":32586,"name":"Elvira García Ruiz","display_name":"Elvira","email":"egarciar@redhat.com","username":"elvira"},"change_message_id":"b0c410b0b70d488656ef35352e83af82879d9870","unresolved":true,"context_lines":[{"line_number":51,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":52,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"``hints`` can be set at port create or update, but there\u0027s particularly"},{"line_number":55,"context_line":"no guarantee that an update to the hints after the port was bound will"},{"line_number":56,"context_line":"have any effect."},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"98c6dc62_0d9a6be9","line":54,"range":{"start_line":54,"start_character":59,"end_line":54,"end_character":71},"updated":"2022-11-01 18:05:57.000000000","message":"very small nit: I think it might not be necessary to put particularly here again, it is also written on the previous paragraph.","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"e6bdeff58cc2928057526243f7b59d9a3e624124","unresolved":false,"context_lines":[{"line_number":51,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":52,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"``hints`` can be set at port create or update, but there\u0027s particularly"},{"line_number":55,"context_line":"no guarantee that an update to the hints after the port was bound will"},{"line_number":56,"context_line":"have any effect."},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"118a4db9_5c05e9a2","line":54,"range":{"start_line":54,"start_character":59,"end_line":54,"end_character":71},"in_reply_to":"98c6dc62_0d9a6be9","updated":"2022-11-03 10:21:40.000000000","message":"Done","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"6e0cbb8ef7efb3428f0a564d1f1c4f4deabbee1c","unresolved":true,"context_lines":[{"line_number":55,"context_line":"no guarantee that an update to the hints after the port was bound will"},{"line_number":56,"context_line":"have any effect."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":59,"context_line":"not be affecting the binding process and decision."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"In the ``openstack`` CLI we propose to expose the above API feature as:"},{"line_number":62,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"0ed8189c_014efd68","line":59,"range":{"start_line":58,"start_character":58,"end_line":59,"end_character":50},"updated":"2022-11-02 10:14:18.000000000","message":"+1","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"e6bdeff58cc2928057526243f7b59d9a3e624124","unresolved":false,"context_lines":[{"line_number":55,"context_line":"no guarantee that an update to the hints after the port was bound will"},{"line_number":56,"context_line":"have any effect."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":59,"context_line":"not be affecting the binding process and decision."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"In the ``openstack`` CLI we propose to expose the above API feature as:"},{"line_number":62,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1cbd2310_52985ae1","line":59,"range":{"start_line":58,"start_character":58,"end_line":59,"end_character":50},"in_reply_to":"0ed8189c_014efd68","updated":"2022-11-03 10:21:40.000000000","message":"Ack","commit_id":"f722636ef47f076034a3a23f8c89dd73fde2a91a"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"1b94cdb7a7dd40f58e1d390ffc45e21347542174","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ec578fa1_d510555f","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"updated":"2022-11-03 16:24:51.000000000","message":"How a user would know if hints were applied or not?","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"c9e0e10b50a23af324aa82479213bd2e380a7877","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"b55945c8_cf9d6176","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"34e37152_e02c5ff7","updated":"2022-11-08 15:26:13.000000000","message":"Cool, I think \"API Impact\" section can be useful in this regard","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"2a29a7608f48d6658ce0792a6965f58bb0743b35","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ae8ea622_6cee4686","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"854cc137_ede487a0","updated":"2022-11-07 13:25:00.000000000","message":"\u003e Do you mean you don\u0027t want to expose those new fields in port GET API response? Why?\n\nThis is not what I meant.\n\n\u003e I mean the one who set those \"hints\" on port creation - how would she/he know if it was applied or not?\n\nI see two possible ways:\n\n1) We introduce another port attribute: hint_status, a dict with keys for the hint aliases and the usual status values, like: BUILD/ACTIVE/ERROR. For example:\n\nport[\"hint_status\"] \u003d {\"ovs-tx-steering\": \"ACTIVE\"}\n\n2) Or that we omit this (hint_status) attribute and don\u0027t give feedback on the API. Then the user would only know about the effect of a hint via ad hoc ways, like the cloud admin communicating/documenting, which hints make sense in a particular deployment.\n\nThe spec currently proposes (2), but I\u0027m also open to (1).","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"f37cd52d22bd5aa3a319ccec90f8925a6b57d1b6","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"854cc137_ede487a0","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"991d847f_470558f4","updated":"2022-11-05 04:19:59.000000000","message":"\u003e In this spec version I\u0027m entertaining the idea that the user does not know this.\n\nI mean the one who set those \"hints\" on port creation - how would she/he know if it was applied or not?\n\nDo you mean you don\u0027t want to expose those new fields in port GET API response? Why?","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"34cd317a3c6f224a05ebf07aa1860063dfff2607","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"d795a813_d0f3602a","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"ae8ea622_6cee4686","updated":"2022-11-07 14:25:28.000000000","message":"I see, the difficulty is that currently there is no mechanism in agent to inform server about separate attributes of the port. So either port was fully processed and applied (and hence ACTIVE) or there were some errors and port can\u0027t be treated as ACTIVE. Right? \nI agree that introducing agent-\u003eserver structured feedback makes this change way more complicated.\n\nFor better UX I still think it makes sense to return \"hints\" in GET response, even we don\u0027t know if hints were followed or not. Otherwise the one who creates ports may end up confused: which ports were created with hints and which not.\nwdyt?","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"2ffefa97afb030d0c1c8edb3a555fb54e5f1281b","unresolved":false,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"d5709ce5_9a48f176","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"b55945c8_cf9d6176","updated":"2022-11-10 09:22:23.000000000","message":"Done","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"c22a024497530d719be8ba31c9cf3ebbcdbab8e9","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"34e37152_e02c5ff7","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"d795a813_d0f3602a","updated":"2022-11-08 14:47:11.000000000","message":"\u003e I see, the difficulty is that currently there is no mechanism in agent to inform server about separate attributes of the port. So either port was fully processed and applied (and hence ACTIVE) or there were some errors and port can\u0027t be treated as ACTIVE. Right?\n\nExactly. And just because a hint was not applied I don\u0027t want to set the port\u0027s status to ERROR, since the port is probably still fully functional. We just missed some performance tuning.\n\n\u003e I agree that introducing agent-\u003eserver structured feedback makes this change way more complicated.\n\nThat\u0027s exactly the tradeoff I also see between the above options (1) and (2).\n\n\u003e For better UX I still think it makes sense to return \"hints\" in GET response, even we don\u0027t know if hints were followed or not. Otherwise the one who creates ports may end up confused: which ports were created with hints and which not.\n\u003e wdyt?\n\nI definitely want to return the hints in a GET response. If anywhere in the spec I wrote something contradicting this, please let me know where, because it was not my intention.","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":15554,"name":"Bence Romsics","email":"bence.romsics@gmail.com","username":"ebenrom","status":"working for Ericsson, UTC+1 (+DST)"},"change_message_id":"a22724974f2594971fc03b0ec3faa7adfd4996ae","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Everything in ``hints`` is interpreted not as a demand, but as a"},{"line_number":57,"context_line":"suggestion. That is, neutron is free to ignore some or all of the"},{"line_number":58,"context_line":"requested hints without returning an error response or putting the"},{"line_number":59,"context_line":"port into an error status. Particularly neutron is free to ignore the"},{"line_number":60,"context_line":"requested hints when the port is bound by a different mechanism driver."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"``hints`` can be set at port create or update, but there\u0027s no guarantee"},{"line_number":63,"context_line":"that an update to the hints after the port was bound will have any effect."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"``hints`` is intentionally not named ``binding:hints`` and it should"},{"line_number":66,"context_line":"not be affecting the binding process and decision."}],"source_content_type":"text/x-rst","patch_set":2,"id":"991d847f_470558f4","line":63,"range":{"start_line":59,"start_character":27,"end_line":63,"end_character":73},"in_reply_to":"ec578fa1_d510555f","updated":"2022-11-04 15:14:15.000000000","message":"In this spec version I\u0027m entertaining the idea that the user does not know this. At least not from the API (but of course documentation for a cloud deployment can convey this information, because if your deployment has ovs after a certain version this will always work). I see that this is not perfect, but it makes the feature waaay simpler. And technically these hints should not change any functional behavior, so maybe we can live with this. What do you think?","commit_id":"0d9d5f84a5efacea47b5c46fa3da3ea7882876d9"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"d3dc6ec09e4c35f8714b5077f23b95e8f4949adc","unresolved":true,"context_lines":[{"line_number":99,"context_line":"API Impact"},{"line_number":100,"context_line":"----------"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Add a new admin_only field to the port resource called ``hints``. This"},{"line_number":103,"context_line":"field can be present in GET, POST and PUT requests. For its semantics"},{"line_number":104,"context_line":"please see above."},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"DB Impact"},{"line_number":107,"context_line":"---------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"a9b2b187_a349f6c0","line":104,"range":{"start_line":102,"start_character":0,"end_line":104,"end_character":17},"updated":"2022-11-15 13:47:37.000000000","message":"thanks for discussing this","commit_id":"b7e53f107573e9ab2b11ddc0e43f6253ba39f29a"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"c3e18b771af9c9619080d9b0ab701a825631ad25","unresolved":true,"context_lines":[{"line_number":117,"context_line":"-------"},{"line_number":118,"context_line":""},{"line_number":119,"context_line":"* Unit tests."},{"line_number":120,"context_line":"* Tempest tests in neutron-tempest-plugin."},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Assignee(s)"},{"line_number":123,"context_line":"-----------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"a6a9e2d0_fcf02b9b","line":120,"updated":"2022-11-15 15:54:50.000000000","message":"I\u0027m fine with general API tempest tests for this new API but also that specific hint which You are going to introduce is good candidate to be tested with fullstack test probably :)","commit_id":"b7e53f107573e9ab2b11ddc0e43f6253ba39f29a"}]}