Hi all,
Here is quick summary from IRC will update Wiki after we have E-Release 
discussions through emails by end of week.
Thanks
Prakash
Meeting summary

  1.
     *   rprakash 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-5>,
 15:00:53)
Agenda Bashing

  1.  Best Practices 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-8>,
 15:09:55)
     *   https://wiki.opnfv.org/display/mano/Best+Practices 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-9>,
 15:10:03)
     *   OpenBaton offers Packages for VNFM for gVNFM as well Juju 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-11>,
 15:16:09)
     *   Docker based packaging is also being connsidered 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-12>,
 15:16:38)
     *   bootsrap for NFVO+VNFM will be from OpenBaton and Integration with 
OPNFV VIM will be using JOID Installer + Scenario? 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-13>,
 15:18:30)
     *   Scnario for OPEN-O os-openo-nofaeture-ha with compass & JOID 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-14>,
 15:19:53)
     *   AGREED: Priority 1 is Integrating MANO Stack Compaonents over OPNFV 
VIM 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-15>,
 15:23:40)
     *   Catalog and Priority for integrating VNF over the MANO Integration 
platform 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-16>,
 15:35:20)
     *   
https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-17>,
 15:35:32)
     *   VNF should establish its name and context as an Application or 
Component with a path to Application/Component Catalog(Cat.3/Repo). This 
assumes that hierarchy of Catalogues/Repos is Cat.5/Repo5 (Marketplace), 
Cat.4/Repo4 -Service Provider Service Catalog (This is where you onboard 
NS/NSD), Cat.3/Repo3 - Application/Component Catalog (This is where you onboard 
your VNF/VNFD/Packages etc), (Cat2./Repo2) -SDN Controller Catalo 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-18>,
 15:36:04)
     *   MANO SB APIs Or-Vi is most mature at this time to consider 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-19>,
 15:43:23)
     *   Close loop monitoring is a possible candidate for OPEN-O with Doctor 
Project' 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-20>,
 15:45:45)
     *   VNFD use of Simaple TOSCA YAML file is norm for most MANO projects 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-21>,
 15:47:13)
     *   Define first the metadata and content like using Blueprint etc before 
a fomrat can be made or agreed 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-22>,
 15:50:02)
     *   How you create package is through SDK which is being proposed by both 
OpenBaton and Open-O 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-23>,
 15:51:55)


  1.  Architecture from MANO side 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-24>,
 15:56:45)
     *   
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111&preview=/6827111/10289542/MANO%20WG%20Priority-Directions-D2Eand%20Architetcure-v1.21.pptx
 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-25>,
 16:02:02)
     *   reviewe both E-Relase Priority and Architecture inputs to Tapio/TSC 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-26>,
 16:02:29)
     *   ACTION: to follow up E-Release Priority by email 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-27>,
 16:02:56)


Meeting ended at 16:03:03 UTC (full 
logs<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html>).
Action items

  1.  to follow up E-Release Priority by email


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: [email protected]<mailto:[email protected]>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to