Dear ONAP TSC, Dear ONAP Community,
I do not know if you have realized but yesterday was our 5th ONAP Anniversary. Over the past few years, we have changed the Industry, promoting forward thinking, influencing SDOs. Together we have also overcome a lot of technical, process and human challenges. Today I feel sad for our ONAP Community. We have not yet been able to reach an agreement concerning our . I have listened to the different points of view. I value all the constructive feedback that has been shared through the different forums. Now I want to share a couple of thoughts * Any contribution to the ONAP Community is always welcome – Nothing in our ONAP Chart prevents anybody from working on a POC<https://urldefense.com/v3/__https:/protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-14178800e67c697c&q=1&e=c9d84d44-6d77-467e-a9e0-247729f9fec4&u=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2F*2Fprotect2.fireeye.com*2Fv1*2Furl*3Fk*3D31323334-501d5122-313273af-454445555731-47eae0e48b07533a*26q*3D1*26e*3Db2cf6e3a-2488-48f0-8a6f-98ac2ad452fa*26u*3Dhttps*2A3A*2A2F*2A2Fwiki.onap.org*2A2Fdisplay*2A2FDW*2A2FPOC*2A2Bdefinition__*3BJSUlJSUlJQ*21*21BhdT*21in_R0py6w-a2n-QNRNzcHw4F7SqGR-CEz8FCa4b9Q1x5wy5yyIGlry8BQ0Pr-WVAFjWFPSpFikVdRWOnJqS7Cs9mgehGHZptia4*24__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!BhdT!lWmaL60jgltn3QGHep0fX6NlWzJoOych3li-bizhAbGRvAzhQSeu_yct2HTqkoHu5QfKGaHDYuCcVytHF48gMVlRx278qYKAtRE$> * SDOs have not yet explored all the technical domains, ONAP should remain inspirational and should keep exploring any ‘unknown’ territory * Divergent thinking is a method that is used to come up with creative ideas I want to recommend how we can move forward as a TEAM: * We should pursue the implementation of the ASD Model POC, that will bring us one step forward into our “Cloud Native” Architecture * We should continue the dialogue in the CNF Taskforce in collaboration with the Modeling Subcommittee to pursue the best solution in alignment of what has already been done * We should share our POC findings to ETSI – so they can consider them (or not) as part of their Cloud Native Modeling standard definition * We should unify our voting process in alignment with the ONAP TSC Chart to prevent any future confusion I remain confident that we will get over this together, like we always did Best regards, Catherine Catherine Lefèvre AVP Software Development & Engineering AT&T Technology Services – Network Systems Common Platform & Services ONAP TSC Chair [cid:[email protected]] Phone: +32 2 418 49 22 Mobile: +32 475 77 36 73 [email protected]<mailto:[email protected]> TEXTING and DRIVING… It Can Wait AT&T BUROGEST OFFICE PARK SA Avenue des Dessus-de-Lives, 2 5101 Loyers (Namur) Belgium [cid:[email protected]] NOTE: This email (or its attachments) contains information belonging to the sender, which may be confidential. proprietary and/or legally privileged. The information is intended only for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient, you are hereby notified that any disclosure, distribution or taking of any action in reliance on the content of this is strictly forbidden. If you have received this e-mail in error please immediately notify the sender identified above. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8445): https://lists.onap.org/g/onap-tsc/message/8445 Mute This Topic: https://lists.onap.org/mt/89363092/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
