Update patch set 1

Patch Set 1:

(1 comment)

Patch-set: 1

7888aecf10cf6a2d0f76d0f8532e6b49114ad4ff

@@ -142,6 +142,30 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": false
     },
+    {
+      "key": {
+        "uuid": "5f7c97a3_62507f2d",
+        "filename": "specs/rocky/vitrage-resources.rst",
+        "patchSetId": 1
+      },
+      "lineNbr": 84,
+      "author": {
+        "id": 19159
+      },
+      "writtenOn": "2018-07-04T10:12:52Z",
+      "side": 1,
+      "message": "Actually, there are two alternatives for writing the Vitrage template:\n\n1. If an instance X is down -\u003e execute a Mistral healing workflow for instance X and stack Y\n\n2. If an instance that belongs to stack Y is down -\u003e execute a Mistral healing workflow for that instance and stack Y\n\nX should be Y are specific ids. In the second alternative, the check is for *any* instance that belongs to the stack.\n\nWhich option is better in your opinion?\nThe input for Vitrage template should be: alarm name, optional instance id, Heat stack id, and Mistral workflow details\n\n(BTW, in the future we will also have options 3,4,... for templates of network failures)",
+      "parentUuid": "5f7c97a3_0763ddb2",
+      "range": {
+        "startLine": 84,
+        "startChar": 10,
+        "endLine": 84,
+        "endChar": 46
+      },
+      "revId": "7888aecf10cf6a2d0f76d0f8532e6b49114ad4ff",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": false
+    },
     {
       "key": {
         "uuid": "5f7c97a3_0e84685c",