Update patch set 4

Patch Set 4:

(1 comment)

Patch-set: 4
CC: Gerrit User 6773 <6773@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Attention: {"person_ident":"Gerrit User 8655 \u003c8655@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_6773\u003e replied on the change"}

aee09a8a2d8420dce54c76692e8e17d7568bbe40

@@ -40,6 +40,24 @@
       "revId": "aee09a8a2d8420dce54c76692e8e17d7568bbe40",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "e72302e7_ef4d89eb",
+        "filename": "specs/2023.1/ovn-monitor.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 40,
+      "author": {
+        "id": 6773
+      },
+      "writtenOn": "2023-01-05T11:59:48Z",
+      "side": 1,
+      "message": "Thanks for starting this discussion.\n\nI like the idea of a single OVN agent instead of multiple ones. As long as it\u0027s engineered in a way that is easy to extend (a well defined API) in a plugin-in style where functionalities can be enabled/disabled easily.\n\nA single agent does help deployers as new functionalities no longer need another service running. It also helps with monitoring such service.\n\nAnd the main thing for me, at least with OVN in mind, is scalability because we really struggle to scale OVSDB and having multiple agents almost always translate into more connections to the OVSDB databases for each service. A single agent could benefit from a single OVSDB connection which is shared across all functionalities.",
+      "parentUuid": "5f61d723_9eaeb605",
+      "revId": "aee09a8a2d8420dce54c76692e8e17d7568bbe40",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
     {
       "unresolved": true,
       "key": {