From d2cd31b73c0282f7aafd5b4adada00c0f4533d61 Mon Sep 17 00:00:00 2001 From: Ralph Knag Date: Mon, 2 Apr 2018 16:27:46 -0400 Subject: Onboarding documentation update for CLI Change-Id: I1d4d0111063ea62c3759aa9b7232998b70229644 Issue-ID: DCAEGEN2-350 Signed-off-by: Ralph Knag --- docs/sections/components/architecture/services.rst | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100755 docs/sections/components/architecture/services.rst (limited to 'docs/sections/components/architecture/services.rst') diff --git a/docs/sections/components/architecture/services.rst b/docs/sections/components/architecture/services.rst deleted file mode 100755 index 9cfd084c..00000000 --- a/docs/sections/components/architecture/services.rst +++ /dev/null @@ -1,19 +0,0 @@ -.. 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. -- cgit 1.2.3-korg