Date and Time: PST 8:00am / UTC 16:00, Friday November 20, 2015
Chair: Bin Hu (AT&T)
Bin shared the information of OPNFV Summit. Our presentations / sessions went very well. One question was why to use ODL. We responded that we encourage more community involvement, and more experts in OpenContrail and ONOS to experiment IPv6 setup in variety of environment.
Meenakshi shared the questions that she discussed in the summit. Basically:
- Use OpenStack to configue radvd
- Use opentstack to add IPV6 routes on the router.
Sridhar indicated that it was because of the bug of ODL that doesn't support IPv6 router.
Bin suggested that Meenakshi start an email thread with Isaku to discuss the details. Meenakshi started the email discussion at the end of the meeting.
Prakash shared his draft of test plan. The team further refined the test scenarios. One uncertainty is whether or not Yardstick is able to perform the test under our setup scenario.
Prakash said that their Huawei experts on Yardstick is visiting their Santa Clara office. He would set up a meeting today to discuss the details. All agreed that Prakash set up the meeting.
Prakash set up the meeting with Huawei's Yardstick expert in Santa Clara. All local IPv6 team members are invited to attend in person for better discussion.
Bin, Prakash and Huawei team Weidong, Ulas, Mei Mei, Matthew Li, Guoku Bai and Hongbo Tian met in Huawei's office in Santa Clara. Qi attended remotely. After discussing the details of IPv6 setup, and the way how Yardstick works, the conclusion is that Yardstick should be able to support this testing, although several changes are needed. For example, the pre-condition should be that VMs of IPv6 setup have been spawned already, and Yardstick will do the testing by ssh to those VMs. And after testing, Yardstick will not destroy VM. This is different from normal Yardstick testing where Yardstick will spawn VMs, launch VNF and test. After testing, Yardstick will destroy VMs.
Huawei team agreed to experiment IPv6 setup in Huawei's Pharos community lab, and explore Yardstick testing on top of it in the next 2 weeks to identify the workload, and best solution to support this type of testing.