ONAP SDC - Model driven design
- 3. Vendor lock-in Coupling of SW with HW Long TTM Manually built Passively operated Low-to-no reusability How can we make a leaner more agile networks ? Open Source De-coupling of SW and HW Short TTM: agility Automatically built Built-in network intelligent Reusability is the key. Design with Lego pieces not with snowflakes.
- 4. Deploy i.e., Local/geo-redundancy ? Both ? Which cloud environment ? Orchestrate i.e., Can we use a generic orchestration flow ? Do we need anything specific Connect i.e., Which type of networks to use ? Do we need IP addresses ? V4 ? 6 ? How many ? Configure i.e., Generic VNF configuration & specific VNF configuration like FW rules.. Monitor i.e., Based on which standard ? SNMP ? Syslog ? Other ? Do we what to get an alarm? Operate & Maintain i.e., How do we handle upgrades ? Fixes, patches ? How do we handle scale in/out ? Delete ? Automate as much as you can. Multi-dimensional design was always our mission.
- 5. Rely on standards. Model-driven design • Well-defined “atoms”. i.e., what is a port ? what is a network ? • Atoms build molecules, molecules build even more complex molecules (organisms). VFCVFC VFC VNF Capabilities Requirements Properties VNFVNF VNF Service Capabilities Requirements Properties ServiceService Service CS N A reusable network starts from the bottom.
- 6. Use abstractions - well-defined model’s “first-class citizens”: VFC, VL, CP, VNF, Service, etc. VNF vFW vR vWANx vMME type CP FN PA J vendor DF#1 DF#2 DF#3 DF#3 deployment Abstract!
- 7. Unlock new ways to design the network and control runtime execution. CP extCP intCP extCP _#1 extCP _#2 type Deployment A B C A B C ~~ E, D A B C ~~ X, Y A B C ~~ X, Y ~~ a, b A B C ~~ X, Y ~~ c, d Abstract!
- 8. VNFOnboarding Automate onboarding of software-based network functions and applications in large quantities and with rapid speed. Catalog Single master catalog, maintaining E2E Models for run-time metadata- driven execution. Maximize model-driven and minimize code changes to the operating platform. Design Compose, deploy, and operationalize services with shareable and reusable functional components. Flexibility is the key. ONAP Service Design & Creation (SDC) VNFOnboarding Catalog Design
- 9. Create Vendor Software Product (VSP): • Deployment artifacts, i.e., HEAT • License artifacts • Images • Monitoring artifacts, i.e., SNMP- MIB • Configuration artifacts • Documentation • … Validation • Standard validation • Syntax validation • Security checks. • ... Enrichment with: • Operational requirements • Deployment requirements • Dependencies • Functional and non-functional requirements • Build license model Create Validate Enrich VNF- ready VNF Onboarding
- 10. Let’s start.