SDN-R Documents

Hi Shankar, have a question on your OOF_PCI_proposal, is this the right place to post?

Thanks,

Shanth Ramakrishnan

Ok, thanks. My question is related to the content of the change notification in step 3 . I will use the 5G use case area to post.

Thanks,

Shanth Ramakrishnan

We had a call specific to OOF-PCI today 8/24. Since there is a lot of detail, we will have a call every Friday at 10am US ET. We will use the same Zoom bridge as the OOF call at 11am US ET. 

I am starting a thread to discuss netconf support in SDN-R as well as netconf server simulation. We have discussed open-source alternatives to confd for the netconf server. Wipro team is evaluating options (see slide 26 in https://wiki.onap.org/download/attachments/28382769/PCI_microservice_proposal_v7_Aug24_2018.pptx?api=v2). It seems that the Honeycomb solution might be suitable since the other option had less capabilities. Seyed has also pointed out that we should also consider netopeer since it was being used for some similar tests, and is also open source. At this point, I would like to ask if anyone knows about specific comparison exercises which would be useful to the Wipro team as they are also going through the comparison.

We would like to avoid a two-step process for the step 3 netconf notification. The experience of previous work which used netopeer is that the netconf notification does not provide the new config value. This seems to be a constraint of the netconf notification statndard. Wipro team is evaluating what IETF standards provide and if any change needs to be submitted. Seyed suggested looking at yang-push (ietf draft). Comments welcome.

I have had mixed results with netopeer. Internally we have a project that builds and adds to netopeer source but to me the build can be flacky and the docker image sometimes works/sometimes doesn't work.

I honestly would stick to honeycomb based since we have experience with that in APPC netconf since pre-Amsterdam.

Agree on the notifications part being tricky but its basically odl to odl so we can get support.

Capturing another email discussion thread re. RFC support in ODL from previous call. Dongho followed up re. Netconf notification (RFC 6470) and Martin is following up re. ODL support. 

Dongho: This ODL link says that RFC-6470 is supported partially in Boron release: https://docs.opendaylight.org/en/stable-oxygen/user-guide/netconf-user-guide.html @Martin, as we discussed on the call, if you can check if RFC-6470 is fully supported with latest release or not, it will be great.

Comment from Dhruv: The other part is that even if it is supported, some work may be needed to extract the information from the notification and populate it in the config DB. For some reason the Oxygen release link below still refers to Boron release!

Thanks. Good knowledge here. Though I am looking for more clarification here. I.e. take a step back and correlate this knowledge based on 3gpp since 5g is based upon these standards. Where do you start developing on ONAP ie. on kuberneties? Got any step by step instructions applying above concept on ONAP? Documents are all over and not easy to follow at all. Let me know. Thanks.