...
- Service flow updated to eliminate "homing emulator" and the corresponding "homing" step.
- Discussed with SDC and SO regarding use case design issues. Clarified that the use case requires both generic and custom flows. Scheduled a follow-up meeting with SDC to discuss specific design process and issues and possibly a demo. Help is needed from SO regarding custom workflow design process.
- vCPE-Infra Heat template on-boarding via SDC successfully tested with ONAP code in release-1.0.0 branch.
- vCPE-Infra on-boarding doesn't work with ONAP code in master branch. This is blocked by known issue with VID.
- Marco reached out to Danny for an ETA about vCPE component installation.
VoLTE use case
- SDC WAN service definition was reviewed. Only basic properties will be used in WAN service template for R1
- SDC import and export Tosca CSAR file structure was reviewed
- A&AI schema change for the use case was reviewed
- Test cases for VoLTE was updated
Reference VNFs (vFW/vLB)
- Both vFW and vLB installed and executed correctly in the following labs:
- Rackspace
- Private OpenStack Liberty lab
- Private OpenStack Mitaka lab
- WindRiver lab
- Issues with vDNS scaling scenario solved with help of Intel VPP team.
- No current issue to report.
Developer Lab
- Installed ONAP1.1 in WindRiver lab, all ONAP components passed sanity test
- Managed to pass vFW onboarding and service creation, and blocked on service instantiation. It seems the problem is in MSO, reported the issue on wiki