Go to start of metadata

Date

 

Attendees

Bob Papa 

Byung-Woo Jun

Andy Mayer

Amir Caduri

Andreas Geissle

SALVATORE RICCI


Discussion Items

Item

Who

Notes

Agenda
Bob Papa

The purpose of the meeting: 

  1. Model Enabled Definition ---   1- 5 bullets describing what does ONAP Model Enabled mean

2.  4 stages of modeling domain  --   How does the 4 stages of Modeling (Onboarding, Design-Time, Service Instantiation, Service Lifecycle Management) fit into a Model Enabled process.  

Definition Discussion All 
  • Model Enabled Definition ---  

Software behavior Is based on information defined in a model. Changing the model will change the behavior of the software system without needing to change the code base.



  • How do the 4 stages of Modeling fit into a Model Enabled definition?

List of what modeling function drives the particular stage of modeling.  

4 stages of modeling domain  --   

  • Onboarding
    • ETSI
    • HEAT
    • TOSCA
    • HELM
  • Design-Time
    • CDS
    • SDC
  • Service Instantiation
    • Current
      • BPMN workflows
      • Directed Graphs
      • OOF
    • Future
      • TOSCA Driven
  • Service Lifecycle Management
    • Current
      • VES descriptors
      • Policy Models for Clamp
      • Policy integration with CDS
 
Next Steps  All 

1)  Provide the Model Enabled definition to the modeling subcommittee.

2) Work with Andy to convert the meeting to an ONAP bridge and add to ONAP calendar. 

3) Continue to define what is used to drive any of the stages of modeling. 

4) Get an update from Seshu on the SO Frankfort POC .

5) Request comments on the Modeling Enabled definition from the Modeling subcommittee.  

6) Send next meeting notice to modeling subcommittee dl.  

  • No labels