| Table of Contents |
|---|
...
Notification mechanism (Code enhancement required)
Support for notification mechanism integration is required within MS container/package. The component spec owner will declare in the spec the script that platform should invoke when a configuration change is received (eg. from Policy) This script should be contained within the MS container/package and When there are configuration changes (triggered via policy/clamp), the platform will fetch the configuration and store them in consul. The platform will also notify the services indicating there is new configuration (slide below indicates the flow involved)
To support this interface, the service component should include a script within the container and specify that in component spec
Component spec - "auxilary": { "policy": { "trigger_type": "docker", "script_path": "/opt/app/reconfigure.sh" } }
The corresponding blueprint should include following (To be added)
This script must have necessary logic to invoke CBS API and cascade the information for application processing. For components not expecting dynamic changes, this step is optional.
...
Once the components meet all above criteria, the component will be included in the DCAE bootstrap process to enable deployment during ONAP/DCAE instantiation (this step is optional if component will be deployed through CLAMP).
Useful Links
JJB - https://wiki.onap.org/display/DW/Using+Standard+Jenkins+Job+%28JJB%29+Templates
CSIT - Creating a CSIT Test
...