| liamfallon | 8fdf84c | 2019-03-15 12:36:38 +0000 | [diff] [blame] | 1 | The "input" prefix indicates that this is what the payload looks like on the POST. While the "output" prefix |
| 2 | indicates that this is what the payload looks like when the response goes back to the caller. |
| 3 | |
| 4 | For each of the use cases, there is at least one configuration policy for DCAE Microservice. |
| 5 | |
| 6 | *.monitoring.input.[json|yaml] <-- POST request |
| 7 | |
| 8 | *.monitoring.output.[json|yaml] --> POST response |
| 9 | |
| 10 | The Operational Policies: |
| 11 | |
| 12 | *.operational.input.yaml --> Can Pam change this to JSON?? |
| 13 | |
| 14 | *.operational.output.json --> POST response |
| 15 | |
| 16 | The Guard Policies: |
| 17 | |
| 18 | *.guard.[frequency|minmax].json <-- POST request |
| 19 | |
| 20 | *.guard.[frequency|minmax].json --> POST response |
| 21 | |
| 22 | For DBAO, the following are internal TOSCA Representations for the Operational and Guard policies, with the |
| 23 | contents of the yaml or JSON URL Encoded: |
| 24 | |
| 25 | *.output.tosca.yaml |