#opnfv-mano: mano-wg

Meeting summary

1. 1. rprakash (rprakash, 13:58:44)
   2. https://global.gotomeeting.com/join/229632485 (rprakash, 14:03:33)
   3. Bryan Sullivan (bryan_att, 14:04:23)
   
   
2. agenda bashing (rprakash, 14:04:34)
   1. https://wiki.opnfv.org/display/mano/OPNFV+MANO+Work+Group+Meetings (rprakash, 14:04:47)
   2. Juju vnfm integration has some issues (rprakash, 14:09:40)
   3. juju command to start the test or API ? - APIs are noavailable to run tests (rprakash, 14:10:33)
   4. https://github.com/juju/python-libjuju/issues/106 (mpauls, 14:11:26)
   5. Deploy and configuring Juju is a major issue (rprakash, 14:12:44)
   6. https://jujucharms.com/docs/2.2/reference-install (rprakash, 14:14:28)
   7. to implement script to automate juju vnfm install and configure on jumphost - needs help from Canonical or any juju expert (rprakash, 14:16:04)
   8. prefer use of generic vnfm for now untill this is resolved (rprakash, 14:17:51)
   9. we move the JOID discusssion to JOID meetying in next 2 hrs (rprakash, 14:18:40)
   10. Narinder Gupta (narinder`, 14:20:43)
   
   
3. auto & opera (rprakash, 14:20:50)
   1. https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216 (rprakash, 14:20:51)
   2. https://wiki.opnfv.org/pages/viewpage.action?pageId=12387216 (rprakash, 14:21:01)
   3. auto is about using onap to test over OPNFV poject like Opera which can focus on test scenario (rprakash, 14:23:20)
   4. Auto will focus on specific scenartio to test (rprakash, 14:23:58)
   5. opera will focus on overall deployment of onap with specifc scenario (rprakash, 14:24:27)
   6. (helen) Opera plans to go full integration foe all use cases but does not have enough resources so there is scope for collaboration (rprakash, 14:29:34)
   7. (helen) use cases vCPE, vOLTE, VFW, different cloud , different functest - end to end (rprakash, 14:30:42)
   8. (Bryan) narrow to how do you deploy onap, LCM of VNF (rprakash, 14:31:26)
   9. (Helen) OLAP Operations Manager - Manges LCM of ONAP, DCE (ONAP) , MuliVIM (rprakash, 14:32:35)
   10. (Bryan) e.g Barometer and Bamboo in OPNFV is usefull for ONAP and similarly Yardstick, Netreay and Gluon and DPDK usgae etc are needed fro ONAP and this we can work through ONAP (rprakash, 14:37:28)
   11. (Bryan) Auto want's to use the above (rprakash, 14:37:58)
   12. (Helen) Can we do it under one ubrella let it be called AUTO if the helps (rprakash, 14:38:41)
   13. (tina) any inputs on merging proejcts Opera and AUTO with better understanding (rprakash, 14:40:06)
   14. (Bryan) there is a consensus that we should work together in a single project (rprakash, 14:41:57)
   15. (bryan) we defer the discussions through email and bring it to Tech meeting tomorrow to go over more details on content of project , naming, merger (rprakash, 14:43:57)
   16. (bryan) tags can be used hold the old code and move to new repo (rprakash, 14:45:29)
   17. (helen) charter can be changed to accomoadte both auto and opera for consolidation (rprakash, 14:48:15)
   18. ACTION: (Prakash) to get tech meeting tomorrow in OPNFV for the continuation on the discussions on AUTO+OPERA (rprakash, 14:48:59)
   19. lab as a service needs adressing between OPNAP and OPNFV can be brought in future meetings (rprakash, 14:51:18)
   
   
4. . Dovetail - Testing gaps (rprakash, 14:51:59)
   1. https://github.com/openstack/tempest (rprakash, 14:57:42)
   2. vnf behaviour and VLAN tagging covergae through API, can be explored , from OpenStcak (rprakash, 14:59:16)
   3. ACTION: (srikanth) to provide the test cases to cover (rprakash, 15:00:16)
   4. next week we go over the same in details (rprakash, 15:00:34)

Action items

1. (Prakash) to get tech meeting tomorrow in OPNFV for the continuation on the discussions on AUTO+OPERA
2. (srikanth) to provide the test cases to cover

People present (lines said)

1. rprakash (41)
2. collabot (4)
3. bryan_att (3)
4. mpauls (1)
5. narinder` (1)
6. Michael__ (1)
7. helenychen (1)
8. uli-k (0)