...
Refer Sample Chart Yaml mapping from component spec and Sample Values yaml mapping from component spec in the requirements document.
Outstanding - 06/01/2021
- stream_publish/stream_subscribe handle as string; change VES spec and test
- readiness mapping Include PORT/initialdelaySeconds into auxillary.healthcheck on component spec schema as optional parameter for mapping into readiness check
...
Add validation if enabled in spec and certificate.yaml not provided - tool must error - switch to use use_external_tls/flagflag - DONE 1.3.2
8. Support MAPPING requirement – Postgres (refer REQ #5 for details) - Target 06/30 30 DONE 1.3.2
9. Support MAPPING requirement – Policy Sidecar (refer REQ #4 for details) Target 06/17 17 DONE 1.3.2
Format written out into values.yaml not as expected
...
11. Support MAPPING requirement – ConfigMap support (refer REQ #2 for details) Target 06/30 DONE 1.3.2
12. Support MAPPING requirement – DMAAP Secure Topic/Feed (refer REQ #6 for details)
...
21. Secret mapping requirement TBD and pv mapping - Vijay Kumar - Target 06/30 30 DONE 1.3.2
- CMPv2 + application_env22. Support chart generation as directory (instead of tgz) via
Option 1: Change spec schema to include secret name as additional input and use that for helm values.yaml setting
Option 2: Have tool set the secret name as <component-name>-cmpv2-keystore-password - Current chosen option - Target
22. Support chart generation as directory (instead of tgz) via configuration (added on )
23. Support dependency download (helm dep up) from repo/access based on deployment configration (added on )
24. Add schema validator module; keep the schema definiton overriddable (either through CI or api parameter); this should be configurable - default enabled (added on based on svc mapping test) - Target
25. Testing with ONAP spec files on ONAP lab with componen-spec (ves, pm-mapper, dfc, tcagen2, hv-ves, prh) - Sivakumar Santharam ONGOING
- Modify spec to align with new schema
- https://git.onap.org/dcaegen2/collectors/hv-ves/tree/dpo/spec/hv-ves-collector.componentspec.json
- https://git.onap.org/dcaegen2/collectors/ves/tree/dpo/spec/vescollector-componentspec.json
- https://git.onap.org/dcaegen2/analytics/tca-gen2/tree/dcae-analytics/dpo/tcagen2_spec.json
- https://git.onap.org/dcaegen2/services/pm-mapper/tree/dpo/spec/pmmapper-component-spec.json
- https://git.onap.org/dcaegen2/collectors/datafile/tree/datafile-app-server/dpo/spec/datafile-component-spec.json
- https://git.onap.org/dcaegen2/services/prh/tree/dpo/spec/prh.componentspec.json
- Generate charts and deploy and check if component comes up clean
- Environment for test to be setup/checked (onap5) - Vijay Kumar - DONE (06/17/2021)
- Verify spec can be run through bp-gen and deployed (backward compatibility)
26. Submit updates on each spec json update to gerrit (to be verified if updated spec breaks bp-gen creation - incase new fields introduced are not ignored)
27. Support for readinesscheck for script based execution (e.g PMMapper); port/endpoint flagged as mandatory fields which are required only for HTTP - added
28. Dynamic secret creation and mapping to env variable - support from Helm tool - added
TEST ISSUES TRACKED UNDER Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2839
...