Update patch set 3

Patch Set 3:

(4 comments)

Patch-set: 3
CC: Gerrit User 11583 <11583@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Attention: {"person_ident":"Gerrit User 7730 \u003c7730@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_11583\u003e replied on the change"}

1e499fc753c19420a47a24f0dd56d352bfe5b381

@@ -0,0 +1,55 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "5189850e_d7835e9e",
+        "filename": "doc/source/stories/2023-10-06.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 76,
+      "author": {
+        "id": 11583
+      },
+      "writtenOn": "2023-10-06T13:48:19Z",
+      "side": 1,
+      "message": "on a 2k computes regions, we have 344 rpc workers, it works like a charm.\n\nThe problem with having a lot of workers is the number of database connection is consume.\nIf you consume all your db connections, you have other issues...\n\nso it has to be computed with the number of connection you are able to provide to neutron.",
+      "revId": "1e499fc753c19420a47a24f0dd56d352bfe5b381",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "03be9ee2_c5987c4d",
+        "filename": "doc/source/stories/2023-10-06.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 84,
+      "author": {
+        "id": 11583
+      },
+      "writtenOn": "2023-10-06T13:48:19Z",
+      "side": 1,
+      "message": "I dont get that one, it\u0027s suppose to affect neutron agent connection with ovs.\nHow is it related to the server?",
+      "revId": "1e499fc753c19420a47a24f0dd56d352bfe5b381",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": false,
+      "key": {
+        "uuid": "933ec327_ed885265",
+        "filename": "doc/source/stories/2023-10-06.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 97,
+      "author": {
+        "id": 11583
+      },
+      "writtenOn": "2023-10-06T13:48:19Z",
+      "side": 1,
+      "message": "nice one",
+      "revId": "1e499fc753c19420a47a24f0dd56d352bfe5b381",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}

b589f7fa2ae49af07ef572df842c77367485577e

@@ -0,0 +1,21 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "68548f91_1b477b4a",
+        "filename": "doc/source/stories/2023-10-06.rst",
+        "patchSetId": 2
+      },
+      "lineNbr": 58,
+      "author": {
+        "id": 11583
+      },
+      "writtenOn": "2023-10-06T13:48:19Z",
+      "side": 1,
+      "message": "s/head/heal/\n\nWe do have 300sec in our deployment there, so yes, increasing the number is good for load on nova side.\n\nMaybe you could add a note about the fact that this periodic task is healing ONE instance every x secs, so having 600sec, it means only one instance will be healing every 10 minutes.\n\nAlso, IIRC, when you restart nova compute, the healing starts over, so in an environment where nova restart often, having a high value here can be problematic",
+      "revId": "b589f7fa2ae49af07ef572df842c77367485577e",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}