PPT-ONAP, MEF, TM Forum Coordiation

Andy Mayer PhD representing MEF and TM Forum am803uattcom Open Collaboration MEF LSO Committee at a Glance Project Editor Kickoff CfC1 CfC2 CfC3 LB Published LSO RA Phase 2 SOF. John D’Elia. V0.8. DRAFT. Background. Multiple Verizon teams require access to management and orchestration applications. A role-based access control (RBAC) mechanism is mandatory in order to constrain users to only the application functionality and data associated with their job responsibilities. Chris Donley. What is a project. 2. A project is:. long . term endeavor. setup to deliver features . across multiple . releases. Single entity solely responsible for 1+ repos. Defined scope. Led by PTL and committers with expertise in the relevant areas. ONAP Architecture Chair. 2. Analytics Applications. Analytics Application use cases. Infrastructure analytics (Hypervisor, Base OS and HW metrics). Application level analytics (Example: CDN, RAN, EPC, IMS, IOT-Gateway . Shitao. li. Namespace . suggestion from OASIS . TOSCA. 2017-11-02 - TOSCA . Namespacing. Explained - . Draft.pptx. There are four important . keynames. need to take into consideration:. . tosca_definitions_version. Puzhavakath. Narayanan, Vikas Varma, Swaminathan S, Krishna Moorthy. Presenters: Shankaranarayanan . Puzhavakath. Narayanan & Krishna Moorthy. OOF: Overview & Hands-on Session. October 14, 2020. StarlingX. Bin Yang. Senior Solutions Architect, Wind River. Agena. CNF Orchestration Overview. Comprehensive . Workflow. Overview. A demo CNF validated over . StarlingX. 3.0. Detail guide to deploy ONAP over . Participants:. . CMCC,. . Wipro,. . Huawei,. . AT&T,. . Deutsche Telecom, TIM, QCT,. . Amdocs, Tech Mahindra,. . Reliance. . Jio. ,. . Tencent,. . China. . Telecom. Authors: Lin. . Meng (CMCC),. SMO-related projects in OSC and ONAP. June xx, 2023. Incorporating ideas and support from several people, including:. Andrea . Buldorini. , . Rittwik. Jana, John Keeney, David Kinsey, . Seshu. . Mudiganti. The customer wants Telephony service. ONAP. Telephony_model_1:. {. techno : . voip. vnf_vendor.  : . vendorA. }. Telephony_model_2 :. {. techno: . voip. vnf_vendor. : . vendorB. }. Telephony_model_3:. - Draft 0.4. . ONAP. The Linux Foundation. This deck will be used for generic, industry talks/keynotes => ONS, LFN Webinar, press release,. etc. and re-used/re-adjusted by ourselves ;-). Slides should be visual, punchlines – see Marketing Honolulu deck. Best of both worlds. Drivers. Latency/ Physics. Bandwidth/ Economics. Context/ Proximity. Privacy/ Legal. Geo Distributed Computing trend. 2. WAN. Public/ Private Cloud. m. S4. m. S4. m. S3. m. S2. m. @twitter. ONAP DOC Team | . 2021 February LFN Developer & Testing Forum. intersphinx. linking & submodules . achievements. got rid of docs submodules. introduced . intersphinx. linking to generate automatic links to the documentation of objects in other ONAP projects. Gil . Bullard,. AT&T. Proposal Summary. Application-level configuration and LCM is the functionality that is peculiar to ONAP, outside of the scope of ETSI MANO.. ONAP should provide two Service Provider options with respect to application level . November 7 , 2022. 2. Agenda. Short introduction to ONAP - Magnus Buhrgard (ONAP technical community coordinator for NW Mgmt). Two ONAP areas: 1) Intent Based Networks   2) Modelling and packaging of Network Functions for K8s .