12-20-2017 Control Loop Sub Committee Weekly Meeting
- Pamela Dragosh
Discussion items
Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
START RECORDING | |||
5 min | Logistics | @Pamela Dragosh |
|
15 min | Control Loop Modeling | @Pamela Dragosh | Per the ONAP Modeling workshop an action item is to start working with Modeling sub committee to produce Control Loop Models. |
|
|
|
|
|
|
|
|
|
|
|
|
Action items
@Pamela Dragosh - Chair vote was initiated, one nomination occurred, waiting for @Kenny Paul and @Phil Robb to confirm next steps as voting ends today.
@Ron Shacham - lead gather Control Loop Guiding Principles
Will provide in January
@Pamela Dragosh - lead to start gather Information and Data models being used for Control Loop
Will begin in January with Nigel from Ciena and Andy Mayer. 1st step will be gather current Amsterdam models then start progressing to Papyrus
@Scott Seabolt - vFirewall use case, ModifyConfig payload.
Will work on finding this information for January to determine how a Payload could be collected during design time and then utilized during runtime for an APPC ModifyConfig call. Currently this is hard coded in the Policy Template.
@Guangrong Fu - will initiate email contact for the auto-scaling use case with China teams. @Ron Shacham has setup a call already with AT&T team.
@Pamela Dragosh - will initiate email with @FREEMAN, BRIAN D regarding vDNS Use Case. We would like to simplify the use case such that Policy makes the auto scale call to APP-C (need @Randa Maher attention for this commitment) vs SO.
Need to identify/fix VOLTE gaps from Amsterdam - will wait for @Guangrong Fu next week to help drive this.
Gap 1: Configuration from DCAE, not able to distribute to Holmes. TODO: Open JIRA's in Policy/DCAE. Need @Lusheng Ji to confirm if fix is for Amsterdam or Beijing.
Gap 2: CLAMP only able to configure one rule for Holmes, would like multiple rules.
TODO: Holmes and Policy meet to share GUI for BRMS Rule Creation.
Recording
