...
- CDS-UI - CCSDK-3814CDS-UI must be able to listen on HTTP Open → DT /TM has a look
- SO Monitor - SO-4027Make SO-Service-Monitor ServiceMesh compatible Open → Byung mentioned, that E/// team try to resolve the issue (Byung's note: It was assigned to Viresh Navalli, Capgemini. E/// plans to assist Viresh as needed.)
→ postpone to Montreal - DCAE Restconf → https://gerrit.onap.org/r/q/project:dcaegen2/collectors/restconf → Implementation done → missing OOM patch (check in DT)
- CLI will not work without fix... ( - OOM-3096[CLI] Remove AAF dependency Delivered )
- UUI - not clear if working
- MSB issue reported:
(helong <hwx171157@163.com>)Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key MSB-755
- MSB issue reported:
...
- SDC Listener HTTP issue - SDC-4233SDC Distribution Client should work with lower-case Header entries Closed → Marek provided patch → merged, need to be released and can be used in the clients
- When released, all clients need to be updated (CDS, AAI, Policy, SO, ...)
- Create tickets for all clients....
- Strimzi improvement (monitoring configmap) → Miro create patch here [STRIMZI] Monitoring chart improvement
- Question:
- Proposal: How to break up ONAP monolithic versioning schema
- if a central values.yaml with global settings is a good approach to decouple the components
- Databases (e.g. Cassandra) used by OOM components
- How to update external resources from the outside:
- strimzi
- keycloak
- Helm
- K8s
- kustomize and Databases:
- Cassandra
- Postgres
- TimeSeriesDB ...
- Proposal: How to break up ONAP monolithic versioning schema