Issues
- SO - VFC interfaceONAPARC-414Resolved issue: ONAPARC-414Former user
- Dublin Architecture Review: PortalONAPARC-412Resolved issue: ONAPARC-412Former user
- Dublin Architecture Review: CLAMPONAPARC-404Resolved issue: ONAPARC-404Former user
- Documenting ONAP Architecture - Architecture principlesONAPARC-401Resolved issue: ONAPARC-401Former user
- Documenting ONAP architecture - Information flowsONAPARC-400Former user
- ONAP Current Architecture DocumentationONAPARC-274Resolved issue: ONAPARC-274Former user
6 of 6
SO - VFC interface
Done
Description
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Labels
Priority
High
Details
Details
Assignee
Former user
Former user(Deactivated)
Reporter
Former user
Former user(Deactivated)Labels
Priority
HighCreated February 26, 2019 at 6:51 PM
Updated February 26, 2019 at 6:52 PM
Resolved February 26, 2019 at 6:52 PM
Activity
Show:
2019-02-26 ArchCom
Viswa presented: https://wiki.onap.org/pages/viewpage.action?pageId=58229331
It is a step towards a SO plug-in for SOL005 where its currently focussed on aligning the interface between SO-VFC to NS-LCM of SOL005.
The discussion lead to the full SOL005 plug-in to SO, which is related to the orchestration scenarios. There were questions in the chat:
I expect that SO would register the Service in A&AI. Homing and assignments are probably in the domain of the NFVO. Perhaps with hats from the parameters.
^hats^hints
From Jimmy Forsyth (AT&T) to Everyone: 05:59 PM
Are you requesting a new NFVO type in the AAI model?
From Gil Bullard (AT&T) to Everyone: 06:00 PM
@Fred - Are you assuming that there is no larger E2E Serivce context that could constrain the external connection points on the NS?
From Fernando (Fred) Oliveira to Everyone: 06:01 PM
@Gil - No the external end points would still be assigned by SO.
And passed as parameters.
This is just an interim milestone
From Gil Bullard (AT&T) to Everyone: 06:01 PM
@ Fred, then I am not following your comment "Homing and assignments are probably in the domain of the NFVO."
From Avi Chapnick to Everyone: 06:01 PM
I dont think external assignments/homing are being handled for VFC services
From Fernando (Fred) Oliveira to Everyone: 06:02 PM
@Gil, Sorry, I was jumping to the VNF assignments.
I agree on the Service end point assignments.
From Gil Bullard (AT&T) to Everyone: 06:03 PM
@Fred, from ONAP's perspective, I would think the NS would look like a "Resource" within the larger E2E ONAP Service
and in the E2E ONAP Service there may be other Resources: VNFs, PNFs, whatever that interact with that NS as a "black box"
ONAP should be the one that does homing and assignments for each of those "Resources" (VNFs, PNFs, NSs)
From Fernando (Fred) Oliveira to Everyone: 06:03 PM
@Fred - Perhaps. Maybe eventually mapped to an allotted resource in a larger Service
From Gil Bullard (AT&T) to Everyone: 06:04 PM
If you want to leverage that functionality of ONAP then we need to be careful which of the two ONAP Data models you assume on the north side of the SOL005 adaptor
From Fernando (Fred) Oliveira to Everyone: 06:04 PM
@Gil. Sorry, Im’m in 2 other meetings simultaneously.