Discussion items
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| Prepare for August 6th meeting | |||
ATTENDEES
NOTES
Functional Requirement #1
Defining and modeling parameters used for LCM later on.
VNF configuration for instantiation. Nothing covers the LCM part. Interim solution for Casablanca is to use CLAMP to set these up.
- How to define those parameters?
- Use the tools that SDNC is using. CDS and Data Dictionary for instantiation parameters and LCM parameters.
- Where do you go to get those parameters?
- When the controller executes the LCM, the controller can fetch the parameters from the data dictionary.
What is the relationship between CDS and Data Dictionary tool?
There is work being done for CDS/data dictionary to get this done.
Functional Requirement #2
vFirewall use case is out-of-date. Bring it up to standard with other use cases to leverage CDS and Data Dictionary. Should ModifyConfig parameters be a part of policy or the data dictionary?
Easiest to use amongst all the use cases and used for automated regression.
The APPC is ModifyConfig is old API. Question is to Brian Freeman and Takamune Cho to upgrade to new API.
Functional Requirement #3
Common Actor API - make the Dmaap based API to perform control loop actions simply configurable.
How do we easily add components, eg. optimization, machine learning?
CLAMP could be simplified in setting up control loops. Perhaps there is a DB that holds what Actors and APIs are available (may be unnecessary).
Functional Requirement #4
Ease of creating analytics component and onboard DCAE microservices.
CLAMP can only use TCA and Holmes. Need to be more generic.
How to define something to be onboarding needs to be simpler? eg. Acumos flavored analytic.