Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Date 

 

Attendees

Bob Papa

Yuriy Malakov

Byung-Woo Jun

Ciaran Johnston


Discussion Items

Item

Who

Notes

Agenda
Bob Papa

The purpose of the meeting was to have each group the has done some sort of ONAP Model Driven/Enabled in the past year to explain their view


  • Record Meeting
  • CDS overview
  • Set up next session --- ETSI modeling - presenter : Byung -Woo Jun


Recording

Contact Bob Papa for recording 

CDS Overview

(Design Time) 

Yuriy Malakov   
  • Yuriy's overview will be a review of a Use case that they have been working on
  • CDS documentation can be found on the CDS wiki page under Modeling concepts :
  • CDS Main functionality
    • Automated Resource Resolution Engine
    • Config generator & Config Download engine
    • Based on a TOSCA package called CBA (Controller Blueprint Archive)      
      • Enables provisioning and configurations
      • Contains folders and files
  • Review of Design Time
    • Resource Resolution is based on Data Dictionary
      • Defines the name of Resource
      • Defines on how to resolve the resource
        • Types of: Input, Rest, SQL , etc…
      • Catalog of Data Dictionary Attributes can be grouped into Libraries
        • Attributes entries can be built up over time
        • Attribs should be re-usable across services
        • You can have one or multiple Libraries
        • Attributes will be used for mapping
      • A GUI is being worked on for Frankfort to allow a user friendly way to create a data dictionary entry
      • Data Dictionary is global and should be used across Services
    • Templates
      • Each template has a mapping file
      • Mapping file is used to resolve resources in the template
      • It is possible to have multiple template/mapping files
    • Scripting is supported
      • Ansible
      • Python
      • Etc….
    • Complex functions can be done with scripts
    • Supports Workflows - Tosca doc Chapter 7.3
      • Config-assign
      • Config-deploy
      • Resolves assignments
      • Can generate an AID to provide to clients
      • Workflow Engine
        • TOSCA imperative Workflow
        • DG workflow (deprecated in Frankfort)
    • SDC distributes CBA file as artifacts are done today
    • LCM actions using CDS is targeted for Frankfort ( Bell Canada and E//)
    • UI - Targeted for Frankfort
      • Need UI resources
      • Reviewed some mock-up screens
        • CBA package creation - 2 modes
        • Designer mode
        • Scripting mode (for developers)
        • Can import files
    • CDS Integration with Policy in Frankfort
      • Plan for a Model Driven with Policy in 2020


Next Steps All 

Next Meeting - December 16 - 10:00 Eastern Time - ETSI Modeling Overview ( Byung-Woo)

(Meeting was moved to January 2020) 

Next year - Model Driven Policy Overview

 


  • No labels