...
- Release Plan - high level proposal reviewed with the team;
- Sprint One: 8/1 - 8/16
- Identify the functional test cases [APPC-105]
- Restart LCM action [APPC-88]
- Bug fix contribution [APPC-100]
- Functional test case automation - part 1
- Can we automate any during sprint 1?
- SONAR blockers- Part 1
- ODL upgrade???
- Updated ETA from SDNC is now 8/4; so tentative at this point if this is Sprint 1 or 2
- OAM Epic (APPC-38)
- Action: Discuss with Sharon if some stories need to be in Sprint 2;
- Sprint Two: 8/17 - 8/31
- AT&T feature contributions (epics: APPC-9, 22,12,10,11,53,57,62,63)
- ODL upgrade ??
- Functional test case automation - part 2
- LCM API Doc upgrade
- SONAR blockers/criticals - Part 2
- Sprint Three: 9/1 - 9/14
- MultiVIM integration testing
- SONAR - blockers/critical - Part 3
- Documentation updates (Epic APPC-89)
- Release Notes
- API Guide
- User Guide
- APPC Client Library Guide
- Sprint Four: 9/15-9/29 - Hardening
- University training recordings
- Scott - APPC overview
- Paul - APPC model driven
- Defect fixes as needed
- University training recordings
- Sprint One: 8/1 - 8/16
- Comments on release plan:
- no major issues raised by team
- question/concern raised on heavy loading of Sprint 2, but that is where the bulk of the code contribution from AT&T and AMDOCs is coming. We will need to see how we can mitigate this during Sprint 2. Will explore to see If there are opportunities to get some of this in Sprint 1.
- JIRA APPC board currently reflect above plan for the most part: APPC JIRA Board
- no major issues raised by team
- Story Pointing Approach….
- We did not get a chance to cover this topic, but my proposal is to use a simple story point method for R1 : 1 or 0
- 1 means in-progress
- 0 means it's done.
- This method seems most reasonable for this release since many of the contribution are coming items being worked by various companies and being pushed to ONAP..
- Reminders of JIRA good practices:
- When you start to work a story or bug, move State to In-Progress.
- When you deliver or close a story or bug, don't forget to update the Resolution field; i.e., don't leave it Unresolved!
- We did not get a chance to cover this topic, but my proposal is to use a simple story point method for R1 : 1 or 0
- Review list of Test Cases (unit, functional, integration) - what can be automated, what can’t be automated; any we can undertake in Sprint 1
- Story: https://jira.onap.org/browse/APPC-105
- Wiki: https://wiki.onap.org/display/DW/Funtional+Test+Cases+for+Amsterdam+Release
- Refer to above wiki for the list of functional test cases for automation.
- Refer to above wiki for the list of functional test cases for automation.
- What we commit to for automation, we will need to have 50% completed by 8/21
- MultiVIM discussion/priority
- Discussion took place with CDP-PAL team
- Identified list of actions that are needed by APPC
- We prioritized list into Priority 1, 2, 3, priority 1 being what we need to support vCPE use case, however, we would also like priority 2.
- Thanks to Scott Seabolt and Ryan Young, following list was provided to CDP-PAL team.
- CDP-PAL team to complete the mapping of CDP action to openstack action.
- MultiVIM has requested changes from CDP-PAL by 8/20; hence, APPC has integration with MultiVIM in Sprint 3.
- I have requested that integration to MultiVIM be transparent to APPC because I want fallback plan to be CDP-PAL without need to make code changes. All this is still under discussion.
- Review M2 checklist
- Communication - IRC channel (#onap-appc)
- https://www.irccloud.com/#!/ircs://chat.freenode.net:6697/%23onap-appc
- Thank you Marcus for setting this up.
- We will need to be able to communicate in real-time as testing kicks off in earnest, so this is important.
- AT&T folks will need to request approval to unblock irccloud.com domain- I will share details, SLA is not quick…
- Labs
- Marco Platania has a rackspace lab that is used to deploy new dockers on daily basis, so we will be running through some level of integration testing to make sure we are not breaking anything. We will not have access to do dev testing in this lab, but we may possible request some specific tests. Marco will reach out to APPC if he sees problems.
- Additionally, Hector is working on his internal lab - making good progress.He was able to bring up a fully working (as far as passing healthchecks go) ONAP instance, We didn't get a chance to discuss this one, we can get more next week.
- Lab with vCPE? Still under discussion, no conclusion yet.
- Sonar
- We have been given a target for unit test/code coverage for R1 - 30% - 50%
- There is an issue with Sonar not reporting correct data (we were at 18%, but now shows 0%)
- Ticket opened with LF Helpdesk (ONAP Helpdesk #43745), no response yet.
- R1 blockers
- List was started as part of Virtual developers event - can be found here:
- I added dependency on ODL Docker from SDNC tean.
- Do you have any other you want to add?
- List was started as part of Virtual developers event - can be found here:
- OpenECOMP vs. ONAP renaming (APPC-13)
- This came up as a topic in PTL weekly call
- Making change from openecomp to onap has wide and extensive implications, cannot be accommodated in R1 without impacting other scope.
- Discussion being taken up by TSC - proposal is to identify plan in R1, execute in R2
- Waiting on guidance for this story.