...
6. Support MAPPING requirement – ENV SETTING (refer REQ #1 for details) - DONE - 1.0.0
Schema Validation to be integrated - tracked separately under task #24
7. Support MAPPING requirement – CMPv2 Certificates (refer REQ #3 for details) - Target 06/24 completion24
Include support for base + addon chart structure (certificate.yaml will be optional) - DONE -1.0.1?
Add validation if enabled in spec and certificate.yaml not provided - tool must error error - switch to use use_external_tls/flag
8. Support MAPPING requirement – Postgres (refer REQ #5 for details) - Target 06/30
9. Support MAPPING requirement – Policy Sidecar (refer REQ #4 for details) Target 06/17 completion17
Format written out into values.yaml not as expected
10. Support SERVICE MAPPING based on spec file (refer REQ #7 for details) DONE - DONE - 1.0.0
Schema Validation to be integrated - tracked separately under task #24
11. Support MAPPING requirement – ConfigMap support (refer REQ #2 for details) Target 06/30
12. Support MAPPING requirement – DMAAP Secure Topic/Feed (refer REQ #6 for details)
...
20. Comments should be cascaded from template and when new yaml is generator and also preserve order
21. Secret mapping requirement TBD and pv mapping - Vijay Venkatesh Kumar - Target 06/30
- CMPv2 + application_env
22. Support chart generation as directory (instead of tgz) via configuration (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)
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 Venkatesh Kumar - DONE DONE (06/17/2021)
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)
TEST ISSUES TRACKED TEST ISSUES TRACKED UNDER Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-2839
...
Code Block | ||||
---|---|---|---|---|
| ||||
externalVolumes:
- name: dcae-external-repo-configmap-schema-map
type: configmap
mountPath: /opt/app/VESCollector/etc/externalRepo/
optional: true (default)
- name: '{{ include "common.release" . }}-another-example' //dcae-external-repo-configmap-sa88-rel16
type: configmap
mountPath: /opt/app/VESCollector/etc/externalRepo/3gpp/rep/sa5/MnS/blob/SA88-Rel16/OpenAPI
optional: false //If set to false, the configMap must be present in order for the microservice's pod to start. Defaults to true. |
...
Code Block | ||||
---|---|---|---|---|
| ||||
################################################################# # Secrets Configuration. ################################################################# secrets: - uid: &pgUserCredsSecretUid pg-user-creds name: &pgUserCredsSecretName '{{ include "common.release" . }}-pmsh-pg-user-creds' type: basicAuth externalSecret: '{{ ternary "" (tpl (default "" .Values.postgres.config.pgUserExternalSecret) .) (hasSuffix "pmsh-pg-user-creds" .Values.postgres.config.pgUserExternalSecret) }}' login: '{{ .Values.postgres.config.pgUserName }}' password: '{{ .Values.postgres.config.pgUserPassword }}' passwordPolicy: generate postgres: nameOverride: dcae-pmsh-postgres service: name: dcae-pmsh-postgres name2: dcae-pmsh-pg-primary name3: dcae-pmsh-pg-replica container: name: primary: dcae-pmsh-pg-primary replica: dcae-pmsh-pg-replica persistence: mountSubPath: pmsh/data mountInitPath: pmsh config: pgUserName: pmsh pgDatabase: pmsh pgUserExternalSecret: *pgUserCredsSecretName '{{ include "common.release" . }}-pmsh-pg-user-creds' |
Note: applicationEnv setting if required should be mapped from spec as-is (req#1). Example above contains <pmsh> part of secret name and PG name which should be mapped to component-name from spec file
Requirement.yaml
Code Block | ||||
---|---|---|---|---|
| ||||
- name: postgres
version: ~8.x-0
repository: '@local'
condition: postgres.enabled |
6. DMAAP – Secure Topic/Feed (WIP)
...