Here is the quick meeting note from our weekly meeting last week
1: PTL election started on Thursday and concluded on Saturday. Xinhui was voted as PTL. Congratulations Xinhui!
2: MultiCloud release planning page has been setup. https://wiki.onap.org/display/DW/Multi-Cloud+Release+1+Planning
- Gil has volunteered to create functionality requirement for release 1 in terms of epics and user stories. The release planning page is already hooked with JIRA. Once Gil populated the information into JIRA, we will be able to review and decide on what to include for R1.
3: Discussed release 1 target architecture
- Danny took action item to update the slide. This is done, see attached slide 2 and 3.
- Committers and volunteers are needed to dedicate time next week to work on release 1 target architecture (slide 2). The consensus is that the architecture should focus on enabling minimal feature set supporting the sequence flows of vFW, vDNS, and vEPC use cases
Please send email to Xinhui, the newly elected PTL, and cc everyone in this email list, if you like to contribute.
- Slide 3 describes one possible approach for R1 API design. The main goal is to maintain OpenStack API compatibility while evolving towards a common API framework. Robert, Bin H, and Danny will discuss this further. Anyone who is also interested in this, please let us know.
4: Given R1 tries to keep OpenStack compatibility, it is relatively straightforward for most cloud providers who support OpenStack already. Eric and Andrew will work on a proposal to incorporate Azure into R1.
5: Once we have finalized the use case (epic and story), architecture, and API design, we will start mapping out release milestones.