...
| # | Description | Notes | Decision |
|---|---|---|---|
| 1 | How to deal with hardcoded E2E NW Slicing model, spike | Discusdons started with E2E NW Slicing Team, to be continued next week | |
| 2 | Which Simulator to use? NetConf Simulator Netopeer v2
| Rahul Tyagi Ericsson more lightweight, more experience. Swaminathan Seetharaman mentioned 'Honeycomb' simulator they used before. Need to investigate if it supports get-schema method over RESTConf/NetConf Need to check if we can use it with E2E NW Slicing model | For E2E use case Honeycomb simulator wil be used. If needs be for certain non E2E functionality where this simulator has limitations the team can still decide to test/develop against NeToPeer simulator |
| 3 | Should (ONAP) dmi-instance be as separate (springboot) application Could be part of DMI Manager | DMI-Instance interface should be an open standard | Tony Finnerty and Team to allow easy integration of future 3rd part DMI-Plugin instances a separate application with its own REST Interface is required |
| 4 | What datastores are supported/recognized by NCMP Interface in Istanbul Release | Suggested, see Datastore paths and format combinations section below
| Suggestions in previous column were agreed in CPS Weekly meeting |
| 5 | What datastores are supported/recognized by (ONAP) DMI-Plugin Interface in Istanbul Release | Suggested exact same as NCMP supported options
| Suggestions in previous column were agreed in CPS Weekly meeting |
| 6 | How to handle any other (custom) datastore value | Agreed in CPS Weekly meeting : Both NCMP and DMI-Plugin wil not support any other datastore value in the Istanbul timeframe | |
| 7 | What to do with old CM-Proxy interface implemented in H. | Methods never really used by E2E Network Slicing team. | Methods will be 'deprecated' using Open API option for that.. Replace and refactor other layers as needs when new methods using the new API are being implemented |
...