...
- What your team has achieved
- vCPE:
- Confirmed that the following interfaces related to CLAMP have been defined, implemented, and tested internally inside AT&T: SDC-CLAMP, SDC-DCAE, CLAMP-DCAE.
- SDC briefly confirmed that the vCPE model can be fully supported. Will hold a meeting with SDC to go through the details.
- Discussed with the VNF developers to revise the design to support auto healing closed loop control.
- Revised the service model to better emulate the real life situation.
- Confirmed the design process of policies for both closed loop and non-closed loop rules.
- vCPE:
Block issues / help needed
- vCPE:
- To clarify the format of recipes and what tool to use to create such recipes (The SDC team does not have a answer to this).
- To confirm the support of the service model in SDC.
- To follow up with different projects to collect information and sample designs for each feature (refer Q22 on Use Case Related Important Questions and Answers)
- vCPE:
- Reference VNFs (vFW/vLB)
- Still working on the installation of the vLB/vDNS VNF in the WindRiver lab
- Intel team is helping out with VPP LB configuration
- Debugging patched VPP 1707 release in local OpenStack environment
- Testsuite
- Implementing Java build for python code
- Merging above code with oparent
- Adding verify and merge jobs for python code in new format
- Adding testing via tox in java based python
- O-Parent
- Formally requested PTLs to update their POMs to inherit from oparent: https://lists.onap.org/pipermail/onap-discuss/2017-July/002762.html
- Logged tracking JIRA issues against the O-Parent epic:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-5 - Working on scripts to verify oparent implementation across projects
- Release
- Sent out poll to PTLs on interest in using a centrally managed standard docker build process: https://lists.onap.org/pipermail/onap-discuss/2017-July/002792.html
- Migrated docker image build scripts from OPEN-O