How to track architecture requirements ONAP Dublin Release

How to track architecture requirements ONAP Dublin Release Architecture F 2 F meeting Montreal, 29 -31 st October, 2018

Introduction - Good discussion - Some requirements start to be identified - Some very concrete - Some still aspirational. - Note: Recommendations seen as requirements - Some have topics that need to be further discussed to be included in dublin - Then there are some decisions to make Subject 1 Subject 2 Subject 3 Subject 4 Subject 5 Arch Reqs Approach to collecting requirements Arch Actual ONAP – Dublin Release Use Case Security 2

Approach? Architectural Requirement Subject Functional Description, project impacts (API, functionality), priority , deliverable, testing Architectural Requirement Functional Description, project impacts (API, functionality), priority , deliverable, testing We need to have a draft at the close of this meeting I need the presents to fill it in. 3

Subjects? (treat as examples) • Edge orchestration • Modularity - SDC modularity - Controller modularity • • CSP? PNF handling Network Slicing ETSI Alignment Service mesh & the like, Dublin step Orchestration of cloud native VNFs Data Lake - Still some feedback / alignment 4

Example Questions to be solved • Internal Service Representation 5

Approach? y Stor Architectural Requirement Subject EPIC Functional Description, project impacts (API, functionality), priority , deliverable, testing Architectural Requirement Functional Description, project impacts (API, functionality), priority , deliverable, testing We need to have a draft at the close of this meeting I need the presents to fill it in. 6

s