1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
\r
2 .. http://creativecommons.org/licenses/by/4.0
\r
4 =============================
\r
5 Configuration and Performance
\r
6 =============================
\r
10 By default, DFC handles the "PM_MEAS_FILES" change identifier and publishes these files on the "bulk_pm_feed" feed.
\r
11 But it can also be configured to handle other change identifiers and publish them to other feeds, see picture below.
\r
13 .. image:: ../../images/DFC_config.png
\r
15 The configuration of DFC is controlled via a blueprint.
\r
17 Blueprint Configuration Explained
\r
18 """""""""""""""""""""""""""""""""
\r
20 For the communication with the Message Router, the user must provide the **host name**, **port**, and **protocol** of the DMaaP Message router.
\r
22 .. code-block:: yaml
\r
23 :emphasize-lines: 2,6,10
\r
28 description: dmaap messagerouter host
\r
29 default: message-router.onap.svc.cluster.local
\r
32 description: dmaap messagerouter port
\r
36 description: dmaap messagerouter protocol
\r
39 The user can also specify which version of DFC to use.
\r
41 .. code-block:: yaml
\r
47 description: DFC image tag/version
\r
48 default: "nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.datafile.datafile-app-server:1.2.0"
\r
50 The user can also enable secure communication with the DMaaP Message Router.
\r
52 .. code-block:: yaml
\r
58 description: enable certificate based connection with DMaap
\r
61 DFC can handle multiple change identifiers. This will require to create manually a new block for each change identifier.
\r
63 .. code-block:: yaml
\r
67 dfcFeed00ChangeIdentifier:
\r
68 dmaap_info: <<bulk_pm_feed>>
\r
71 For each feed related to a change identifier the user must provide the **feed name**, and **feed description**.
\r
73 .. code-block:: yaml
\r
74 :emphasize-lines: 2,6
\r
79 description: The name of the feed the files will be published to. Should be used by the subscriber.
\r
80 default: "bulk_pm_feed"
\r
81 dfcFeed00Description:
\r
83 description: A description of the feed the files will be published to.
\r
84 default: "Feed for Bulk PM files"
\r
86 **Note!** The feed name provided should be used by the subscriber/s to set up the subscription to the feed.
\r
88 To dynamically create the feeds, DFC uses the DCAE DMaaP plugin. This means that for each feed the user must also add an
\r
89 item under the "**node_templates**" section of the blueprint. The feed is identified within the blueprint with a feed identifier, "**dfcFeed00**" in the example.
\r
91 .. code-block:: yaml
\r
96 type: ccsdk.nodes.Feed
\r
98 feed_name: { get_input: dfcFeed00Name }
\r
99 feed_description: { get_input: dfcFeed00Description }
\r
101 To configure DFC micro service itself, the user must also add the change identifier and the feed identifier to the "**application_config**" section
\r
102 under the tag "**dmaap.dmaapProducerConfiguration**" in the blueprint. **Note!** The identifier should be surrounded by **<<>>** for the feed's configuration to be bound to the DFC configuration in CBS.
\r
104 .. code-block:: yaml
\r
105 :emphasize-lines: 4
\r
107 application_config:
\r
108 dmaap.dmaapProducerConfiguration:
\r
109 - changeIdentifier: {get_input: dfcFeed00ChangeIdentifier}
\r
110 feedInfo: <<dfcFeed00>>
\r
112 And, lastly, to set up the publication to the feed, the feed identifier must be added to the "**streams_publishes**" section
\r
115 .. code-block:: yaml
\r
116 :emphasize-lines: 2
\r
123 Sample blueprint configuration
\r
124 """"""""""""""""""""""""""""""
\r
126 The format of the blueprint configuration that drives all behavior of DFC is probably best described using an example.
\r
127 The blueprint below configures DFC to handle the two feeds shown in the picture above.
\r
129 .. code-block:: yaml
\r
134 description: dmaap messagerouter host
\r
135 default: message-router.onap.svc.cluster.local
\r
138 description: dmaap messagerouter port
\r
142 description: dmaap messagerouter protocol
\r
146 description: DFC image tag/version
\r
147 default: "nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.datafile.datafile-app-server:1.2.0"
\r
150 description: number of instances
\r
154 description: enable certificate based connection with DMaap
\r
158 description: The name of the feed the files will be published to. Should be used by the subscriber.
\r
159 default: "bulk_pm_feed"
\r
160 dfcFeed00Description:
\r
162 description: A description of the feed the files will be published to.
\r
163 default: "Feed for Bulk PM files"
\r
166 description: The name of the feed the files will be published to. Should be used by the subscriber.
\r
167 default: "log_feed"
\r
168 dfcFeed01Description:
\r
170 description: A description of the feed the files will be published to.
\r
171 default: "Feed for log files"
\r
175 type: ccsdk.nodes.Feed
\r
177 feed_name: { get_input: dfcFeed00Name }
\r
178 feed_description: { get_input: dfcFeed00Description }
\r
180 type: ccsdk.nodes.Feed
\r
182 feed_name: { get_input: dfcFeed01Name }
\r
183 feed_description: { get_input: dfcFeed01Description }
\r
185 datafile-collector:
\r
186 type: dcae.nodes.ContainerizedServiceComponentUsingDmaap
\r
189 - type: ccsdk.relationships.publish_files
\r
191 - type: ccsdk.relationships.publish_files
\r
195 cloudify.interfaces.lifecycle:
\r
199 - concat: ["8100:0"]
\r
200 - concat: ["8433:0"]
\r
203 service_component_type: 'dcae-datafile'
\r
204 application_config:
\r
205 dmaap.security.enableDmaapCertAuth: { get_input: secureEnableCert }
\r
207 dfcFeed00ChangeIdentifier:
\r
208 dmaap_info: <<dfcFeed00>>
\r
210 dfcFeed01ChangeIdentifier:
\r
211 dmaap_info: <<dfcFeed01>>
\r
213 streams_subscribes:
\r
219 { concat: [{ get_input: dmaap_mr_protocol },"://",{ get_input: dmaap_mr_host },
\r
220 ":",{ get_input: dmaap_mr_port },"/events/unauthenticated.VES_NOTIFICATION_OUTPUT/OpenDcae-c12/C12"]}
\r
232 To see the performance of DFC, see "`Datafile Collector (DFC) performance baseline results`_".
\r
234 .. _Datafile Collector (DFC) performance baseline results: https://wiki.onap.org/display/DW/Datafile+Collector+%28DFC%29+performance+baseline+results