Network Slice Examples
This page contains some examples used during the development of the Network Slice Manager in roder to prove its features.
Concept to show: A Network Slice is a set of one or more NSs. NST File
Description: Composed by only one NS without any assigned SLA or endpoints, there are no VLDs (not necessary) or any other section to configure.
Procedure: Upload and instantiate one time the previous NST file.
Result: An instantiation of the used service which has 3 VNFs linked among them.
Concept to show: Network Service Composition within the Network Slice.
NST Description: Composed by three equal NSs without any assigned SLA or endpoints, there are five VLDs to interconnect the three NSs. NST file
Procedure: Upload and instantiate one time the previous NST file.
Result: Here you can see one slice instantiation which mean a set of 9 VNFs (3 per NS) linked among them. If you acces into the VIM and look for the networks (VLDs within the NST), there will be more than just five links due to the internal connections inside the NSs to interconnect the VNFs composing the NSs.
Concept to show: Sharing NSs among multiple Network Slices.
NST Description: Composed by three equal NSs without any assigned SLA or endpoints, there are five VLDs to interconnect the three NSs. NST File
Procedure: Upload and instantiate twice the previous NST one time after the other.
Result: Here you can see how instead of having 18 VNFs (9 per each slice), there should be only 15VNFs because one of the 3 NSs composing the NST is shared and so, not instantiated when the second slice is requested.
Concepts to show (they are independent one from each other):
- It is possible to define a specific endpoint to assign to the NS in order to be used for a specific service like a public IP address where users might connect to get a Service. Further information in tng-sp-ia-wtapi.
- In order to give an initial idea of a Quality of Service at the Network Slice level, it is possible to assign an SLA (must be previously created in SONATA SP). This can be assigned manually when the NST is created (copy the uuid of the sSLA from portal and paste it into the selected nsr, copying the uuid/name to the "sla-ref"/"sla-name" keys). Further information on SLAs, check the tng-sla-mgmt webpage.
NST Description: Composed by only one NS with an SLA and endpoints assigned, there are no VLDs (not necessary) or any other section to configure. You can use any of the following NST files:
Author's INFO: There are two more NST files (comm_pilot_SILVER_nst.json, comm_pilot_nst_silver.yaml) for this example within the folder where the previous two are, their structure is exactly the same, only the SLA assigned in our tests and the endpoints change.
Procedure: Upload and instantiate one time the previous NST one time after the other.
Result: Here you will see a simple slice with one single NS but the assigned IP address should be the one defined within the NST. Please change the uuid of the "location" fields with the right one.