...
Message from Policy to SDN-R
RAN model – affects netconf, and also the payload format of msg from Policy
- ConfigDB database and API spec
- Yang model queries – PCI as r/w, change trigger (neighbor list change???)
- Multiple config changes in 1 message from Policy to SDN-R, which means SDN-R has to extract the different parts
- PNF-name, PLMN id
(sko) TO BE CLEANED UP - once the doc is uploaded
Discussion items
Time | Item | Who | Notes | ||||||
---|---|---|---|---|---|---|---|---|---|
60min |
| 20min | RAN model – affects netconf, and also the payload format of msg from Policy | 20min | ConfigDB database and API spec |
...
Next steps
- swagger.json for ONAP components
- yang module for SDN-R and the RAN simulator
Chat
from Rebecca Lantz (Ericsson) to all: 06:24 PM
I think pnf-name just needs to be unique and value provided at service instantion == value provided by PNF at registration. The proposal for pnf-name is to use first 3 letters of vendor name + serial number. I suppose it would change if there was hardware swap out?
Von Prashant Rajpal an alle: 06:31 PM
If there is a name change of PNFs due to any operational reasons, then does it mean that we will have to change in SDN-R? If we were to use ID, then changing any names would not cause downstream impacts.
from demx8as6 to all: 06:34 PM
here the pnf-name is a global identifier - if you change it you basically "delete" an existing pnf and create a new one. - so I assume there is a whole process behind
from Rebecca Lantz (Ericsson) to all: 06:41 PM
will YANG model be hardcoded in SDNC? Or retrieved from SDC? Or retrieved from PNF?
from demx8as6 to all: 06:45 PM
at least retrieved from PNF (NetConf-Server) - there might be an advantage to add yang models in advance to ODL (but not mandatory)
from Rebecca Lantz (Ericsson) to all: 06:48 PM
ok so config database will use RFC 6022 <get-schema> on NETCONF interface. Thanks.
from demx8as6 to all: 06:50 PM
yep