From: saravanan.a75@... [mailto:saravanan.a75@...]
Sent: Thursday, July 4, 2019 11:52 AM
To: Michal Čmarada <michal.cmarada@...>
Cc: honeycomb-dev@...; Peter Lapoš <peter.lapos@...>
Subject: RE: [honeycomb-dev] <module>-impl project code file generation

 

Hello Michal,

 

I have one more related question.

Honeycomb is sending lot of yang capabilities. Where is this list maintained? Can I remove some unused capabilities and keep only my yang capability?

How to do this?

 

Regards,
Saran

 

<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">

<capabilities>

<capability>org:onap:ccsdk:features:sdnr:northbound:oofpcipoc?module=oofpcipoc&amp;revision=2019-03-08</capability>

<capability>urn:ietf:params:xml:ns:yang:iana-if-type?module=iana-if-type&amp;revision=2014-05-08</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-interfaces?module=ietf-interfaces&amp;revision=2014-05-08</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:impl?module=opendaylight-sal-binding-broker-impl&amp;revision=2013-10-28</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&amp;revision=2010-10-04</capability>

<capability>http://openconfig.net/yang/bgp?module=openconfig-bgp&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-message?module=bgp-message&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:config:legacy-entity-ownership-service-provider?module=opendaylight-legacy-entity-ownership-service-provider&amp;revision=2016-02-26</capability>

<capability>http://openconfig.net/yang/bgp-multiprotocol?module=openconfig-bgp-multiprotocol&amp;revision=2015-10-09</capability>

<capability>http://openconfig.net/yang/openconfig-ext?module=openconfig-extensions&amp;revision=2015-10-09</capability>

<capability>http://openconfig.net/yang/bgp-types?module=openconfig-bgp-types&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding?module=opendaylight-md-sal-binding&amp;revision=2013-10-28</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bmp-message?module=bmp-message&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding:v1:codec?module=opendaylight-md-sal-binding-v1-codec&amp;revision=2016-07-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:aaa?module=aaa&amp;revision=2016-12-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:general-entity?module=general-entity&amp;revision=2015-08-20</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom?module=opendaylight-md-sal-dom&amp;revision=2013-10-28</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-evpn?module=odl-bgp-evpn&amp;revision=2017-12-13</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:remote?module=sal-remote&amp;revision=2014-01-14</capability>

<capability>http://openconfig.net/yang/policy-types?module=openconfig-policy-types&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-vpn-ipv6?module=bgp-vpn-ipv6&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:md:sal:config:impl:cluster-singleton-service?module=cluster-singleton-service-impl&amp;revision=2016-07-18</capability>

<capability>urn:opendaylight:yang:extension:yang-ext?module=yang-ext&amp;revision=2013-07-09</capability>

<capability>http://openconfig.net/yang/openconfig-types?module=openconfig-types&amp;revision=2015-10-09</capability>

<capability>urn:ietf:params:xml:ns:yang:rpc-context?module=rpc-context&amp;revision=2013-06-17</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-peer-rpc?module=bgp-peer-rpc&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:pmsi-tunnel?module=pmsi-tunnel&amp;revision=2016-08-12</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?module=ietf-netconf-notifications&amp;revision=2012-02-06</capability>

<capability>http://openconfig.net/yang/local-routing?module=openconfig-local-routing&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:operational-dom-store?module=opendaylight-operational-dom-datastore&amp;revision=2014-06-17</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-multiprotocol?module=bgp-multiprotocol&amp;revision=2017-12-07</capability>

<capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&amp;revision=2011-06-01</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:rfc2385:cfg?module=rfc2385&amp;revision=2016-03-24</capability>

<capability>http://openconfig.net/yang/interfaces?module=openconfig-interfaces&amp;revision=2016-04-12</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring?module=ietf-restconf-monitoring&amp;revision=2017-01-26</capability>

<capability>http://openconfig.net/yang/network-instance-types?module=openconfig-network-instance-types&amp;revision=2015-10-18</capability>

<capability>urn:TBD:params:xml:ns:yang:network-topology?module=network-topology&amp;revision=2013-10-21</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bmp-monitor?module=bmp-monitor&amp;revision=2017-12-07</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&amp;revision=2013-07-15</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-linkstate?module=bgp-linkstate&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:ieee754?module=ieee754&amp;revision=2013-08-19</capability>

<capability>urn:TBD:params:xml:ns:yang:network-topology?module=network-topology&amp;revision=2013-07-12</capability>

<capability>http://openconfig.net/yang/routing-policy?module=openconfig-routing-policy&amp;revision=2015-10-09</capability>

<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-restconf?module=ietf-restconf&amp;revision=2013-10-19</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:bgp:linkstate-app-config?module=bgp-linkstate-app-config&amp;revision=2016-06-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:entity-ownership-service?module=opendaylight-entity-ownership-service&amp;revision=2015-08-10</capability>

<capability>urn:sal:restconf:event:subscription?module=sal-remote-augment&amp;revision=2014-07-08</capability>

<capability>instance:identifier:patch:module?module=instance-identifier-patch-module&amp;revision=2015-11-21</capability>

<capability>subscribe:to:notification?module=subscribe-to-notification&amp;revision=2016-10-28</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-segment-routing-ext?module=bgp-segment-routing&amp;revision=2015-10-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-rib?module=bgp-rib&amp;revision=2017-12-07</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-restconf?module=ietf-restconf&amp;revision=2017-01-26</capability>

<capability>config:aaa:authn:encrypt:service:config?module=aaa-encrypt-service-config&amp;revision=2016-09-15</capability>

<capability>urn:opendaylight:params:xml:ns:yang:md:sal:config:spi:cluster-singleton-service?module=cluster-singleton-service-spi&amp;revision=2016-07-18</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-labeled-unicast?module=bgp-labeled-unicast&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-epe?module=bgp-epe&amp;revision=2015-06-22</capability>

<capability>http://openconfig.net/yang/bgp-policy?module=openconfig-bgp-policy&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:common?module=opendaylight-md-sal-common&amp;revision=2013-10-28</capability>

<capability>urn:opendaylight:params:xml:ns:yang:footprint?module=footprint&amp;revision=2017-08-30</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:inmemory-datastore-provider?module=opendaylight-inmemory-datastore-provider&amp;revision=2014-06-17</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bmp-monitor-config?module=odl-bmp-monitor-config&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:network:concepts?module=network-concepts&amp;revision=2013-11-25</capability>

<capability>urn:opendaylight:params:xml:ns:yang:iana?module=iana&amp;revision=2013-08-16</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-vpn?module=bgp-vpn&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:config?module=config&amp;revision=2013-04-05</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-inet?module=bgp-inet&amp;revision=2017-12-07</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:netty:timer?module=netty-timer&amp;revision=2013-11-19</capability>

<capability>urn:ietf:params:xml:ns:netconf:notification:1.0?module=notifications&amp;revision=2008-07-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-vpn-ipv4?module=bgp-vpn-ipv4&amp;revision=2017-12-07</capability>

<capability>urn:ietf:params:xml:ns:netmod:notification?module=nc-notifications&amp;revision=2008-07-14</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp-types?module=bgp-types&amp;revision=2013-09-19</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring-extension?module=ietf-netconf-monitoring-extension&amp;revision=2013-12-10</capability>

<capability>urn:opendaylight:params:xml:ns:yang:rsvp?module=rsvp&amp;revision=2015-08-20</capability>

<capability>urn:opendaylight:aaa:app:config?module=aaa-app-config&amp;revision=2017-06-19</capability>

<capability>urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?module=odl-general-entity&amp;revision=2015-09-30</capability>

<capability>urn:ietf:params:netconf:base:1.1</capability>

<capability>urn:ietf:params:netconf:base:1.0</capability>

<capability>http://openconfig.net/yang/network-instance?module=openconfig-network-instance&amp;revision=2015-10-18</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:core:spi:config-dom-store?module=opendaylight-config-dom-datastore&amp;revision=2014-06-17</capability>

<capability>urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions?module=bgp-openconfig-extensions&amp;revision=2017-12-07</capability>

<capability>http://openconfig.net/yang/bgp-operational?module=openconfig-bgp-operational&amp;revision=2015-10-09</capability>

<capability>urn:opendaylight:params:xml:ns:yang:controller:netty?module=netty&amp;revision=2013-11-19</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-yang-library?module=ietf-yang-library&amp;revision=2016-06-21</capability>

<capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2013-07-15</capability>

</capabilities>

<session-id>1</session-id>

</hello>

 

 

-----Original Message-----
From: Saravanan A (TECH)
Sent: Thursday, July 4, 2019 11:06 AM
To: Michal Čmarada <michal.cmarada@...>
Cc: honeycomb-dev@...; Peter Lapoš <peter.lapos@...>
Subject: RE: [honeycomb-dev] <module>-impl project code file generation

 

Hello Michal,

Thanks a lot for your answer and support.

Your solution to change the basic capabilities in NetconfServerDispatcherProvider.java solved my problem.

Now I am able to mount honeycomb server into ODL.

 

Regards,

Saran

 

 

 

Sensitivity: Internal & Restricted

 

-----Original Message-----

From: Michal Čmarada [mailto:michal.cmarada@...]

Sent: Monday, July 1, 2019 1:14 PM

To: Saravanan A (TECH) <saravanan.a75@...>

Cc: honeycomb-dev@...; Peter Lapoš <peter.lapos@...>

Subject: RE: [honeycomb-dev] <module>-impl project code file generation

 

** This mail has been sent from an external source. Treat hyperlinks and attachments in this email with caution**

 

Hi Saran,

 

We use implementation of Netconf from Opendaylight. This feature is loaded from original implementation of netconf. You can take a look at https://clicktime.symantec.com/3Y2c7TnDKfb2FK447jzCEhB7Vc?u=https%3A%2F%2Fgit.opendaylight.org%2Fgerrit%2Fgitweb%3Fp%3Dnetconf.git%3Ba%3Dtree%3Bf%3Dnetconf%2Fnetconf-netty-util%2Fsrc%2Fmain%2Fjava%2Forg%2Fopendaylight%2Fnetconf%2Fnettyutil%2Fhandler%2Fexi%3Bh%3Dbad12569de87e7ba9c666d5b21ed4bceffec5220%3Bhb%3Drefs%2Fheads%2Fmaster

 

What you can do first is modify the default capabilities that our netconf implementation is being started with. To do this you need to change the DEFAULT_BASE_CAPABILITIES Original implementation from odl netconf:

    public static final Set<String> DEFAULT_BASE_CAPABILITIES = ImmutableSet.of("urn:ietf:params:netconf:base:1.0", "urn:ietf:params:netconf:base:1.1", "urn:ietf:params:netconf:capability:exi:1.0");

to a custom set without exi:1.0

    public static final Set<String> DEFAULT_ CAPABILITIES = ImmutableSet.of("urn:ietf:params:netconf:base:1.0", "urn:ietf:params:netconf:base:1.1");

You can find this in NetconfServerDispatcherProvider class. Located in honeycomb/infra/northbound/netconf/src/main/java/io/fd/honeycomb/northbound/netconf/NetconfServerDispatcherProvider.java

 

This should be enough and honeycomb shouldn't report this capability anymore. Since this hasn't been used in honeycomb it shouldn't be a problem if the feature is removed. However I haven`t tested this so I am not sure what this will cause. And if netconf has some internal dependencies on this feature you may run into other errors. You would need to test this by yourself.

 

Hopefully this will work. But if it doesnt the other options would be to create a dummy handler for this feature in honeycomb (or try to do a propper full implementation). Next option is to modify the Netconf implementation in honeycomb to remove this feature (not sure if this is possible and how hard it can be). Or you can build your own version of netconf without the exi support and built honeycomb on top of it.

 

 

Michal

 

From: Marek Grądzki <margradz@...>

Sent: Thursday, June 27, 2019 12:45 PM

To: saravanan.a75@...; Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco) <mcmarada@...>

Cc: honeycomb-dev@...

Subject: Re: [honeycomb-dev] <module>-impl project code file generation

 

Hello Saran,

 

I am no longer actively involved in the project.

Adding Michal Cmarada, current PTL, to CC.

 

Regards,

Marek

 

czw., 27 cze 2019 o 10:53 saravanan.a75@... <saravanan.a75@...> napisał(a):

> 

> Hello Team,

> 

> Any update on this query?

> 

> Regards,

> Saran

> 

> 

> 

> -----Original Message-----

> From: Saravanan A (TECH)

> Sent: Tuesday, June 25, 2019 7:00 PM

> To: Marek Grądzki <margradz@...>; honeycomb-dev@...

> Subject: RE: [honeycomb-dev] <module>-impl project code file

> generation

> 

> Hello Team/ Marek,

> 

> I have developed a simulator using honeycomb 08_10 version and testing it with opendaylight controller.

> 

> Honeycomb agent is sending "urn:ietf:params:netconf:capability:exi:1.0" as part of initial <hello> message.

> So opendaylight start sending binary request data as described in https://clicktime.symantec.com/3DWmpigZygsWXTdQEQrgG6Z7Vc?u=https%3A%2F%2Ftools.ietf.org%2Fid%2Fdraft-varga-netconf-exi-capability-00.html%23W3C.REC-exi-20110310 to honeycomb agent and I am getting deserialization exception in Honeycomb while reading this binary request data.

> 

> I have following questions:

> 1. I would like to remove this "urn:ietf:params:netconf:capability:exi:1.0" capability from the <hello> message. Where in honeycomb code this capability is mentioned?

> 2. Is this W3C.REC-exi-20110310 EXI feature really supported in honeycomb? If so, why I am getting deserialization exception?

> 

> Regards,

> Saran

> 

> 

> 

> Sensitivity: Internal & Restricted

> 

> -----Original Message-----

> From: Marek Grądzki [mailto:margradz@...]

> Sent: Friday, August 31, 2018 11:55 AM

> To: Saravanan A (Communications-Telecom Equipment)

> <saravanan.a75@...>

> Cc: honeycomb-dev@...

> Subject: Re: [honeycomb-dev] <module>-impl project code file

> generation

> 

> ** This mail has been sent from an external source. Treat hyperlinks

> and attachments in this email with caution**

> 

> Hello Saran,

> 

> generating netconf agent based on custom model is not supported.

> 

> But feel free to create jira ticket if you are interested in the feature.

> Contributions to design/implementation are welcomed!

> 

> Currently Honeycomb plugin archetype generates maven project structure, code and documentation only for the sample model (parametrized by root artifact id):

> https://clicktime.symantec.com/37CEjWJgYbmpnNUpRvjUNPA7Vc?u=https%3A%2

> F%2Fgit.fd.io%2Fhoneycomb%2Ftree%2Ftools%2Farchetype%2Fsrc%2Fmain%2Fre

> sources%2Far

> chetype-resources/__rootArtifactId__-api/src/main/yang/__rootArtifactI

> d__.yang

> 

> Here is relevant patch where you can find more info:

> https://clicktime.symantec.com/3XiMvybPV57vdgoqBshFYtd7Vc?u=https%3A%2

> F%2Fgerrit.fd.io%2Fr%2F%23%2Fc%2F2429%2F

> 

> You can find more examples in:

> https://clicktime.symantec.com/3Cw91tvzguNH9xJHuiA4wnQ7Vc?u=https%3A%2

> F%2Fdocs.fd.io%2Fhoneycomb%2F1.18.10-SNAPSHOT%2Frelease-notes-aggregat

> or

> /release_notes.html#_devel_guide

> https://clicktime.symantec.com/3Wquvr7n5EQJAG75DKgSKm37Vc?u=https%3A%2

> F%2Fgit.fd.io%2Fhoneycomb%2Ftree%2Fsamples

> 

> Please also take a look at https://clicktime.symantec.com/3JmsWLQWoXrwQrJ8nLvVpMc7Vc?u=https%3A%2F%2Fwiki.fd.io%2Fview%2FHc2vpp which is Honeycomb agent for VPP.

> 

> Regards,

> Marek

> 

> śr., 29 sie 2018 o 05:16 saravanan.a75@... <saravanan.a75@...> napisał(a):

> >

> > Hello Team,

> >

> >

> >

> > I am using honeycomb 18.07 version. Trying to bring up Netconf server for my own yang model file.

> >

> >

> >

> > I modified the “honeycomb/enodebsim/enodebsim-api/src/main/yang/enodebsim.yang” file with my yang content.

> >

> > Then I did the following:

> >

> > $cd honeycomb/

> >

> > $ rm enodebsim/pom.xml enodebsim/enodebsim-api/pom.xml

> >

> > $ vi pom.xml      #removed the enodebsim from Module list

> >

> >                 $ mvn -X archetype:generate

> > -DarchetypeGroupId=io.fd.honeycomb.tools

> > -DarchetypeArtifactId=honeycomb-plugin-archetype

> > -DarchetypeVersion=1.18.10-SNAPSHOT -DinteractiveMode=false

> > -DgroupId=org.onap.ransim -DartifactId=enodebsim

> > -Dversion=1.0.0-SNAPSHOT -Dpackage=org.onap.ransim

> >

> > $cd honeycomb/enodebsim/

> >

> > $mvn clean install

> >

> >

> >

> > This generated the java files for my new yang model. However the code generated in “honeycomb/enodebsim/enodebsim-impl” is not referring my new yang model. It still uses the old sample yang model.

> >

> >

> >

> > Will the generate netconf agent automatically includes new yang model into capabilities?

> >

> >

> >

> > Pls let me know if I missed any steps. If you can share the link/doc explaining what needs to be done for custom yang model simulation?

> >

> >

> >

> >

> >

> > Regards,

> > Saran

> >

> >

> >

> >

> >

> > Sensitivity: Internal & Restricted

> >

> > The information contained in this electronic message and any

> > attachments to this message are intended for the exclusive use of

> > the

> > addressee(s) and may contain proprietary, confidential or privileged

> > information. If you are not the intended recipient, you should not

> > disseminate, distribute or copy this e-mail. Please notify the

> > sender immediately and destroy all copies of this message and any

> > attachments. WARNING: Computer viruses can be transmitted via email.

> > The recipient should check this email and any attachments for the

> > presence of viruses. The company accepts no liability for any damage

> > caused by any virus transmitted by this email.

> > https://clicktime.symantec.com/3LHWiJpF3JyaLm7PsYhEnAt7Vc?u=www.wipr

> > o.com

> > -=-=-=-=-=-=-=-=-=-=-=-

> > Links: You receive all messages sent to this group.

> >

> > View/Reply Online (#816):

> > https://clicktime.symantec.com/34cdidSm8tEP2DpNMjyZbau7Vc?u=https%3A

> > %2F%2Flists.fd.io%2Fg%2Fhoneycomb-dev%2Fmessage%2F816

> > Mute This Topic:

> > https://clicktime.symantec.com/33pfbLXCFawi25CcVEfKseV7Vc?u=https%3A

> > %2F%2Flists.fd.io%2Fmt%2F25070762%2F675181

> > Group Owner: honeycomb-dev+owner@...

> > Unsubscribe:

> > https://clicktime.symantec.com/3SmoByB9kTv6p7PwM85RwUX7Vc?u=https%3A

> > %2F%2Flists.fd.io%2Fg%2Fhoneycomb-dev%2Funsub

> > [margradz@...]

> > -=-=-=-=-=-=-=-=-=-=-=-

> The information contained in this electronic message and any

> attachments to this message are intended for the exclusive use of the

> addressee(s) and may contain proprietary, confidential or privileged

> information. If you are not the intended recipient, you should not

> disseminate, distribute or copy this e-mail. Please notify the sender

> immediately and destroy all copies of this message and any

> attachments. WARNING: Computer viruses can be transmitted via email.

> The recipient should check this email and any attachments for the

> presence of viruses. The company accepts no liability for any damage

> caused by any virus transmitted by this email.

> https://clicktime.symantec.com/3LHWiJpF3JyaLm7PsYhEnAt7Vc?u=www.wipro.

> com

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com