blob: 51fb031b626d17281089a7fca23b848eb400cf55 [file] [log] [blame]
Ralph Knag1fca6ac2017-12-05 12:05:57 -05001
2.. http://creativecommons.org/licenses/by/4.0
3
4.. _glossary:
5
Ralph Knagd2cd31b2018-04-02 16:27:46 -04006
Ralph Knag1fca6ac2017-12-05 12:05:57 -05007Glossary
8========
9
Ralph Knagd2cd31b2018-04-02 16:27:46 -040010A&AI - Active and Available Inventory
11-------------------------------------
Ralph Knag1fca6ac2017-12-05 12:05:57 -050012
Ralph Knagd2cd31b2018-04-02 16:27:46 -040013Inventory DB for all network components
14
15CLAMP
16-----
17
18Non DCAE Platform Component - Controls the input and processing for
19Closed Loop services.
20
21Closed Loop
22-----------
23
24Services designed to monitor and report back to a controlling function
25that automatically deals with the event reported without human
26interaction.
27
28CDAP
Ralph Knag1fca6ac2017-12-05 12:05:57 -050029----
30
Ralph Knagd2cd31b2018-04-02 16:27:46 -040031Opensource Platform for development of Big Data platforms using Hadoop.
32Some DCAE service components are written utilizing CDAP.
Ralph Knag1fca6ac2017-12-05 12:05:57 -050033
Ralph Knagd2cd31b2018-04-02 16:27:46 -040034Cloudify
35--------
36
37Open Source application and network orchestration framework, based on
38TOSCA used in DCAE to deploy platform and service components from
39Cloudify Blueprints. Refer to :doc:`Architecture <./architecture/pieces>`
40for more information.
41
42Cloudify Blueprints
43-------------------
44
45YAML formatted file used by Cloudify to deploy platform and service
46components. Contains all the information needed for installation.
47
48Consul
49------
50
51Opensource Platform Component that supports Service Discovery,
52Configuration, and Healthcheck. Refer to
53:doc:`Architecture <./architecture/pieces>` for more information.
Ralph Knag1fca6ac2017-12-05 12:05:57 -050054
55Component
56---------
57
Ralph Knagd2cd31b2018-04-02 16:27:46 -040058Refers to a DCAE service component which is a single micro-service that
59is written to be run by the DCAE platform and to be composeable to form
60a DCAE service. That composition occurs in the SDC.
Ralph Knag1fca6ac2017-12-05 12:05:57 -050061
Ralph Knagd2cd31b2018-04-02 16:27:46 -040062Config Binding Service
63----------------------
Ralph Knag1fca6ac2017-12-05 12:05:57 -050064
Ralph Knagd2cd31b2018-04-02 16:27:46 -040065DCAE Platform Component - Service Components use Config Binding Service
66to access Consul and retrieve configuration variables.
67
68Component Specification
69-----------------------
70
71JSON formatted file that fully describes a component and its interfaces
72
73Data Format / Data Format Specification
74---------------------------------------
75
76JSON formatted file that fully describes a components input or output
77
78dcae_cli Tool
79-------------
80
81Tool used for development and testing. It validates the component and
82data format specifications against their respective schemas and provides
83the capability to view platform generated configuration for the
84component.
85
86Deployment Handler
87------------------
88
89DCAE Platform Component - talks to
90Cloudify to deploy components.
91
92Design-Time
Ralph Knag1fca6ac2017-12-05 12:05:57 -050093-----------
94
Ralph Knagd2cd31b2018-04-02 16:27:46 -040095Refers to when the System Designer uses the SDC Tool to compose services
96from components in the SDC catalog. The Designer can provide input to
97assign/override defaults for configuration for any parameter with the
98property designer_editable set to true’.
Ralph Knag1fca6ac2017-12-05 12:05:57 -050099
Ralph Knagd2cd31b2018-04-02 16:27:46 -0400100Deploy-Time
101-----------
102
103Refers to when a service is being deployed. This can be done
104automatically via the SDC Tool, or manually via the DCAE Dashboard or
105CLAMP UI. When manually deployed, DevOps can provide input to
106assign/override defaults for configuration for any parameter with the
107property sourced_at_deployment set to true’.
108
109Docker
110------
111
112Opensource Platform for development of containerized applications in the
113cloud. Many DCAE service components and all DCAE collectors are written
114utilizing Docker.
115
116Dmaap
117-----
118
119A data transportation service platform that supports message-based
120topics and file-based feeds. Runs locally at the Edge and Centrally.
121
122Inventory
123---------
124
125DCAE Platform Component - Postgres DB containing Cloudify Blueprints for
126platform and service components.
Ralph Knag1fca6ac2017-12-05 12:05:57 -0500127
128Onboarding catalog
129------------------
130
Ralph Knagd2cd31b2018-04-02 16:27:46 -0400131Catalog used exclusively by the dcae_cli tool during development and
132testing. Contains validated components and data_formats to be used among
133developers during development and testing.
134
135Policy (not yet implemented)
136----------------------------
137
138Refers to the setting of configuration parameters for a component, by
139Operations via the Policy UI.
140
141Policy Handler (not yet implemented)
142------------------------------------
143
144DCAE Platform Component that received Policy updates from Policy UI
145
146Policy UI (not yet implemented)
147-------------------------------
148
Stanislav Chlebece7933a02018-11-15 10:08:31 +0100149Non DCAE Component - Policy User Interface where Operations assigns
150values to configuration specified for this.
Ralph Knagd2cd31b2018-04-02 16:27:46 -0400151
152Run-Time
153--------
154
Stanislav Chlebece7933a02018-11-15 10:08:31 +0100155Refers to the when a service is running on the platform.
Ralph Knagd2cd31b2018-04-02 16:27:46 -0400156
157SCH - Service Change Handler
158----------------------------
159
160DCAE Platform Component - Receives updates from SDC and updates
161Inventory
162
163SDC - Service Design and Creation - (formerly ASDC)
164---------------------------------------------------
165
166Tool used by Service Designers to compose services from SDC catalog
167artifacts. Once services are created, Cloudify Blueprints can be
168generated to deployment and installation.
169
170SDC Catalog
171-----------
172
173Catalog of composable Components and Data Formats to be used in the SDC
174Tool to create services. Currently, there is no access to the SDC
175Catalog from the dcae_cli tool. Artifacts are manually placed there
176after testing. Every catalog artifact has a ``UUID``, a globally unique
177identifier that identifies that artifact.
178
179Self-Service
180------------
181
182Refers to services that are supported by SDC, and that are automatically
183installed as a result of a Service Designers composition and submission
184of a service. Only a handful of services are self-service currently.
185Most require manual effort to generate the Tosca Model files and
186Cloudify Blueprints.
187
188Service Component
189-----------------
190
191Microservice that provides network monitoring or analytic function on
192the DCAE platform.
193
194Service
195-------
196
197Generally composed of multiple service components, which is deployed to
198the DCAE platform.
199
200Tosca Model
201-----------
202
203Model generated from validately component specification, (stored in SDC
204catalog for Self-Service components), and used as input to generate
205Cloudify Blueprints
206
207VNF - Virtualized Network Function
208----------------------------------
209
210A network function that runs on one or more virtualized machines.