Hi Taka, As I pointed out already I'm using APP-C version 1.2.0. However despite of version, APP-C seems to be self-contained and package naming in the DG and actual code should be in sync!
I can confirm there is no such class in my running environment, for example this returns no results: *opendaylight-user@root>bundle:find-class NetconfDeviceNode* However this - does: *opendaylight-user@root>bundle:find-class FlowControlNode* *Flow Executor - Provider (430)* *org/openecomp/appc/flow/controller/node/FlowControlNode.class* Also there is no gerrit change associated with NetconfDeviceNode: https://gerrit.onap.org/r/#/q/file:NetconfDeviceNode.java. That's why I asked if APP-C is ready and if ECOMP has fully merged into ONAP (at least APP-C parts). Can you confirm you have tested NETCONF scenario and it worked? Thanks, Beka On Wed, 16 May 2018 at 20:41 CHO, TAKAMUNE <[email protected]> wrote: > HI Beka, > > > > I see your problem. APPC refactored the naming space from com.att to > org.onap in R2. I am not sure what version you are using now. The plugin > for R2 would be “org.onap.appc.device.interfaces.node.NetconfDeviceNode” > for DownloadNetconf DG. > > > > R2 release sign off would be 5/24. If you want use R2, then you would wait > after 5/24. > > > > Hope that would help > > > > Taka > > > > *From:* Beka Tsotsoria [mailto:[email protected]] > *Sent:* Wednesday, May 16, 2018 4:29 AM > *To:* CHO, TAKAMUNE <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [onap-discuss] APP-C incomplete? > > > > Taka, > > > > thank you for the response. > > > > Unfortunately the links provided by you do not make much sense for me, > since they do not address the issues I'm facing. More important questions > are still open: is my assumption correct that DOWNLOAD_CONFIG_DG should be > set to DownloadNetconfConfig/DownloadRestconfConfig in case of NETCONF? If > yes why are plugins > *com.att.appc.device.interfaces.node.NetconfDeviceNode* and > *com.att.sdnctl.restconf.RestConfCallNode* missing? > > > > Beka > > > > On Tue, 15 May 2018 at 14:59 CHO, TAKAMUNE <[email protected]> wrote: > > Hi Beka, > > > > Thanks for interested on APPC. > > > > We will answer your question that you posted on wiki later. > > > > APPC is ready for netconf. Here is the page when APPC tested for R1: > https://wiki.onap.org/display/DW/Creating+a+Netconf+Mount > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Creating-2Ba-2BNetconf-2BMount&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=98uegbItCAYrInpaMjJ4Hm-k35VauM4Hvd1j2siHTx0&s=1cK0hNfCCBNHkV09EOLvFO4vzfx6aLup18fV881Tw4U&e=> > > > > APPC is ready for ansible. Here is the source code that APPC supports for > Ansible: > https://gerrit.onap.org/r/gitweb?p=appc.git;a=tree;f=appc-adapters/appc-ansible-adapter/appc-ansible-example-server;h=90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4;hb=refs/heads/master > <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dappc.git-3Ba-3Dtree-3Bf-3Dappc-2Dadapters_appc-2Dansible-2Dadapter_appc-2Dansible-2Dexample-2Dserver-3Bh-3D90fa259c3905d1c5f25b9668a6e537a7c1f1a8e4-3Bhb-3Drefs_heads_master&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=98uegbItCAYrInpaMjJ4Hm-k35VauM4Hvd1j2siHTx0&s=CHDSOwdwynnnnuuuJsSe2lwS-YrhEYibQ3tySUXln_s&e=> > > > > Thanks > > > > Taka > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Beka Tsotsoria > *Sent:* Tuesday, May 15, 2018 7:30 AM > *To:* [email protected] > *Subject:* [onap-discuss] APP-C incomplete? > > > > Dear all, > > > > I'm reposting this question here, please have a look: > https://wiki.onap.org/display/DW/questions/30900903/what-should-be-specified-in-tmp.configureactiondg.download-config-dg-when-working-with-ansible-adapter > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_questions_30900903_what-2Dshould-2Dbe-2Dspecified-2Din-2Dtmp.configureactiondg.download-2Dconfig-2Ddg-2Dwhen-2Dworking-2Dwith-2Dansible-2Dadapter&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=CZeJ_mBTPGgEd14jin5iVXoFxXv6o5jCO0TmY3mBPo0&s=rkRZ554kZYpcRgtYAjBNusexMlVBZu5p_en3jzOwW24&e=> > > > > > > Also we have trouble establishing NETCONF connection from APP-C to the > south. Above question partially applies here too - what to specify in > *DOWNLOAD_CONFIG_DG*.*CONFIGURE_ACTION_DG?* We tried > both DownloadNetconfConfig and DownloadRestconfConfig, but plugins > *com.att.appc.device.interfaces.node.NetconfDeviceNode* and > *com.att.sdnctl.restconf.RestConfCallNode* > > can not be resolved at runtime (appc version 1.2.0), neither are they > presented in the codebase (v1.2.0 and latest master). > > > > Important questions that arise: is APP-C ready for NETCONF? Is APP-C ready > for Ansible? I have an impression that some parts of ECOMP are not still > merged into ONAP. Can you confirm if this is the case? If yes when should > we expect functional APP-C? > > > > I have other issues as well to report, but I would like to get > clarifications on this first. > > > > > > Thank you and kind regards, > > Beka > > > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
