NST Selection

Interfaces

1. NST selection Request
   1. Input: Service profiler parameters.

      {

      "requestInfo":{

      "transactionId":"c86b3019-39f4-4cd3-b847-b22afe9f36dc",

      "requestId":"c86b3019-39f4-4cd3-b847-b22afe9f36dc",

      "sourceId":"so",

      "timeout":600,

      "callbackUrl":"http://0.0.0.0:9000/callback/"

      },

      "serviceProfile":{

      "serviceProfileParameters":{

      "latency":20,

      "areaTrafficCapDL" : 10000,

      "coverageAreaTAList" : "India"
      }

      }

      }

2. Fetch Optimization policies
   1. vnfPolicy - it will identify the inventoryProvider and inventoryType - Forms demand policy.
   2. Attribute policy - for storing the serviceprofileparameters and its value as attribute - value pair- Constraint policy.
   3. QueryPolicy -  Its used to query the serviceprofileparameters from the input so that it can be added as a value to the attribute.
3. NST selection request - HAS
   1. Demand: NST
   2. Constraint: Attribute policy for matching whether nst templates have these attributes.
4. Fetch NST metadata from AAI
   
   1. Output: List of all NSTs metadata .
5. Fetch NST candidate from SDC
   1. Input: NST metadata
   2. Output: List of NST candidates matching the metadata
6. Run optimization  - taking attribute constraint, the candidates are filtered out matching the attributes.
7. Solution list is formed
   
   1. Solution List. Solution object have nst candidates matching the input service profile params.

NST Template example (Candidate)