Update patch set 7

Patch Set 7:

(2 comments)

Patch-set: 7
Attention: {"person_ident":"Gerrit User 16688 \u003c16688@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_15554\u003e replied on the change"}

7fdc74b912aa683acb27532c45a09c93dcf38a4a

@@ -16,6 +16,46 @@
       "message": "I\u0027ll push a new PS tomorrow. I\u0027ll remove the section describing the script to heal the inventories. We\u0027ll reduce the scope to a simple script that will inform about the ports with min-bw rules in overlay networks.",
       "revId": "7fdc74b912aa683acb27532c45a09c93dcf38a4a",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "ee04b034_d60b4400",
+        "filename": "specs/2023.1/strict-minimum-bandwidth-tunnelled-networks.rst",
+        "patchSetId": 7
+      },
+      "lineNbr": 52,
+      "author": {
+        "id": 15554
+      },
+      "writtenOn": "2022-11-10T14:54:56Z",
+      "side": 1,
+      "message": "1) So far we had kind of \"hierarchical\" rp names like \"devstack0:Open vSwitch agent:br-test\". Is the tunnelled_network_rp_name supposed to be the full name or only the last component? The sample rp listing below suggests the latter.\n\n2) \"accessible from the Neutron server and the OVS agent\" - Does this mean that we need to set this for each agent using this and then the agents report this to the server?",
+      "revId": "7fdc74b912aa683acb27532c45a09c93dcf38a4a",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "6fb709a1_a85e273b",
+        "filename": "specs/2023.1/strict-minimum-bandwidth-tunnelled-networks.rst",
+        "patchSetId": 7
+      },
+      "lineNbr": 147,
+      "author": {
+        "id": 15554
+      },
+      "writtenOn": "2022-11-10T14:54:56Z",
+      "side": 1,
+      "message": "Without debating the scope you set, I\u0027m not sure I agree with this. It seems possible to me to create a single inventory and then make multiple allocations (for different use cases like one for a physnet and another for a tunnelled net) against it, consuming the same inventory.",
+      "range": {
+        "startLine": 146,
+        "startChar": 31,
+        "endLine": 147,
+        "endChar": 44
+      },
+      "revId": "7fdc74b912aa683acb27532c45a09c93dcf38a4a",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     }
   ]
 }