Bryan and Kumar, I could not locate the email you pointed in my emails so will use directly point link here in https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html
Concretely, My 5 main criteria to deploy a VNF on top of OPNFV are: #1: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 Catalog, (Cat1/Repo1) Image Catalog [Glance for Openstack], Cat.0/Repo0 - Instance Catalog [like HEAT catalog in OpenStack, or] Any Catalogue in OPNFV that shows running Instances', their id, state etc. Note: Cat5 / Marketplace Catalog is external to Service Provider and is part of hosting and can be found in all Markets including OpenStack, OPEN-O, OpenBaton, OSM, openECOM etc. [cid:[email protected]] #2:VNF Should have a list of metadata described either in its package along with Catalogue architecture for identifying explicitly a.Cat.3/repo3 path with list of components/topology/relations in Cat3. and any Scenario for OPNFV VIM Configuration and reference to SDN-C Cat2 if used, Any underlay topology in Cat2/Repo2, And any system images to use in Cat.1/Repo1,and specify default Orchestrator Instance Catalog to use if any or optional ones. #3:The preference would be to use CSAR. tgz or an Orchestrator acceptable formats to avoid conversion at launch . Thus this means we want to ensure that there is a run time specified and will be native to OPNFV MANO Stack #4:The VNF Packages' are signed and have a signature file associated to verify that these are from valid repos and that meet security criterions of OPNFV Security WG and or Badge certifications #5:The LCM of VNF will follow standard configure, init metadata, run, start, pause , snapshot, restart, restore,[optional for now Scale-up, Scale-down, Scale-out, Scale-in], stop, delete metadata, de-configure etc. We will discuss this in MANO WG this tomorrow and will confirm priorities. Bryan too has stated his 5 and would like to get an agreement for Release-E as we are too far into to D to add any of this now. Thanks Prakash 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
