#opnfv-mano: mano-wg

Meeting started by rprakash at 15:00:37 UTC (full logs).

Meeting summary

    1. rprakash (rprakash, 15:00:53)

  2. Best Practices (rprakash, 15:09:55)
    1. https://wiki.opnfv.org/display/mano/Best+Practices (rprakash, 15:10:03)
    2. OpenBaton offers Packages for VNFM for gVNFM as well Juju (rprakash, 15:16:09)
    3. Docker based packaging is also being connsidered (rprakash, 15:16:38)
    4. bootsrap for NFVO+VNFM will be from OpenBaton and Integration with OPNFV VIM will be using JOID Installer + Scenario? (rprakash, 15:18:30)
    5. Scnario for OPEN-O os-openo-nofaeture-ha with compass & JOID (rprakash, 15:19:53)
    6. AGREED: Priority 1 is Integrating MANO Stack Compaonents over OPNFV VIM (rprakash, 15:23:40)
    7. Catalog and Priority for integrating VNF over the MANO Integration platform (rprakash, 15:35:20)
    8. https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html (rprakash, 15:35:32)
    9. 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, 15:36:04)
    10. MANO SB APIs Or-Vi is most mature at this time to consider (rprakash, 15:43:23)
    11. Close loop monitoring is a possible candidate for OPEN-O with Doctor Project' (rprakash, 15:45:45)
    12. VNFD use of Simaple TOSCA YAML file is norm for most MANO projects (rprakash, 15:47:13)
    13. Define first the metadata and content like using Blueprint etc before a fomrat can be made or agreed (rprakash, 15:50:02)
    14. How you create package is through SDK which is being proposed by both OpenBaton and Open-O (rprakash, 15:51:55)

  3. Architecture from MANO side (rprakash, 15:56:45)
    1. https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111&preview=/6827111/10289542/MANO%20WG%20Priority-Directions-D2Eand%20Architetcure-v1.21.pptx (rprakash, 16:02:02)
    2. reviewe both E-Relase Priority and Architecture inputs to Tapio/TSC (rprakash, 16:02:29)
    3. ACTION: to follow up E-Release Priority by email (rprakash, 16:02:56)


Meeting ended at 16:03:03 UTC (full logs).

Action items

  1. to follow up E-Release Priority by email


People present (lines said)

  1. rprakash (25)
  2. collabot` (3)


Generated by MeetBot 0.1.4.