| Table of Contents |
|---|
Architecture Changes since Beijing
...
- No updates since Beijing: https://wiki.onap.org/display/DW/MUSIC+Cassablanca+Release+PlanningWe where we satisfied the requirements of Cassablanca as well.
- While we had two documented vulnerabilities in Beijing for which we obtained a TSC exception, now we do have new vulnerabilities (critical and severe) that we will address before M4.:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MUSIC-104 CII badging –
100%100% https://bestpractices.coreinfrastructure.org/projects/1722
- Code Coverage > 60%
MUSIC repos in R3
- music
- music/prom
- music/distributed-kv-store
IM/DM Alignment
- NA
API Update
...
...
API enhancements
Enhanced the onboarding admin API to provide callback functionality wherein the onboarded app can specify tables, columns, callback REST URL wherein if a column changes, MUSIC will call the callback REST URL- Used by OOF HAS to efficiently read their job queue maintained in MUSIC.
Provided/Consumed Interfaces
