aboutsummaryrefslogtreecommitdiffstats
path: root/docs/modelingconcepts/cba.rst
blob: a400ef61495be8c4dc098a2d9152458fb7e3db3e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
.. This work is a derivative of https://wiki.onap.org/display/DW/Modeling+Concepts#Concepts-66498 by IBM 
.. used under Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright (C) 2020 Deutsche Telekom AG.

.. _cba:

Controller Blueprint Archive (.cba)
-------------------------------------

The **C**\ ontroller **B**\ lueprint **A**\ rchive is the overall service design, fully model-driven, intent based
**package** needed for provisioning and configuration management automation.

The CBA is **.zip** file, comprised of the following folder structure, the files may vary:

.. code-block::

   ├── Definitions
   │   ├── blueprint.json                   Overall TOSCA service template (worfklow + node_template)
   │   ├── artifact_types.json              (generated by enrichment)
   │   ├── data_types.json                  (generated by enrichment)
   │   ├── node_types.json                  (generated by enrichment)
   │   ├── relationship_types.json          (generated by enrichment)
   │   └── resources_definition_types.json  (generated by enrichment)
   ├── Environments                         Contains *.properties files as required by the service
   ├── Plans                                Contains Directed Graph
   ├── Tests                                Contains uat.yaml file for testing the cba actions within a cba **package
   ├── Scripts                              Contains scripts
   │   ├── python                           Python scripts
   │   └── kotlin                           Kotlin scripts
   ├── TOSCA-Metadata
   │   └── TOSCA.meta                       Meta-data of overall package
   └── Templates                            Contains combination of mapping and template

To process a CBA for any service we need to enrich it first. This will gather all the node- type, data-type, 
artifact-type, data-dictionary definitions provided in the blueprint.json.