2019-07-09 ArchCom:

Principles were presented again. 

Question was raised as to how we use these principles in governing the ONAP architecture

• for new components or changes to existing components we can use these as the basis for evaluating the change
• question of whether we should make a SOC against the principles for existing components so we can understand how to evolve them - not agreed
• Next steps to bring the principles to the TSC for approval and to clarify next steps

 

2019-03-19 ArchCom:

The architecture principles have moved to the wiki: https://wiki.onap.org/display/DW/ONAP+Architecture+Principles  

Vimal walked through the architecture principles.

• in the strucutre picture, add session numbers.
• There was a discussion about seperation between requirements and principles.
• There is a discussion about the next steps.
  • measurable?
  • design rules?
• Suggestion that we follow-up with more detailed sub-topics that break down the principles into more detailed implications
• Comment from Steven Write:  "While this is a nice list of topics, I'm not sure how to interpret it. From the diagram style, I assume it is some sort of mind map, but aside from classifying the topics - I'm not sure why they are classified that way, or how they relate to ONAP. I would point out that "ONAP" is not on the picture. You could probably add ONAP as an adjective to all the boxes EXCEPT for those under scope which probably should refer to VNF or network service?

 

Vimal to call for meetings to review chapter by chapter

 

As part of documenting the ONAP architecture, it was stated that we should document the architecture principles.

ArchCom 2019-02-26:

The architecture principles have moved to the wiki: https://wiki.onap.org/display/DW/ONAP+Architecture+Principles  

Ciaran and Margerate volunteered to review them and Vimal will have an update in 2 weeks.

---

 

ArchCom 2019-02-19

Vimal presented: ------

• Based on the existing pricinples.  He indicated that he welcomed feedback.
• Slide 3:
  • "Standardization" - standard templates should be interpreted as following standards with they apply, or ONAP will define its own approach
  • Remove the term product
  • Clarify the scope of the COMMON information model approach
  • "integration & centralized design studio". some small editorial re-wording
  • in "Vendor & Service agnostic", service needs to be clear.
  • Add examples of what is vendor & service agnostic.
  • There was a question on whether this describes the scope, or whether scope is the right term.  It was indicated thata definition slide as well

• • • Draw inspriation from here: https://onap.readthedocs.io/en/casablanca/guides/onap-developer/architecture/onap-architecture.html
  • Slide 4
    • Ben: three things to think about
      • CAPEX/OPEX reduction
      • Scalability
      • Brings together many vendors equipment scope, so make it multi-vendor environment.
  • Slide 5:
    • add cloud native
  • Slide 6:
    • Use of common services.
  • Overall: add as text to this page:  https://wiki.onap.org/display/DW/ONAP+Architecture+Principles
    **