Update patch set 4

Patch Set 4:

(1 comment)

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

1c13b866955721f7542d43c6cfb514d80632b2ae

@@ -52,6 +52,24 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "35f2c59f_ab9694cf",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 3
+      },
+      "lineNbr": 134,
+      "author": {
+        "id": 7144
+      },
+      "writtenOn": "2021-08-05T21:04:51Z",
+      "side": 1,
+      "message": "By \"refactored\" then, do you mean t-h-t service templates will be replaced by that openstack-keystone.yaml example from task-core?\n\nI didn\u0027t think that was the case, as it breaks the user interface for how we presently configure Keystone.\n\nThe example I\u0027m looking for would illustrate the link between tripleo-heat-templates/deployment/keystone/keystone-container-puppet.yaml and task-core/examples/directord/services/openstack-keystone.yaml.\n\nDoes one generate the other? Influence the other in some way? Or is the task-core one a full pluggable replacement and we would no longer use the template from t-h-t for keystone? Given that they both are a complete overlap of functionality (install, bootstrap, configure, launch keystone), how are they related, or is it one or the other?\n\nI\u0027m trying to understand what the end picture looks like and how the heat templates are still used (if at all) once this spec is implemented.",
+      "parentUuid": "e92ff57b_2bb82e82",
+      "revId": "1c13b866955721f7542d43c6cfb514d80632b2ae",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "c6690ee1_52cdcc10",