Thanks Brian for the quick response. Please check if I understand you correctly:
We noticed there are two Netconf Client implementations in APP-C netconf adapter folder: (1) NetconfClientRestconfImpl(), which is based on ODL Netconf Connector through Restconf interface; and (2) NetconfClientJsch(), which is a standalone implementation of Netconf Client. My previous question was mainly about the implementation (2) which lacks the multi-message transaction support. So after reading your answer, my understanding is I should follow implementation (1)'s path instead of implementation (2), and some changes to implementation (1) are also needed to support multi-message transaction, correct? Thanks again for your help, Cheng (Ian) Liu Senior Network Architect *Futurewei Technologies, Inc. *| *HUAWEI R&D USA* 5340 Legacy Drive, Suite 175, Cube 101E Plano, TX 75024 email: cheng.liu1 at huawei.com +1 (469)-277-5835 <(469)%20277-5835> On Tue, Apr 18, 2017 at 2:34 PM, FREEMAN, BRIAN D <bf1936 at att.com> wrote: > A few answers. > > > > 1. APPC uses the ODL Netconf adaptor but through the RESTCONF > interface. > > a. You can see the external mount in ODL through the standard > apidoc/explorer interface. > > b. RESTCONF uses simple single transaction semantics which was > appropriate for the vFW closed loop. > > c. More advanced netconf operations require the node to directly > call the netconf API?s in ODL and single device transactions (edit-config, > edit-config, ? , commit, unlock) can be done with that function. We have > not put that SLI node in ONAP opensource yet. > > d. Multiple device netconf operations are possible with something > we call Netconf-lite (the name came about from loosening the restrictions > in netconf) to permit (lock-device1, lock-devic2, editconfig-device1, > check-commit-device1, editconfig-device2, check-commit-device2, > commit-device1, unlock-devic1, commit-device2,unlock-device2. We have not > upstreamed this function to Opendaylight or ONAP but intend to once we > determine the right path. > > 2. SDNC doesn?t automatically load the netconf adaptor for the demo > but it is in the odl distribution of Beryllium SR2 that we are running. > > a. Generally *feature:install odl-netconf-connector-all * > > b. Then edit /opt/opendaylight/current/etc/ > opendaylight/karaf/99-netconf-connector.xml to change the default > password to the current password for the sdnc controller. > > <password xmlns="urn:opendaylight:params:xml:ns:yang:controller: > md:sal:connector:netconf"> > > Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U</password> > > c. The RESTCONF and NETCONF adaptors are all in the sdnc instance > of ODL. Log into karaf and use feature:list to see the available components > like openflow, bgpcep, sfc, ovsdb etc. > > > > > > Brian > > > > *From:* onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-bounces@ > lists.onap.org] *On Behalf Of *Cheng Ian Liu > *Sent:* Tuesday, April 18, 2017 3:10 PM > *To:* onap-discuss at lists.onap.org > *Subject:* [onap-discuss] Questions about APP-C / SDN-C Netconf Adapter > > > > Hi All, > > > > We are trying to use the ONAP APP-C Netconf Adapter > (the NetconfClientPluginImpl Class) to configure some southbound VNFs. Here > are some questions we have: > > > > 1. How to use the APP-C Netconf Adapter to complete a multi-message > Netconf transaction? > > > > Seems the current configure() method writes only one message at a time, > and closes the session right after each message. This prevents us from > sending two messages (i.e. <edit-config> the *Candidate* datastore and > <commit> the changes) in one session. Is there any other method in the code > we should use to do this multi-message transaction that we may have missed? > > > > > > > > 2. Two high-level questions: > > > > (1) May we know why APP-C did not use the Netconf Connector feature of > ODL, and instead created its own Netconf adapter? > > > > (2) May we know why the current SDN-C code does NOT come with the Netconf > (and Restconf) Adapters like APP-C does? > > > > Thanks a lot, > > > > Cheng (Ian) Liu > > Senior Network Architect > > *Futurewei Technologies, Inc. *| *HUAWEI R&D USA* > > 5340 Legacy Drive, Suite 175, Cube 101E > Plano, TX 75024 > > email: cheng.liu1 at huawei.com > > +1 (469)-277-5835 <(469)%20277-5835> > > > -- *Liu, Cheng* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/d795ed41/attachment-0001.html>
