diff options
author | 2018-02-20 15:21:38 +0000 | |
---|---|---|
committer | 2018-02-20 15:21:38 +0000 | |
commit | 8dc68240c1494609b6460818757abb811b0ea8b4 (patch) | |
tree | a673bb034e0334e1e7028e30f8fca3c05b41ec6b /docs/sections/components/architecture/services.rst | |
parent | b36e25242529c5256e9f49c5f1cb1435a554e51b (diff) | |
parent | f5fda2da52b91e5e98644677599b8e3c90a87d8c (diff) |
Merge "DCAE Controller documentation DCAEGEN2-213" into amsterdam
Diffstat (limited to 'docs/sections/components/architecture/services.rst')
-rwxr-xr-x | docs/sections/components/architecture/services.rst | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/sections/components/architecture/services.rst b/docs/sections/components/architecture/services.rst new file mode 100755 index 00000000..9cfd084c --- /dev/null +++ b/docs/sections/components/architecture/services.rst @@ -0,0 +1,19 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+‘Services’ Overview
+===================
+
+DCAE Services run on the DCAE platform. A service performs either
+monitors the virtualized network services or does analytics. A service
+is composed of one or more components, and performs a business need.
+
+Services are created in a ‘Service Design and Creation’ tool called
+‘Service Assurance Flow Designer’ by a Service Designer. This is done by
+\* 1. ‘compose’ing a service from the available SDC catalog components
+(actually from the TOSCA models representing the components), then \* 2.
+’submit’ing the service, which generates a Cloudify blueprint, is then
+automatically uploaded to INVENTORY, and then deployed by DEPLOYMENT
+HANDLER (once a DTI Event is triggered for the service). It should be
+noted that some service flows, specifally ’closed-loop’ flows, are not
+initiated by DTI, but are done by CLAMP.
|