ONAP Control Loop Flows Beijing Ron Shacham Carol
ONAP Control Loop Flows - Beijing Ron Shacham, Carol Nelson, Gervais -Martial Ngueko, Chrisophe Closset, Pierre Close, Sebastien Determe January 15, 2018
Assumptions in Beijing Release • The flows described here apply to the Beijing release, with possible changes noted for future releases • There is no mechanism in place for automated triggering of DCAE service assurance deployment, i. e. DCAE microservice instantiation and configuration will be driven by CLAMP - DTI is not part of ONAP • The DCAE-DS will not generate any policies in Beijing - It is hoped that the default policies for VNF types entered in DCAE-DS will be stored in the Policy Repository in a later release, such as Casablanca. • DCAE-DS needs to: - Generate TOSCA Service Template describing the different parts of the flow: source, collector, analytics, operational policy reference/placeholder - Generate Cloudify Blueprint - Store both service template and blueprint in SDC catalog as part of Service/Resource instance - Distribute these service assurance artifacts for consumption by DCAE and CLAMP 2
Beijing Design Flow D 1 Option 1: User creates a new flow from flow components Source VES collector TCA microservice Operational policy placeholder Option 2: User chooses an existing flow in the catalog User saves service assurance flow as an artifact of a resource instance within a service Certification of service, followed by distribution Need to work with DCAE-DS and/or DCAE onboarding to establish exact format of blueprint/service template, including what is provided as an input. CLAMP SDC D 1 Control Loop Design GUI Distribution Policy Repo Catalog SDC Service Design GUI DCAE
Beijing Design Flow D 2 Distribution of service assurance artifacts will go D 3 to both CLAMP and DCAE D 2 CLAMP processing of service template artifact • • • Service template used to visualize the flow Policy model TOSCA used to generate configuration windows Who will provide the Policy model TOSCA to CLAMP through an API? Should this be linked from the service template to a Nexus repo? D 3 DCAE stores blueprint, indexed by service/resource instance IDs CLAMP CL Design SDC D 2 D 1 Control Loop Design GUI Distribution Catalog SDC Service Design GUI Policy Repo D 3 DCAE CL Design
Beijing Runtime Flow – Configure CL R 1 CLAMP generates policies based on the models that are referenced in the blueprint. CLAMP CL Design SDC R 1 Distribution Policy Repo CL Design Control Loop Design GUI Catalog SDC Service Design GUI DCAE CL Design
Beijing Runtime Flow – Deploy CL R 2 • • • CLAMP populates the policy ID in input set for blueprint CLAMP processes full list of inputs CLAMP allows for inputs to blueprint to be configured CLAMP generates a full set of inputs CLAMP triggers the DCAE runtime deployment CLAMP CL Design SDC Distribution R 2 Policy Repo CL Design Control Loop Design GUI Catalog SDC Service Design GUI DCAE CL Design
Beijing Runtime Flow - Update RU 1 RU 2 User makes updates via CLAMP UI. • CLAMP updates either microservice configuration or Operational Policies in the Policy Repository. • Microservice configuration policy changes are pushed to DCAE through Policy Handler CLAMP CL Design SDC RU 1 Distribution Policy Repo CL Design Control Loop Design GUI RU 2 Catalog SDC Service Design GUI DCAE CL Design
Full Beijing Flow DCAE SDC DCAE-DS C. L. flow Creation/pre-defined specific user created flows TBC Distribute C. L. Blueprint model to DCAE inventory (!!this is necessary minimum for Beijing!!) Policy CLAMP m. S Tosca (create Component Spec) Creation/Onboarding (TBC for Beijing/manual) Distribute C. L. . Flow description (Tosca) to CLAMP Retrieve m. S Tosca from catalog (TBC for Beijing/manual) Configure all m. S ‘s and create configuration policies Configure actions and create operational policies Trigger blueprint model ! deployment and start the resulting C. L. instance! (‘env’ file sent in API to DCAE to configure blueprint for deployment) C. L. instance deployment Update m. S ‘s and update configuration policies Monitor/Manage C. L. instance 8
- Slides: 8