Hi all, There was asking for simplifying the MANO write-up for Release D at TSC today as the table for MANO Integration had too many points listed. Danube priorities<https://wiki.opnfv.org/display/SWREL/Danube+priorities?src=mail&src.mail.timestamp=1484639012819&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>
Suggest the following simplification to message MANO Integration Pilot Integration Pilot MANO stack Integration pilot in Danube requires identifying ways and means to enable MANO modules to integrate with OPNFV VIM. An effort is made in Danube to add nfvo and vnf artifacts through upstream OPEN-O and OpenBaton and Juju over OPNFV VIM and test sample vnf(vIMS) through functest This can be cleaned for consistency across different stacks in future releases Actual details of consistency of MANO stack integration we differ to later release as Bryan Sullivan has listed for release E. e.g. of consistency could be Service Catalog addition for On-boarding, using Registration, Health check and using Keystone v3 (AAA), Hierarchical Catalog etc. If any of the MANO community participants want to reword it to reflect the view point please feel free to respond. Thanks Prakash Prakash Ramchandran [logo_huawei] R&D USA FutureWei Technologies, Inc Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com> Work: +1 (408) 330-5489 Mobile: +1 (408) 406-5810 2330 Central Expy, Santa Clara, CA 95050, USA
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
