Issues
2 of 2
Documenting ONAP architecture - Information flows
Description
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Priority
High
Details
Details
Assignee
Former user
Former user(Deactivated)Reporter
Former user
Former user(Deactivated)Priority
Created February 11, 2019 at 9:37 PM
Updated October 29, 2019 at 1:59 PM
Resolved February 11, 2019 at 9:37 PM
Activity
Show:
This is part of the documentation for the information flows.
ArchCom 2019-08-06. Walked through some of the updates.
For concsistency, neeed another actor added to the SDC comonent description.
Small changes expected then bringing back
ArchCom 2019-05-21
Ben walktrhough the updates to the onboarding flows.
Archcom 2019-05-07
Ben walked through part of : https://wiki.onap.org/display/DW/ARCHCOM%3A+InfoFlow+-+Onboard+Resource+into+SDC+Flow
-
ArchCom 2109-03-26.
Ben went over his slides and his wiki page: https://wiki.onap.org/display/DW/ARCHCOM%3A+InfoFlow+-+SO+Service+Instantiation+Flow
There is a need to have terminology for VNF, Service, etc. (outside this flow)
It was confirmed that the level was the correct level
ArchCom 2019-02-12
Ben Chueng presented link which is the first time that the information flows are described.
It was noted that VFC does not currently recieve information from SDC.
There was a discussion about the PNF CSAR, VNF CSAR, internal SDC CSAR and finally the Service CSAR.
Requested to have the API name