- Time: August 29, 2016, starting at 9:00AM
- Room: Floor 2,splendid Hall
- Hotel: DoubleTree by Hilton Shanghai - Pudong
- Address: 889 Yanggao Nan Road, Pudong Shanghai, P.R.China, 200127
- Food will be served: AM tea time/ PM tea time, Buffet lunch
You are invited to a Zoom meeting now.
Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/215866962
Or iPhone one-tap (US Toll): +14086380968,215866962# or +16465588656,215866962#
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 215 866 962 International numbers available: https://huawei.zoom.us/zoomconference?m=4JT4qWB9BE5PTVu-BC2fw-dsi3jKbeZ6
Or a H.323/SIP room system:
H.323: 188.8.131.52 (US West) or 184.108.40.206 (US East) Meeting ID: 215 866 962
Integration current Infrastructure - Tools update by Gary Wu
Use Case break down and Testing strategy by Casem Majd
NFVO introduction by Chengli Wang
OPEN-O test lab by Chengli Wang
OPNFV the 2nd plugfest plan by Chengli Wang
Integration Workshop Presentation-Common Service by Huabing Zhao
OPEN-O API Portal Proposal by Huabing Zhao
Open-O Integration F2F Shanghai Summery by Helen Chen and more
August 29, 2016 Integration Day Meeting Minutes
Use Case break down and Testing strategy
Emphasize that each team should automate the functional testing. Mock up server may be used to simulate external components.
Question on Mock server and Driver integration testing (Lizong)
Assumption is that test case covers the described the agreed Use Case.
Assumption presented are agreed by all participants (slide 11)
Release 1 is single tenancy.
Integration current Infrastructure - Tools update
Talk about all the repos we have in OPEN-O.
More specific on Oparent, License check,
Code style (setup as warning in Sun Release), Google style (which is well known and well documented)
Explanation of what Nexus provides: Repository for Java
CI Management Jenkins Jobs:
JJB job: comprehensive versus core
Explanation on how to setup the environment
Language to be checked: Oparent will perform checks only for Java in Sun Release.
Question: Backward Compatibility.
Answer: because we are in a very early stage (incubation), API changes are allowed, communication to the whole team is critical.
Question: Who is writing unit test code.
Answer: the developers.
Question: Who execute the unit test code.
Answer: the Jenkins infrastructure will invoke the test.
Gary to publish his slides and link from here.
API Portal, levearing Micro Service
OPEN-O API Portal Proposal
Proposal to address problems: format consistency, no API portal, manual update of documents
This proposal should be seen as an internal OPEN-O tool to generate and present APi. This is not something we will put into production.
Question: Should we use Swagger to first define our needs and the derive the code, or do the reverse, write the code and generate the definition.
Answer: as we are reaching M3 , the code is ready to generate the API. This discussion is also in mail list.
Question: Where should the proposed model be applicable: Inner or Outer API discussion.
Answer: Stretch goal for Outer for Sun Release.
Huabing and Alex: Offline discussion on the necessity of Service name Suggestion to make reservation for Tenant ID. Further team discussion needed (Alex) Concern on using VMs and deployment impact. Further team discussion needed (Alex)
Presenter: Li Zhongbiao
Slide deck presentation.
Numerous questions on the structure of Lifecycle Manager. Discussion on where VNFM Driver should be or not inside the NFVO box. More talk needed.
Deployment concerns on laptop? Maybe We should design different levels of deployment policies according to the workload, for the lowest level NFVO can be deployed on single VM, rack server or laptop.
Slide deck presentation
Integration Workshop Presentation-Common Service
Integration Community Lab
OPEN-O test lab presentation
The focus of the lab is to provide an environment for demo purposes. This is not for integration testing.
Discussion if the lab availability is or not a Sun Release deliverable. The Lab Team will take OPEN-O cpts as they become available but won’t be able to have the demo lab available the same day as the Sun release. This has to be brought to TSC knowledge (there may be other expectation that we don’t know) and approval.
Action Item: Get approval from TSC on the discussion regarding Lab availability date.
Discussion on what to demo
Who will be here
- Helen chen@huawei
- Wan Qing@Ericsson