Update patch set 4

Patch Set 4:

(2 comments)

Patch-set: 4

1c13b866955721f7542d43c6cfb514d80632b2ae

@@ -17,6 +17,24 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "104c2b1c_78f6428d",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 36,
+      "author": {
+        "id": 7353
+      },
+      "writtenOn": "2021-08-06T15:15:14Z",
+      "side": 1,
+      "message": "I would like to refrain from putting pseudo code in this spec as I feel it is more distracting than helpful. That said, we have put together examples of how this would all tie together within THT, one of which can be seen here: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/798747\n\nThere may be a lot of overlap between Heat and Task-Core, which I think is helpful to highlight. With Task-Core, we\u0027re able to implement most, if not all, of what we need in a tiny utility with minimal dependencies that should™ be far easier to maintain long term. That being said, there\u0027s no design on replacing heat wholesale, heat templates are our user interface. However, we can marginalize Heat substantially, and potentially excise it in a future iteration should we ever find the need or desire.",
+      "parentUuid": "d800eea8_1205c703",
+      "revId": "1c13b866955721f7542d43c6cfb514d80632b2ae",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "aa1a6184_c8031e70",
@@ -70,6 +88,24 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "fd55b842_430b133a",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 134,
+      "author": {
+        "id": 7353
+      },
+      "writtenOn": "2021-08-06T15:15:14Z",
+      "side": 1,
+      "message": "Refactoring will be within the in heat-template Ansible tasks. The heat templates themselves will remain mostly intact, keeping the user interface the same. The heat template would be responsible for the generation of input into task-core which would then invoke either Ansible or Directord to execute a deployment.",
+      "parentUuid": "35f2c59f_ab9694cf",
+      "revId": "1c13b866955721f7542d43c6cfb514d80632b2ae",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "c6690ee1_52cdcc10",