2019-011-05

Andrea provided feedback on how we have documented the ONAP architecture in read-the-docs. https://wiki.onap.org/download/attachments/8225716/ONAP_architecture_document_suggestions_Andrea_Visnyei.pptx?api=v2

• important information is hidden inside the more marketing text
• Restructure is required.
• could also reflect that security and deployment could be considered.
• At the moment its part of the developer guide, should it be located in another place.  The users and the developers mayhave different needs when it comes to documentation.
• Avoid release dependant text - put that in the release notes.
• agree to copy to the wiki, andrea can provide initial comments; then we seek volunteers.

2019-02-05 - notes from ONAP Arch weekly meeting (CJ)

• Few comments received. Updated documents provided by Ting for further offline comments in the wiki
• The discussion veered towards what the target ONAP architecture should be vs what ii is today
• The AT&T team wants to make sure that the ONAP documentation take into account the ONAP architecture principles
• Documentation of architecture principles
  • Is it likely in an open source community to expect alignment with all requirements – e.g. how to measure microservices compliance?
  • Purpose of documentation is to enable ease of onboarding of new users / developers
• “Black-box” picture (Ciaran's picture):
  • Considered “old-school” integration architecture picture – needs to be described in terms of capabilities not implementations
  • Are we documenting the current “tight coupling” or the wanted loose coupling and service based, or both? How do we provide a “wanted approach” for new projects?
• Comments to be provided on updated slidepack uploaded to the wiki

01-05-2019 update - CAH

2019-01-29 Arc Dublin F2F

• Ting presented: https://wiki.onap.org/download/attachments/50202249/ONAP%20Component%20Arch%20Review%20%28SDC%29%201-29-2019.pptx?api=v2
• Need to have an additional higher level slide.
• Slide 8; add the IM or DM

Will follow-up on the next Seccom next week to allow time for people to provide considered input.

2018-10-31 Arc Dublin F2F:

(From https://wiki.onap.org/download/attachments/50202249/Documenting%20the%20ONAP%20Architecture.pptx?api=v2)

we need better documentation for architecture.
2 way split  inward doco that we produce for ourselves and outward facing for everyone else
Document the real Architecture
Multiple Views ( one diagram cannot cover it!)
Functional Architecture = Business Capabilities
Platform Architecture = Outer and Inner Architectures = High Level MSA
Inner :  ONAP Services -  The Microservices that Deliver ONAP Functionality
Outer : ONAP Microservices Platform  - The Platform that Supports the ONAP Services

 Need to come back with the archecture blueprint and way to document it before running off.