diff options
| author |   Ralph Knag <rhknag@research.att.com> | 2018-04-02 16:27:46 -0400 |
|---|---|---|
| committer | Ralph Knag <rhknag@research.att.com> | 2018-04-02 16:54:16 -0400 |
| commit | d2cd31b73c0282f7aafd5b4adada00c0f4533d61 (patch) | |
| tree | 0ca259920246992703fe4c6c996c0e0639cdeef2 /platformdoc/docs/architecture/services.md | |
| parent | ef55ef2163dee32905bd10b0a0b3ea0f6a763322 (diff) | |
Onboarding documentation update for CLI
Change-Id: I1d4d0111063ea62c3759aa9b7232998b70229644
Issue-ID: DCAEGEN2-350
Signed-off-by: Ralph Knag <rhknag@research.att.com>
Diffstat (limited to 'platformdoc/docs/architecture/services.md')
| -rw-r--r-- | platformdoc/docs/architecture/services.md | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/platformdoc/docs/architecture/services.md b/platformdoc/docs/architecture/services.md index 985953c3..f17f563b 100644 --- a/platformdoc/docs/architecture/services.md +++ b/platformdoc/docs/architecture/services.md @@ -1,7 +1,11 @@ # '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. +DCAE Services run on the DCAE platform. A service 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. + +* 'compose'ing a service from the available SDC catalog components (actually from the TOSCA models representing the components), then +* 'submit'ing the service, which generates a Cloudify blueprint, which is then automatically uploaded to INVENTORY, and then deployed by DEPLOYMENT HANDLER (and CLOUDIFY) (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. + +Only a few services are supported in SDC so far, and therefore steps above are done manually by the Onboarding Team for most services. + |