Some inputs - We should categorize the technical success of the platform in tangible ways. Some suggestions are provided below for further discussion.
We can perhaps institute a process of arriving at a Net Promoter Score (NPS) for each of these aspects - 1. Operational Agility Metrics The ability for the community to BUILD-TEST-DEPLOY the ONAP platform is a key technical aspect. Hence, the automated CI/CD process would be a key measure of technical success - as it will help in greater adoption and use of ONAP. 2. Extensibility Metrics (APIs). The ONAP Platform will need to integrate with 3rd party systems - such as OSS, BSS and Carrier-specific analytics platforms to realize advanced use cases. This will require a rich set of APIs to be exposed from the ONAP Platform for 3rd party consumption. Hence, how rich is our REST API set would determine how seamlessly ONAP integrates in diverse carrier and vendor ecosystems. Each subsystem of ONAP should have a documented API library for enabling these integrations, which can be exposed via the API gateway design pattern. 3. Performance Metrics (Scaling) The ONAP platform needs to scale massively - depending upon the scale of the NFVI it is managing and the number of VIMs involved. We should discuss and arrive at a set of scalability numbers for all the platform components - which can give a clear message to the larger community that the platform is scalable and "Carrier Grade". 4. ONAP Certifications and Inter-op Ecosystem We must have an aggressive program with targets to "certify" vendor products and "carrier networks" to be ONAP ready. This program can perhaps be run quarter on quarter through the open labs project. Larger the "certified" ecosystem of vendors and carriers - better the platform's technical success. 5. Quantitative Aspects Based on the discussion below, I suggest the following quantitative measures which can be visualized on the ONAP website - a. Lines of code b. Number of commits c. Downloads (Binary Distribution of ONAP) d. Checkouts (Source repo wise) e. Community Comments (representing a vibrant community) f. Number nightly builds through the CD process (which would increase with each day) g. Others? Regards Aayush From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Stephen Terrill Sent: 14 September 2017 19:29 To: GILBERT, MAZIN E (MAZIN E); onap-disc...@lists.onap.org; onap-tsc@lists.onap.org P Subject: Re: [onap-discuss] ONAP TSC measures of success Hi, The metrics of course depend on what we want to promote and the message related to this. The Health of the community is probably a good one - and this could be worth looking at: https://wiki.linuxfoundation.org/chaoss/metrics Regarding LoC - is more or less better really? i.e. you can have many LoC that don't do much, or less that does a lot .... It's an easy metric and its there, but its questionable the message that you really get from it. BR, Steve From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: 13 September 2017 18:56 To: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> P <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: [onap-discuss] ONAP TSC measures of success Dear ONAP Community, I want to start an email dialog which we will follow up in our Paris meeting on technical measures of success of the ONAP platform. What measures we should track and make publicly visible in PR events? I know LOC has been used already. This seems like one of 2-3 other measures we should be tracking. Those measures should be agnostic to any particular release and publicly recognized. Please share your thoughts and ideas. thanks! Mazin "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
