| Ralph Knag | 1fca6ac | 2017-12-05 12:05:57 -0500 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License.
|
| 2 | .. http://creativecommons.org/licenses/by/4.0
|
| 3 |
|
| 4 | ‘Services’ Overview
|
| 5 | ===================
|
| 6 |
|
| 7 | DCAE Services run on the DCAE platform. A service performs either
|
| 8 | monitors the virtualized network services or does analytics. A service
|
| 9 | is composed of one or more components, and performs a business need.
|
| 10 |
|
| 11 | Services are created in a ‘Service Design and Creation’ tool called
|
| 12 | ‘Service Assurance Flow Designer’ by a Service Designer. This is done by
|
| 13 | \* 1. ‘compose’ing a service from the available SDC catalog components
|
| 14 | (actually from the TOSCA models representing the components), then \* 2.
|
| 15 | ’submit’ing the service, which generates a Cloudify blueprint, is then
|
| 16 | automatically uploaded to INVENTORY, and then deployed by DEPLOYMENT
|
| 17 | HANDLER (once a DTI Event is triggered for the service). It should be
|
| 18 | noted that some service flows, specifally ’closed-loop’ flows, are not
|
| 19 | initiated by DTI, but are done by CLAMP.
|