#opnfv-mano: mano-wg

Meeting summary

1. 1. Uli (uli-k, 14:00:31)
   2. https://wiki.opnfv.org/display/meetings/MANO+Working+Group+Meeting (uli-k, 14:01:41)
   3. Aimee joined now (rprakash, 14:13:36)
   
   
2. Agenda Bashing (rprakash, 14:14:09)
   1. https://global.gotomeeting.com/join/229632485 (rprakash, 14:14:40)
   2. we do irc only and will quit the GTM (rprakash, 14:16:08)
   3. I wanted to go over action Items at start of Agenda Bashing and clean the agenda (rprakash, 14:17:01)
   
   
3. Agenda Bashing (Action Item review from last week) (rprakash, 14:17:36)
   1. the slides are in pdef fiel (rprakash, 14:19:47)
   2. https://wiki.opnfv.org/download/attachments/6826259/ONAP%20Use%20cases%20%26%20OPNFV%20Opera%20considerationsv2.0.pdf?version=1&modificationDate=1495212290000&api=v2 (rprakash, 14:20:00)
   3. importnat notes - ONAP Project plan slide on slide 10 shows that ONAP 1st code output for Opera to be available on August 3 (rprakash, 14:21:20)
   4. until Aug 3 , Opera can n ot start and planning for F-Release particaption starts then (rprakash, 14:22:00)
   5. The expetations stated from ONAP team is that Opera should be able to help them in testing NFVO bundle available then in Nexus and and file any bug reports to ONAP (rprakash, 14:23:13)
   6. this means the they can run their CI Build process by pulling from upstream Nexus repo (rprakash, 14:24:11)
   7. OK do you want me to start GTM again? (rprakash, 14:24:33)
   8. (uli) not possible if no partcoipation E-Relase but for F-Release they can untill then work with ONAP and for Sceneario it will be good to look after August (rprakash, 14:32:21)
   9. no project in ONAP is yest approved and there are apparently 30+ on their pipeline (rprakash, 14:33:21)
   10. Opera issues closed for untill August (rprakash, 14:33:55)
   
   
4. 2. Release E followups on MANO projects plans and inputs from PTLs (rprakash, 14:34:33)
   1. c. Write a Juju charm for installing Open Baton and ONAP / Test Juju charm - (Action Item closed) (rprakash, 14:35:03)
   2. A juju charm allowing instantiating Open Baton has been implemented. Its code has been placed on github as suggested by Narinder: https://github.com/openbaton/juju-charm (rprakash, 14:36:46)
   3. https://github.com/openbaton/juju-charm (rprakash, 14:37:19)
   4. the seond Item of Integrating Charms for OpenBaton was to be taken us using Conatiners and hence we said that Build and Deploy steps for OpenBaton Intgeration should be seperated as two steps (rprakash, 14:39:38)
   5. the Designa and Build can be discussed in MANO but Deployment has been to Infra wg and Uli+Giuseppe assigned this action (rprakash, 14:40:33)
   6. Orchestra project needs to clarify what they want to achieve in Euphrates. (uli-k, 14:42:12)
   7. they need to define scenario etc. (uli-k, 14:42:38)
   8. we need to understand whether there are additional requests to infra. E.g. can they run on any Pharos POD? (uli-k, 14:43:19)
   9. EUAG Pain Points is back to Tech meetings (rprakash, 14:43:51)
   10. (Narinder) JOID plans to support OpenStack Ocata with noSDN scenario for OpenBaton in release-E. (rprakash, 14:44:45)
   11. (Narinder) If ODL support for charm is added later it may consider that for OpenBaton at that time and Giuseppe to take it further for OpenBaton/Orchestra)) (rprakash, 14:45:19)
   12. this seems like multi-installer support for MANO scenarios (rprakash, 14:48:12)
   13. like Apex for ODL VIM and Juju for NFVO+VNFM (rprakash, 14:48:39)
   14. check https://gerrit.opnfv.org/gerrit/#/c/30679/ (uli-k, 14:49:38)
   15. that's example for MANO SDF (uli-k, 14:50:03)
   16. Will any projects use Pike features for OpenStack in MANO integration? (rprakash, 14:50:15)
   17. MNAO WG -considering on focus areas to in facilitating Delivering E release priority & plan for F (rprakash, 14:53:18)
   18. any more topics? (rprakash, 14:54:20)

Action items

1. (none)

People present (lines said)

1. rprakash (47)
2. uli-k (33)
3. aimeeu (7)
4. collabot` (4)
5. bryan_att (0)