...
Step 4. OOF → SO - Return the target <cloud owner, cloud region> for the Service Instance + deployment-intent per vnfc (code changes in OOF for R3)
OOF
...
↔
...
SO
...
API
...
extension
...
-
...
aligned
...
to
...
the
...
OOF/SO
...
API
...
defined
...
by SO
...
...
...
Design to
...
minimize
...
the
...
terminology
...
set. The data between OOF to SO and SO to MC is identical -- details of the API are in section 5.
Step 5. SO → MC - Deploy VNF template in the target <cloud owner, cloud region> for the Service Instance (code changes in Multi-Cloud for R3)
...