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
- 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?
- Cloud regions
- Zones (optional)
- Complex (optional)
- Service Type(s)
ONAP Platform Service Design
- Use SDC to build vendor software product
- Use SDC to build the service using vendor software product(s)
- Use CLAMP to build the control loop for the service
- Use SDC to distribute the models
ONAP Platform Onboard a Customer
- Use A&AI to onboard customer(s)
ONAP Platform - Instantiate Service
- Use VID to instantiate the Service Instance for the Customer
- Service Instance → creates ServiceID
- Use Postman or ODL GUI (slow to initialize) to pre-load SDNC using ServiceID
- Set the vnf-name (SDNC) - but VID names this the vf-module-name
- ISSUE: This vnf-name has to be known to control loop applications somehow
- Set the vnf-name (SDNC) - but VID names this the vf-module-name
- Use VID to do the following
- VNF Instance → creates VNFID
- VF Modules