1. UUI Configuration
...
Insert ORCHESTRATION_URI into service_recipe, SERVICE_MODEL_UUID replaced by CST.ModelId.
|
Insert ORCHESTRATION_URI into service_recipe, SERVICE_MODEL_UUID is ServiceProfile.ModelId
|
4. A&AI Configuration
If the service distribution to A&AI failed, like the picture shows bellow:
...
Add 'ServiceProfile' and 'NSTAR' model to A&AI through postman.(ServiceProfile/NSTAR Model Id and Invariant Id can be find on SDC page.)
...
Elite soft json viewer | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
{ "model-invariant-id": "73e7212d-a340-4626-a050-a9d07b96e146", "model-type": "resource", "model-vers": { "model-ver": [ { "model-version-id": "7d33bac2-7372-45d6-89a3-d8b2ecf16f87", "model-name": "NSTAR", "model-version": "1.0" } ] } } |
Create Customer and service-subscription
Create customer(5GCustomer) and service-subscription(5G) in AAI.
5. OOF Configuration
...
Example of these three policies can be found in this link Policy Models and Sample policies - NSI selection
6. ESR Configuration
Configure Simulator by Esr
...
theme | Eclipse |
---|
...
6. Internal CORE NSSMF Simulator
...
First, pull down the simulator image from public docker hub.
|
Step 2. Start the simulator container(s)
After compiling the pnc-simulator image locally or fetching the docker image from remote registry, execute the command below to start the container:
|
|
For demonstration purposes, two domain controllers are required, in our case we use 18181 as SERVER_PORT for domain1 and 18182 for domain2.
After starting the container, you should be able to verify the running container by:
|
Step 3. Initialize the simulator(s)
...
To initialize the simulator for each domain:
|
For demonstration purposes, two domain controllers are required, both need to be properly launched and initialized. The initialization payloads are attached below.
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
curl -k -X PUT "https://AAI:AAI@<worker-vmIp>:30233/aai/v23/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/ff9ef162-951d-4e14-9ce6-b4fa0adf896b" \ -H 'Accept: application/json' \ -H 'X-FromAppId: AAI' \ -H 'X-TransactionId: 1' \ -H 'Content-Type: application/json' \ -d '{ "thirdparty-sdnc-id":"ff9ef162-951d-4e14-9ce6-b4fa0adf896b", "location": "edge", "product-name": "TSDN", "esr-system-info-list":{"esr-system-info":[{ "esr-system-info-id": "7c29b9df-feef-4fa7-b56d-3e39f5ef4a90", "system-name": "sdnc2", "vendor": "HUAWEI", "type": "WAN", "version": "v1.0", "service-url": "http://<simulator-ip>:<simulator-port>", "user-name": "onos", "password": "rocks", "system-type": "thirdparty_SDNC", "protocol": "restconf" }]} }' |
8. UUI operations (Creating communication service, Activation)
...
There are no changes in the UI for the NSMF based TN slices. It is same as the usual operations. The UUI operation details can be found here.
UI Operation Guidance for 5G Network Slicing