...
8. Support MAPPING requirement – Postgres (refer REQ #5 for details) - Target 06/30 DONE 1.3.2
9. Support MAPPING requirement – Policy Sidecar (refer REQ #4 for details) Target 06/17 DONE 1.3.2
Format written out into values.yaml not as expected
Test completed on 1.3.5
10. Support SERVICE MAPPING based on spec file (refer REQ #7 for details) - DONE - 1.0.0
...
- Optional specSpecma json file ( if not provided, it will not validate the schema as of 7/16/21)
For example,
java -jar ./helmchartgenerator-1.3.5-SNAPSHOT.jar vescollector-componentspec-v3-helm.json ./blueprint ./output schemas/specSchema.json
java -jar helmchartgenerator-1.3.5-SNAPSHOT.jar ./input/specs/hv-ves-collector.componentspec-new.json ./input/blueprint ./output ./schemas/specSchema.json
helm install command
java -jar ./helmchartgenerator helm install --set global.dockerHubRepository=nexus3.onap.org:10001 dev-dcae-ves-collector -n onap ./dcae-ves-collector-1.38.5-SNAPSHOT.jar vescollector-componentspec-v3-helm.json ./blueprint ./output schemas/specSchema.json0.tgz --set global.pullPolicy=IfNotPresent
- 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 (pending test)
- https://git.onap.org/dcaegen2/collectors/datafile/tree/datafile-app-server/dpo/spec/datafile-component-spec.json (pending test)
- 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 - ENV DONE (06/17/2021)
- Verify spec can be run through bp-gen and deployed (backward compatibility) - - Sivakumar Santharam DONE
- New spec schema not backward compatible; bp-gen and onboardingAPI needs to be updated to reflect schema + onboardingAPI?
- New spec schame will be added under v3 directory
...
31. OnboardingAPI changes to use V3 spec files for supporting helm spec files - added
32. Syncup latest oom/templates under repo:test/blueprints
TEST ISSUES TRACKED UNDER Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DCAEGEN2-2839
...
| Component | V3 Schema | V2 Schema | With CMPV2 | With Postgres | With Policy |
|---|---|---|---|---|---|
| VESCollector | vescollector-componentspec-v3-helm | vescollector-componentspec | vescollector-componentspec-cmpv2-v3-helm | vescollector-componentspec-postgres-v3-helm | |
| TCAgen2 | tcagen2_spec-v3-helm | tcagen2_spec | tcagen2_spec-policy-v3-helm | ||
| PRHPRH | prh-componentspec-v3-helm (pending test) | prh-componentspec | |||
| hv_vescollector | hv-ves-collector-componentspec-v3-helm (pending test) | hv-ves-collector.componentspec | |||
| PM-Mapper | |||||
| DataFileCollector (DFC) |
REFERENCE
Discussed ppt slides Helm_deployment.pptx
...