...
- Need to follow-up with SDC again on their plans to move to onap from openecomp; we still have not gotten feedback on timeline for this dependency yet. Takamune Cho to follow-up with SDC,
- Update 2-14-18: Per TPL, Michael Lando, SDC will address namespace change in their next sprint, so looks like APPC won't be able to finish APPC-13 until Sprint 4. There is still an open issue on use of openecomp-tosca-lib, which needs to be clarified.
- Update 2-14-18: Per TPL, Michael Lando, SDC will address namespace change in their next sprint, so looks like APPC won't be able to finish APPC-13 until Sprint 4. There is still an open issue on use of openecomp-tosca-lib, which needs to be clarified.
- Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
Update: 2-07-18: Meeting moved to this Thurs, 2/8/18- Update2Update: 2-14-18: Meeting on 2/8 was canceled; Sai indicated another will be schedule this week.
New Actions Items:
- Scott Seabolt & Aaron Hay to work together to pull together some lab diagrams for WindRiver lab setup for APPC usage (clustered vs non-clustered environments)
- Aaron Hay to add details on his work on Resiliency epic on wiki - APPC Beijing Testing - feel free to add wiki pages under this entry to capture details.
Notes:
- Sprint 2 started on 2/8 and ends on 2/22.
- M2 deadline was on 2/12
- Sprint 2 status
- Security
- APPC-486 - secure DMaaP topics - currently unassigned.... move this to Sprint 3
- Code Coverage
- APPC-437 - Michal - will this be implemented for the methods documented ?
- APPC-501 - Atul - can this be closed?
- APPC-533 - Shubhada - plan to complete by 2/22 - moved this to backlog; move APPC-617 to Sprint 2
- APPC-439 - Tomasz - In-Progress...
- Taka - which issues can we move to Sprint 2?
- APPC-600, 615, 624, 626, 635 moved into Sprint 2.
- ODL upgrade - APPC-403 (Patrick)
- Dependency on CCSDK - follow-up with Dan, he said he would have it ready this week.
- Patrick Brady to follow-up with Dan on readiness of ODL from CCSDK.
- Resiliency (Aaron)
- Merging work on 476 & 475Kurbenetes master and worker setup; OOM, troubleshooting some issues
Made a lot of progress - Kurbenetes w/OOM setup in WindRiver similar to what SDNC had as documented on their wiki. Everything is working correctly.
- APPC installed correctly, all the bundles successful. Next step to work on - scale out replicas, which was not successful - if we want APPC to be able to change the number of replicas for appc or appc-dbhost, then statefulset.yaml files will need to be created similar to SDNC
Aaron has as separate environment for work on the resiliency testing (does not interfere with environment being used by Stability team) - working on getting Appc working in Kubernetes
- Action: Randa to setup call with James McNider & Sharon to discuss with SDNC has done.
- Action: Aaron to document details of his efforts on APPC wiki
- I added this wiki page and subpage to start adding details: APPC Beijing Testing
- CDT
- Waiting
- Waiting on License scan to complete before pushing code to LF
- Patrick to create verify jenkins job for cdt repo (APPC-627) - put into Sprint 3
- Manual Scale Out
- APPC-479, APPC-544, (Vidhya)
- worked on the services classes, working on junit
- will submit by end of week
- APPC-543 (Ramya)
- Code submitted, story can be closed once code is merged.
- However, requirements are still churning a bit on this, so will have additional changes probably in Sprint 3.
- APPC-479, APPC-544, (Vidhya)
- Stability - 72hr soak
- APPC-456 (Scott, Ryan)
- APPC-456 (Scott, Ryan)
- Documentation
- Nothing planned for Sprint 2
- Platform Hardening
- APPC-13 - namespace update - Moved to Sprint 3 since SDC will not address their changes until next sprint
- Security
- Amsterdam jenkins jobs will be removed (APPC-625)
- working on jmeters tests, loading AAI data, set up VMs, but they are evacuating which causes more work for us (we need to keep snapshots around to minimize the impact)
- Initial testing will be done on the non-clustered environment, but moving to clustered later should be just a matter of pointing to the clustered environment.
- Where do we want to put the tests? Deployment project..
- Action: Create wiki to track our testing status
- I added this wiki page to start populated tests: APPC Beijing Testing Scope and Status
- Documentation
- Nothing planned for Sprint 2
- Platform Hardening
- APPC-13 - namespace update - Moved to Sprint 3 since SDC will not address their changes until their next sprint, which wont start until end of Feb.
- Amsterdam jenkins jobs will be removed (APPC-625)
- Vacations
- Ramya - 2/13/18 - 2/26/18
- Atul - 2/16/18 - 3/5/18
- Other topics ?discussed
- Need to review latest email from Steve Winslow received today on license items.
- Gerrit submits addressing more than just Sonar issue; reviewing some submissions is difficult because a lot of code is moved around. Options proposed by team: Only allow 1 sonar issue per Gerrit submit, stick to fixing the specific Sonar issue and don't try to restructure file, etc.... We don't want to discourage contributions;however, we are responsible as committers to ensure the health of the application, so I propose that code review session be requested with the contributor to step through their changes and have him/her explain the changes and their reasoning behind those that are not clear.
- We really need to put priority on code coverage/junits since that's tied to the S3P requirements; however, this is difficult to enforce for folks that are not formally part of the APPC Beijing team.