DCAE Controller documentation DCAEGEN2-213

[dcaegen2.git] / docs / sections / components / architecture / services.rst

diff --git a/docs/sections/components/architecture/services.rst b/docs/sections/components/architecture/services.rst
new file mode 100755 (executable)
index 0000000..9cfd084
--- /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.\r
+.. http://creativecommons.org/licenses/by/4.0\r
+\r
+‘Services’ Overview\r
+===================\r
+\r
+DCAE Services run on the DCAE platform. A service performs either\r
+monitors the virtualized network services or does analytics. A service\r
+is composed of one or more components, and performs a business need.\r
+\r
+Services are created in a ‘Service Design and Creation’ tool called\r
+‘Service Assurance Flow Designer’ by a Service Designer. This is done by\r
+\* 1. ‘compose’ing a service from the available SDC catalog components\r
+(actually from the TOSCA models representing the components), then \* 2.\r
+’submit’ing the service, which generates a Cloudify blueprint, is then\r
+automatically uploaded to INVENTORY, and then deployed by DEPLOYMENT\r
+HANDLER (once a DTI Event is triggered for the service). It should be\r
+noted that some service flows, specifally ’closed-loop’ flows, are not\r
+initiated by DTI, but are done by CLAMP.\r