Recurring Meeting (Weekly Monday 9-10 am EST)
Zoom details:
https://zoom.us/j/2672903080
Phone: +1 646 876 9923
Meeting ID: 802 547 419
Release Planning
Amsterdam Release
Music project was not part of Amsterdam Release scope.
Beijing Release
M1 Release Planning link
- M1 Release Planning Checklist link
- M2 Functionality Freeze Checklist link
- M3 API Freeze Checklist link
- M4 Code Freeze Checklist link
- RCx Checklist link
- Sign-Off Checklist link
Cassandra Release
Place for whatever the team needs
Basic Benchmarks
Minutes (02/05/2018)
- Tom: Music code is in there but Bharath, the PTL, needs to review it.
- Shashank: Distributed KV store will stay in Consul since config4j supports only that. Maybe a change of name? Also, by end of week basic test cases and API documents (maybe even as a pdf while Sashank explores Swagger integration).
- Vishwa: To integreate with OOM first need to make sure containers are created as part of build.
Minutes (01/29/2018)
- Import MUSIC code from ATT to ONAP by end of week [Tom]
- Prepare draft of functional test cases before next meeting [Bharath, Tom, Garima]
- OOM integration [Tom to create JIRA entry, Vishwa will track this with OOM]
- Understanding Distributed KV store responsibilities regarding milestones [Sashank]
- Potential integration of Distributed KV store as a recipe on top of MUSIC [Sashank]
- Greg will generally be available to handle JIRA issues once prioritized
- Agenda for next meeting: Go over all the above and deep dive of MUSIC concepts [Bharath]
- Send invite for regular meeting slot [Bharath]