...
- Assumptions
- CDP-PAL
- When invoking the authentication API call to MultiVIM’s identity url (passing in the openstack username, password, and identity service URL), we will get a token identical to the one we would normally receive from Openstack.
In order to access the Openstack provider API’s through the MultiVIM proxy, we need only replace the OpenStack service base url with the MultiVIM service base url. Furthermore, we expect the API response to be identical to what we would normally get if we had interacted directly with the Openstack Provider API.
e.g. instead of https://OpenStackServiceURL/v2.0/login, we will use https://MultiVimProxyServiceURL/v2.0/login.
- MutliVIM
- MultiVIM team is aligned with above assumption and is aligned with their plans
- CDP-PAL
- Impacts
- Development impacts for APPC, CDP-PAL, and MultiVIM teams
- Deadlines
- All components will be code complete by 8/20 with goal of being able to start pairwise testing week of 8/21 pending availability of an environment
- Testing- where?
- Most likely environment for use is the WindRiver Dev2Dev lab being setup by Integration team.
- Action: Randa to follow-up with Helen and Marco on readiness of this environment for testing start week of 8/21.
- Open Issues:
- What version of OpenStack does APPC need?
- https://releases.openstack.org/
- VoLTE is using Mitaka, which is EOL, we probably want Newton or Ocata - neet to verify.
- What version of OpenStack does APPC need?
- Testing- where?
- Sprint 1 Status
- Sprint One: 8/1 - 8/16
- Identify the functional test cases [APPC-105]
- This is done; A wiki page has also been added to track these test, plus individual JIRA issues to track automatio of each test case.
- Looking for volunteers to take on these test case automation. Please let me know if you want to take one on.
- Restart LCM action [APPC-88]
- This done and available; looking for place to validate, talking with Marco Plantania and Dan Rose about using an internal lab that has latest dockers deployed. Working with them to get vFW VNFs deployed and populated in AAI.
- This done and available; looking for place to validate, talking with Marco Plantania and Dan Rose about using an internal lab that has latest dockers deployed. Working with them to get vFW VNFs deployed and populated in AAI.
- Bug fix contribution [APPC-100]
- This is done
- This is done
- Functional test case automation - part 1
- Aaron has started working on one of them, but this will be part of Sprint 2, not 1 most likely.
- Still looking for volunteers to work the other ones.
- Aaron has started working on one of them, but this will be part of Sprint 2, not 1 most likely.
- SONAR blockers- Part 1
- We will do what we can in Sprint 1 bandwidth permitting.
- We will create another story for Sprint 2 to make sure we continue focusing on this.
- Need volunteers to look at issues.
- ODL upgrade
- This will move to Sprint 1.
- Per Dan Timoney (PTL for CCSDK and SDNC), Carbon package slipped to this week.
- Also, SDNC was refactored to move core functions into CCSDK, so we will have a bit more work to integrate Carbon ODL. This work is assigned to Patrick (APPC-91)
- OAM Epic (APPC-38)
- Will be submitted as part of Sprint 1. Stories moved to Sprint 1.
- Action: Discuss with Sharon if some stories need to be in Sprint 2;
- Update: CLOSED. All stories linked to Epic APPC-38 will be submitted in Sprin 1
- Update: CLOSED. All stories linked to Epic APPC-38 will be submitted in Sprin 1
- Identify the functional test cases [APPC-105]
- Sprint One: 8/1 - 8/16
- Documentation
- Working with Rich Bennett. He would like to use APPC release notes as the pilot project to demo their proposal for documentation using rst.
- The idea is that documentation is handle like code, files manage in code repos, changes need to be submitted to Gerrit for reviewes, tools are use for rendering, etc.