Till Casablanca release, SO acts as both Orchestrator and OSS/BSS System in some usecases. In the role of OSS/BSS System, SO sends the request to VF-C for Network Services LCM. In the Dublin release, VF-C introduces SOL005
...
What usecase to be tested with SOL 005 Flow:
As of the Dublin release, SOL 005 flow will be tested against vCPE usecase. But in further releases the flow will be validated/tested against VoLTE usecasesvFW usecase with SOL004 CSAR.
What other components will be affected SOL 005 Flow:
- UUI: Two new dropdowns will be introduced to select SOL 005 and orchestrator details.
- AAI: New entity in ESR will be introduced to accept NFVO registrations.
- SDC: We tested with vCPE CSARs to check artifacts distributed to SO and there is no change needed in vCPE usecase. Other usecases has to be tested.UUI: Based on the SOL 005 payload required by SO, UUI interfaces invoking SO will be modified.
- SDNC: ????
Prerequisites/ Assumptions:
...
Known Scope:
- The scope of work is limited to NS LCM APIs, so Service Orchestrator (SO) won’t deal with CSAR package onboarding to VFC.
- As all the attributes that SOL005 instantiate request expects are not provided from Usecase UI, so scope of this work is limited to such requests.