This page is used to list important questions and answers related to the use cases. The goal is to explain the principles and possibly clarify further with concrete examples based on a specific use case, such as vCPE or VoLTE. With this we can avoid the same questions being asked repeatedly. We invite people to contribute to this wiki page by answering existing questions or adding new questions.
- The output of SDC will include a variety of file (csar, xml, yang, etc) being distributed to multiple modules, SO, AAI, Policy, etc. Can we create document to specify the details, including package structure, format, usage, etc. There are NSD and VNFD specs on the VF-C page (refer https://wiki.onap.org/display/DW/VF-C+R1+Deliverables). Does ONAP use them as generic spec?
Answer: - For VNF onboarding, do we use HEAT as the input for the VPP-based VNFs? Does SDC still convert them to TOSCA internally and output TOSCA-based VNF packages?
Answer: For vCPE, the input is HEAT. Internally, SDC converts HEAT to TOSCA. The output of onboarding is TOSCA-based. The service description is TOSCA but the attachment include HEAT artifacts, which will be distributed to SO. SO will pass HEAT to Multi-VIM.
For VoLTE, the input is TOSCA. It needs to be confirmed that SDC can support it. - What is the complete list of artifacts needed to complete a service design? Workflow recipes for SO, data model for AAI, Yang and DGs for SDNC and APPC, policies, data analytic programs. Anything else?
Answer:- Workflows for SO.
- Yang models and DGs
- Policies
- AAI data models: generic VNF model (existing) and service-specific models (to be created).
- Data analytics: to reuse the existing TCA.
- Robot framework to emulate BSS - What specific workflow recipes are needed for vCPE? What are the tools to create such recipes? How are the recipes associated with the service, packaged, and distributed?
Answer: to discuss with SO
A generic workflow to instantiate the service infrastructure. Can we reuse the existing generic VNF workflow?
Another customer-orient workflow to create per-customer on-demand service. - Are we supposed to create a specific set of workflow recipes for each use case? E.g., one set for vCPE and one set for VoLTE.
Answer: There are generic workflows that can be reused. There are also needs for specific workflows for each use case. - Do we manual create AAI data models or use tools? How are the model packaged with the service and distributed? What data models are needed for vCPE?
Answer: We need a consumer broadband service model. The existing generic VNF model will be reused. Additional parameters may be needed on top of the generic VNF model to create specific use case VNF models. There are tools to do this. To discuss with AAI. - Who creates the Yang files to define the SDNC/APPC NBI APIs and data models? Does SDC use the Yang files?
Answer: For vCPE, Yang files are needed for SDNC to define the NBI API and the service data model for configuration. The APPC will just do stop/start, so no Yang files are needed.
The SDNC team will define the Yang files for the SDNC NBI APIs. The Yang models will be based on the Yang models provided by individual VNFs.
In R1, DG Builder will work separately outside of SDC. So SDC does not use the Yang files. The long term goal is to integrate DG Builder into SDC. - In the general case, ONAP may need to create a new SDNC/APPC dedicated for a new service when the service is instantiated. Is it designed by the ONAP operational team outside of SDC or included as a SDC function? What is the process of creating a new SDNC/APPC? Who does it and in what way, manual or automatic?
Answer: In R1, the DGs are packaged with SDNC/APPC and are loaded into their DBs during instantiation. SDC does not use such DGs. The SDNC and APPC instances are created in advance with the required DGs loaded. The creation of SDNC and APPC is not part of SDC. It belongs to OOM. - What policies are needed for vCPE? Are they created manually or using tools (Drools?) How are they integrated into SDC or CLAMP?
Answer: - Topics need to be defined and used on DMaaP to enable communication among different modules. When are such topics defined and how are they configured? E.g., Policy will send event on a TOPIC_VM_RESTART to invoke VM restart, APPC will subscribe to TOPIC_VM_RESTART and execute the restart DG. When and where to define this topic? Who configures Policy and APPC to publish/subscribe to the topic, and when?
Answer: - Are we going to let VNFs actively post VES data to the DCAE REST API for data collection? If yes, we will need to configure the VNFs with the DCAE collector's URI. Is this configuration performed by APPC? Does APPC get the URI from AAI?
Answer: - Who will develop the data analytics program? Is it required to re-build the DCAE containers to include the analytics program?
Answer: - Are we going to build the analytics program a CDAP application or a docker container?
Answer: - Are there any KPI scripts that need to be created in SDC?
Answer: - What Robot testings need to be created during design time? How is the process integrated into SDC?
Answer: We need Robot framework to emulate BSS to send in customer order. We also need robot framework to load data into DHCP and AAA. - Is there a standard format for Robot testing reports? How are they presented in ONAP?
Answer: talk to Daniel Rose, Jerry Flood. - Are we going to use the generic VID or create a vCPE flavor VID to instantiate vCPE?
Answer: - What kind of monitoring dashboard is required for vCPE?
Answer: