diff options
| author |   Dan Timoney <dtimoney@att.com> | 2019-04-16 14:24:14 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-04-16 14:24:14 +0000 |
| commit | a10f0b6adca32776aa8fc0eece2c4bf916d18cb4 (patch) | |
| tree | 59d8f597223943e955e7d76094d6574436570f4d | |
| parent | 9c924e65a44f836775ebada68b7d568dde31b861 (diff) | |
| parent | 763d29eded8b16d74611fa308034119cb5eb5810 (diff) | |
Merge "Doc CDS Architecture in Index"
| -rw-r--r-- | docs/index.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/index.rst b/docs/index.rst index 477c251da..5f3902687 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -56,6 +56,13 @@ The Controller Design Studio is composed of two major components: * The Run Time (or backend) The GUI handles direct user input and allows for displaying both design time and run time activities. For design time, it allows for the creation of controller blueprint, from selecting the DGs to be included, to incorporating the artifact templates, to adding necessary components. For run time, it allows the user to direct the system to resolve the unresolved elements of the controller blueprint and download the resulting configuration into a VNF. At a more basic level, it allows for creation of data dictionaries, capabilities catalogs, and controller blueprint, the basic elements that are used to generate a configuration. The essential function of the Controller Design Studio is to create and populate a controller blueprint, create a configuration file from this Controller blueprint, and download this configuration file (configlet) to a VNF/PNF. +|image0| + +.. |image0| image:: media/CDS_architecture.jpg + :height: 4.43750in + :width: 7.88889in + + Resource assignment: ===================== .. toctree:: |