summaryrefslogtreecommitdiffstats
path: root/platformdoc/docs/architecture
diff options
context:
space:
mode:
authorMichael Hwang <mhwang@research.att.com>2017-11-06 14:52:37 -0500
committerMichael Hwang <mhwang@research.att.com>2017-11-06 14:53:29 -0500
commit3d2b2aed3172d48325ed91ee6c1546c5172bac5e (patch)
treeec0ae314c46c33998b11ae7a1e4e48d0720425ee /platformdoc/docs/architecture
parenta73548f4eb6ba4bdb2b2064c7e24a4b74b467f5a (diff)
Merge in accumulated changes
Change-Id: I3cd9da556c31efe879f0ff1eaf48f63e4fc353aa Issue-Id: DCAEGEN2-189 Signed-off-by: Michael Hwang <mhwang@research.att.com>
Diffstat (limited to 'platformdoc/docs/architecture')
-rw-r--r--platformdoc/docs/architecture/services.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/platformdoc/docs/architecture/services.md b/platformdoc/docs/architecture/services.md
new file mode 100644
index 00000000..985953c3
--- /dev/null
+++ b/platformdoc/docs/architecture/services.md
@@ -0,0 +1,7 @@
+# '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.