Initial Release for Frankfurt
- MUSIC now runs on a springboot server, instead of a standalone tomcat server
- HTTPS support for clients through AAF certificates
- A background lock clean up daemon will periodically check the status of current locks, cleaning up ‘stale’ references.
Clients should see a performance boost if they were previously dealing with many stale locks.
- Improved error messaging to the user, allowing clients to better debug their applications
- Continued adherence to ONAP S3P requirements
- Bug Fixes
- `MUSIC-573 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-573`_ Pods still run as root
- `MUSIC-557 <https://jira.onap.org/projects/MUSIC/issues/MUSIC-557`_ Test coverage goals met, and migrated to new sonar location
- MUSIC-530 Security Vulnerability in pom.xml fix
Known Issues N/A
MUSIC code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The MUSIC open Critical security vulnerabilities and their risk assessment have been documented as part of the project.
- MUSIC project page
- MUSIC Frankfurt Release
- Passing Badge information for MUSIC
- MUSIC Architecture Page
- Project Vulnerability Review Table for MUSIC
End of Release Notes