Update patch set 4

Patch Set 4:

(1 comment)

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

975c7280c649e390625700604c793d41bf05e32c

@@ -390,6 +390,30 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": true
     },
+    {
+      "key": {
+        "uuid": "537352b5_36fe3792",
+        "filename": "specs/xena/directord-orchestration.rst",
+        "patchSetId": 4
+      },
+      "lineNbr": 421,
+      "author": {
+        "id": 7144
+      },
+      "writtenOn": "2021-08-09T20:49:24Z",
+      "side": 1,
+      "message": "can you check my comment at https://review.opendev.org/c/openstack/tripleo-specs/+/801630/3/specs/xena/directord-orchestration.rst#134\n\ni get that we are adding \"core_services\" to the role_data output in the service template interface. What is the plan on how we migrate existing services?\n\nHow do we move from keystone-container-puppet.yaml to a task-core native definition (e.g., https://github.com/mwhahaha/task-core/blob/main/examples/directord/services/openstack-keystone.yaml).\n\nWhat is the expectation on service owners? What I\u0027d like to see is an example of migrating an existing service template.",
+      "parentUuid": "46569b5a_3fbfc8be",
+      "range": {
+        "startLine": 421,
+        "startChar": 24,
+        "endLine": 421,
+        "endChar": 71
+      },
+      "revId": "975c7280c649e390625700604c793d41bf05e32c",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": true
+    },
     {
       "key": {
         "uuid": "975093cb_cbd9f7bf",