PPT-TOSCA Namespaces suggestion for ONAP
Author : piper | Published Date : 2023-08-31
Shitao li Namespace suggestion from OASIS TOSCA 20171102 TOSCA Namespacing Explained Draftpptx There are four important keynames need to take into consideration
Presentation Embed Code
Download Presentation
Download Presentation The PPT/PDF document "TOSCA Namespaces suggestion for ONAP" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
TOSCA Namespaces suggestion for ONAP: Transcript
Shitao li Namespace suggestion from OASIS TOSCA 20171102 TOSCA Namespacing Explained Draftpptx There are four important keynames need to take into consideration toscadefinitionsversion. targetNamespaceA Axsd targetNamespaceB Bxsd targetNamespaceC schemaLocationAxsd schemaLocationBxsd Cxsd brPage 2br 13 A schema then may be comprised of components from multiple namespaces Thus when a schema is designed the schema designer must decid Documentation. Today’s Agenda. Namespaces – what is a namespace? Why is it important?. Examples of namespace policies. Directories and Directory services. LDAP – lightweight directory access protocol. anatoly.katzman@att.com. R3: Chain of Data Models. “… why . we need an internal DM for what scenario and what benefit? . And why R2+ modeling can’t handle this? . “. ONAP DM. ONAP DM. ONAP DM. 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. Andy Mayer, Ph.D. (representing MEF and TM Forum). am803u@att.com. Open Collaboration. MEF LSO . Committee at a Glance. Project. Editor. Kick-off. CfC1. CfC2. CfC3. LB. Published. LSO RA. Phase 2 SOF. 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 . R6 Frankfurt Use Cases. August 03, 2020 version 3. Benjamin Cheung, PhD. 5G Basics & 5G RAN. Benjamin Cheung, PhD. . 3GPP Release 15, IMT-2020 = . 5G. Virtual and Augmented Reality. Smart City. Geographically spread devices. 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. - 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 .
Download Document
Here is the link to download the presentation.
"TOSCA Namespaces suggestion for ONAP"The content belongs to its owner. You may download and print it for personal use, without modification, and keep all copyright notices. By downloading, you agree to these terms.
Related Documents