summaryrefslogtreecommitdiffstats
path: root/docs/index.rst
diff options
context:
space:
mode:
authorEzhilarasi <ezhrajam@in.ibm.com>2019-03-08 19:52:30 +0530
committerEzhilarasi <ezhrajam@in.ibm.com>2019-03-08 19:52:40 +0530
commit38c2f6c8b5cfbc5c36f2815f27226e8e3cc64a03 (patch)
tree6e5f4432167092300c4567bbee49eb4cb23f37fc /docs/index.rst
parent9effeea959df66400a10321afcd05d12a1abbf9f (diff)
CDS Doc index change
Change-Id: Ib362ce974683024d40776ec9a5a38b099741523f Issue-ID: CCSDK-917 Signed-off-by: Ezhilarasi <ezhrajam@in.ibm.com>
Diffstat (limited to 'docs/index.rst')
-rw-r--r--docs/index.rst41
1 files changed, 10 insertions, 31 deletions
diff --git a/docs/index.rst b/docs/index.rst
index bc39ca392..0ff255683 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -13,38 +13,17 @@ The system is designed to be self service, which means that users, not just prog
Self service is a completely new way of delivering services. It removes the dependence on code releases and the delays they cause and puts the control of services into the hands of the service providers. They can change a model and its parameters and create a new service without writing a single line of code.
This makes SERVICE PROVIDER(S) more responsive to its customers and able to deliver products that more closely match the needs of its customers.
-Sections
-========
-
-.. toctree::
- :maxdepth: 1
- :glob:
-
- sections/architecture/index
- sections/installation/index
- sections/configuration/index
- sections/development/index
- sections/logging
- sections/release-notes
+Design tools:
+=============
-Data Flow:
-==========
-|image0|
+Controller Blueprint Archived
+Data dictionary
-.. |image0| image:: media/image0.png
- :width: 7.88889in
- :height: 4.43750in
-
-Functional Decomposition:
-=========================
-|image1|
-.. |image1| image:: media/functional_decomposition.png
- :width: 7.88889in
- :height: 4.43750in
-
-Controller design Studio Presentation:
-======================================
+Architecture:
+=============
+The Controller Design Studio is composed of two major components:
+ * The GUI (or frontend)
+ * 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.
-Details about CDS Architecture and Design detail, Please click below.
-:download:`CDS_Architecture_Design.pptx` \ No newline at end of file