Thanks Eric for adding more context around the OVP testing. To further expound on the testing, there are 3 classes of testing:
1. Compliance - is the VNF packaged to the standards that will allow it to integrated in the defined infrastructure? 2. Verification - does the VNF behave correctly? (onboarding, lifecycle, orchestration, change mgmt, etc) 3. Performance - how does the VNF perform against industry benchmarks? #1 does not require a stood-up instance. #2 and #3 do... Since #1 is available today, we are now looking to #2 for the OVP badging - hence bringing ONAP deployment more into the workstream for VNF vendors. On Thu, Apr 18, 2019 at 1:37 PM Eric Debeau <eric.deb...@orange.com> wrote: > Hello Jim > > > > « Ease of Deployment » is important and OOM team (with the community) is > working hard to ease the deployment. > > > > The first OVP Program step is only to validate the VNF package/descriptor. > There is no need to deploy full ONAP for that. > > VNF Vendor just need to run VVP or VNFSDK to check their > package/descriptor. It is an easy task. > > We have developed a portal for VVP and DT also proposed their portal to > help any vendor to test their VNF using Heat descriptor. > > > > To fully test VNF within ONAP and to check the full onboarding, > deployment, configuration and closed-loop, they need to deploy a full ONAP. > > I believe that all ‘main’ vendors have deployed ONAP in their labs. > > > > I agree that we must help ‘small’ VNF vendors with ONAP community > solutions to avoid them to deploy a full ONAP or we must provide more > adapted ONAP deployment to test their VNF managed by ONAP. That is why I > advocated from Day0 to get a small footprint for ONAP. Within OOM project, > we defined an override file to only deploy a subset of ONAP components to > enable on-boarding and deployment. > > > > In addition, Orange OpenLab welcomes different VNF vendor that can test > their VNF. > > > > Best Regards > > > > Eric > > > > *De :* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *De la > part de* Jim Baker > *Envoyé :* jeudi 18 avril 2019 20:04 > *À :* onap-tsc > *Objet :* [onap-tsc] ONAP deployment baseline > > > > Greeting ONAP TSC, > > One of my areas of contribution within LFN is on the OVP program. As the > OVP program seeks to attract a marketplace of verified VNFs, the developers > of the VNFs have the task of completing testing using ONAP. Before they can > begin the self-testing work required by the OVP, they need to have deployed > ONAP and OpenStack before that > <https://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/onap_heat.html#openstack> > ... > > > > My question is: Is "ease of install" a system attribute that we have > baselined AND improve upon? > > > > My desired outcome from raising this question is to accurately state for > VNF developers an estimation of the process time required currently to > deploy ONAP AND to understand the interest in the community of investing in > "ease of deployment" to improve the end-user experience. > > > > Thanks for sharing your thoughts! > > > > -- > > Jim Baker > > Linux Foundation Networking - Technical Program Manager > > mobile: +1 970 227 6007 > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > > -- Jim Baker Linux Foundation Networking - Technical Program Manager mobile: +1 970 227 6007 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4873): https://lists.onap.org/g/onap-tsc/message/4873 Mute This Topic: https://lists.onap.org/mt/31234067/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
