Update patch set 5

Patch Set 5:

(1 comment)

Patch-set: 5

975c7280c649e390625700604c793d41bf05e32c

@@ -118,6 +118,30 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "b40d4e5a_c93c1e70",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 246,
+      "author": {
+        "id": 8833
+      },
+      "writtenOn": "2021-08-10T03:41:18Z",
+      "side": 1,
+      "message": "I don\u0027t know what we mean by stateless model. Heat definitely had deployment/stack state stored in the heat database, but obviously it was not designed as a task engine to keep state/health of remote workers/nodes.\n\nI would like to know more about \u0027robust and reliable\u0027 part of the new toolset which includes recovery from server/client failure, network issues and queue overflow etc and how those are addressed. \n\nThough I don\u0027t see we using zeromq (rather something like QDR maybe) and don\u0027t know a lot about zeromq, here is an example doc snippet from zeromq documentation about heartbeats.\n\n\"When we use a ROUTER socket in an application that tracks peers, as peers disconnect and reconnect, the application will leak memory (resources that the application holds for each peer) and get slower and slower.\"\n\nI\u0027m asking these questions because we\u0027re purpose writing some custom tools for our needs and they should just address specific needs and pain points without any overlap.",
+      "parentUuid": "dc88d59c_f2f18ed1",
+      "range": {
+        "startLine": 246,
+        "startChar": 0,
+        "endLine": 246,
+        "endChar": 21
+      },
+      "revId": "975c7280c649e390625700604c793d41bf05e32c",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "0ca9bf5c_f0b09213",