This wiki will describe the desired target architecture for designing and creating generic control loops.

ONAP Platform Configuration - Day 0

Assumption: Install Openstack onto your VM and then installed ONAP via OOM or Heat

  1. Setup A&AI with the following information that describes your network. Use curl and/or ESR to do this work. Q: Should this be done via SDC?
    1. Cloud regions
    2. Zones (optional)
    3. Complex (optional)
    4. Service Type(s)


ONAP Platform Service Design

  1. Use SDC to build vendor software product
  2. Use SDC to build the service using vendor software product(s)
  3. If using APPC as controller, then goto APPC CDT to build VNF Templates
    1. Uses VNF Type and Template Identifier that is generated by SDC
    2. Can specify user parameters for performing an Operation
  4. Use CLAMP to build the control loop for the service
  5. Use SDC to distribute the models


ONAP Platform Onboard a Customer

  1. Use A&AI to onboard customer(s)


ONAP Platform - Instantiate Service

  1. Use VID to instantiate the Service Instance for the Customer
    1. Service Instance → creates ServiceID
  2. Use Postman or ODL GUI (slow to initialize) to pre-load SDNC using ServiceID
    1. Set the vnf-name (SDNC) - but VID names this the vf-module-name
      1. ISSUE: This vnf-name has to be known to control loop applications somehow
  3. Use VID to do the following
    1. VNF Instance → creates VNFID
    2. VF Modules


ONAP Control Loop Runtime Processing





  • No labels

1 Comment

  1. In the Control Loop meeting today, Oct. 24, 2018, for Dublin release there was talk of a TOSCA CSAR package distributed by SDC that contains everything related to a Control Loop Service model.

    Is it correct to think of this Control Loop Service CSAR package as very similar to the main CSAR package that SDC distributes for ONAP Network Service models, with these distinctions:

    • ONAP Network Service model CSAR contains VNF Descriptors and VNF related Artifacts needed to create and manage Network Service instances (by VID).
    • Control Loop Service model CSAR contains micro-Service Blueprints, micro-Service related Artifacts and configuration/operation Policy models needed to create and manage Control Loop Service instances (by CLAMP).

    Is this correct?