Update patch set 5

Patch Set 5:

(1 comment)

Patch-set: 5
Reviewer: Gerrit User 14985 <14985@4a232e18-c5a9-48ee-94c0-e04e7cca6543>

975c7280c649e390625700604c793d41bf05e32c

@@ -630,6 +630,30 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "f389486d_443831d1",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 421,
+      "author": {
+        "id": 14985
+      },
+      "writtenOn": "2021-08-11T13:42:47Z",
+      "side": 1,
+      "message": "\u003e I don\u0027t see a lot of activity in taskflow, and even if there were, activity isn\u0027t a predictable indicator of future maintenance (see Heat, Mistral, Ansible).\n\u003e \n\u003e I\u0027m more leaning towards one or the other (Heat or taskflow or something else). That is why I proposed the alternative in my comment about clean room, with support for opt-in backwards compatibility.\n\nNo thanks. I don\u0027t think anyone wants to sign on to write a task graph utility from scratch. We already have 3 as you\u0027ve mentioned. Heat, Ansible, Taskflow.  All three overlap here but only *1* is specifically for this functionality. Taskflow.  Yes it\u0027s low in activity but it\u0027s core to things like VM creation in nova or volume creation in Cinder.  I keep pointing out that the goal is to simplify by using tools *specifically* designed for a function to reduce the issues we have.  In terms of execution testing, we\u0027ve already tested task-core at a scale larger than tripleo and have tools to show that it can handle the number of tasks with various relationships.\n\nhttps://github.com/mwhahaha/task-core/blob/main/examples/scale/gen_scale_data.py\n\nYour ask here is a bit difficult for me because we didn\u0027t ask for any of this before jumping on the ansible bandwagon and have been dealing with the fallout for years now. In this case we\u0027ve provided scale examples for both task-core and directord at larger scale than we ever tested with ansible or heat.  Why is this such a sticking point *now*?",
+      "parentUuid": "d1f22753_0be150f5",
+      "range": {
+        "startLine": 421,
+        "startChar": 24,
+        "endLine": 421,
+        "endChar": 71
+      },
+      "revId": "975c7280c649e390625700604c793d41bf05e32c",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "975093cb_cbd9f7bf",