Date   

REMINDER: LFN Booth Demo Ideas for ONS Europe Due 7/31

Edward Warnicke
 

FD.io folks,

We hope that you are planning to attend ONS Europe, September 23-25, in Antwerp, Belgium. Those in attendance at the last three ONS events will recall that we hosted an LF Networking Booth that showcased 8-10 compelling, community-driven demos from the LFN technical projects. See this blog post from ONS North America last April to learn more about the opportunity. 

We wanted to reach out now to the FD.io community to let you know that there will be space for 8-10 networking demos inside the LFN booth again at ONS Europe and they are seeking demo ideas using the same process. The goal is to show compelling uses of networking project technology to solve real world industry challenges.

Demos that show cross-project elements (e.g. between LFN projects and other networking projects), that map to a specific industry use case, or are endorsed by a service provider are preferred. That said, there is some room for demos that highlight the good work and value-add from projects that don't necessarily meet these criteria. At least one demo slot will be made available for each LFN project (FD.io, ONAP, ODL, OPNFV, PNDA, SNAS, Tungsten Fabric) that submits a quality idea.  

Demos stations will again have storage space, a counter, backdrop, monitor, power, and Wi-Fi internet provided. There is no cost to host a standard demo in the LFN booth although additional power, internet, space, etc. may incur a cost. 

Here are the key dates to keep in mind:
  • July 10: Demo idea solicitation email sent to community lists
  • July 31: Demo ideas submissions due
  • August 14: Demos ideas reviewed, chosen, and notifications sent
  • September 23-25: Demos shown at ONS
To submit your demo idea for consideration, please collect and provide the following information:
  • Demo title (10 words max)
  • Brief demo description (200 words max)
  • List of demo manager(s) with contact information 
  • List of open source projects involved
  • List of companies involved
  • Any extra requirements or special considerations
Demo manager responsibilities include:
  • Creating the demo concept and actual demo to be shown
  • Responding promptly to requests for information
  • Meeting all demo preparation deadlines
  • Setting up and testing the demo pre-show and taking down post-show
  • Staffing the demo during ONS expo hours (along with other designated team members to help share the load)
  • Being willing to participate in media activities, e.g. photos, videos
ONS sponsor companies are of course welcome to host demos in their booths on the show floor as well. Please check with your ONS sponsorship manager to explore these opportunities. 

Submit your demo ideas by July 31st by sending an email to bwick@.... LFN staff leadership (Heather, Arpit) will then review the submissions, get back to submitters with questions/suggestions if needed, and recommend a final demo roster by August 14th. Send any questions you may have to bwick@....

We look forward to seeing your demo ideas.

Ed


Re: <module>-impl project code file generation

Michal Cmarada
 

Hi

 

This is all related to BGP so if you are not using BGP capabilities it is best to disable all modules for BGP. Take a look in infra/northbound/pom.xml. It contains northbound modules. You can remove bgp and bgp-extensions.

Also you may need to remove other BGP related stuff. In infra/pom.xml. you can remove modules for BGP too (bgp-translate-api, bgp-translate-impl, bgp-distribution-test). You may need to take a look in other pom.xml files and look for BGP. The advantage of disable for all modules will be faster builds, less code to maintain. Once rebuilt it should not contain any BGP capabilities anymore.

 

Michal

 

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


Re: <module>-impl project code file generation

saravanan.a75@wipro.com <saravanan.a75@...>
 

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


Re: <module>-impl project code file generation

saravanan.a75@wipro.com <saravanan.a75@...>
 

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


Re: <module>-impl project code file generation

Marek Grądzki <margradz@...>
 

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://tools.ietf.org/id/draft-varga-netconf-exi-capability-00.html#W3C.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://git.fd.io/honeycomb/tree/tools/archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/yang/__rootArtifactId__.yang

Here is relevant patch where you can find more info:
https://gerrit.fd.io/r/#/c/2429/

You can find more examples in:
https://docs.fd.io/honeycomb/1.18.10-SNAPSHOT/release-notes-aggregator/release_notes.html#_devel_guide
https://git.fd.io/honeycomb/tree/samples

Please also take a look at https://wiki.fd.io/view/Hc2vpp 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. www.wipro.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#816):
https://lists.fd.io/g/honeycomb-dev/message/816
Mute This Topic: https://lists.fd.io/mt/25070762/675181
Group Owner: honeycomb-dev+owner@...
Unsubscribe: https://lists.fd.io/g/honeycomb-dev/unsub
[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. www.wipro.com


Re: <module>-impl project code file generation

saravanan.a75@wipro.com <saravanan.a75@...>
 

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://tools.ietf.org/id/draft-varga-netconf-exi-capability-00.html#W3C.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://git.fd.io/honeycomb/tree/tools/archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/yang/__rootArtifactId__.yang

Here is relevant patch where you can find more info:
https://gerrit.fd.io/r/#/c/2429/

You can find more examples in:
https://docs.fd.io/honeycomb/1.18.10-SNAPSHOT/release-notes-aggregator/release_notes.html#_devel_guide
https://git.fd.io/honeycomb/tree/samples

Please also take a look at https://wiki.fd.io/view/Hc2vpp 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. www.wipro.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#816):
https://lists.fd.io/g/honeycomb-dev/message/816
Mute This Topic: https://lists.fd.io/mt/25070762/675181
Group Owner: honeycomb-dev+owner@...
Unsubscribe: https://lists.fd.io/g/honeycomb-dev/unsub
[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. www.wipro.com


Re: <module>-impl project code file generation

Michal Cmarada
 

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://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=tree;f=netconf/netconf-netty-util/src/main/java/org/opendaylight/netconf/nettyutil/handler/exi;h=bad12569de87e7ba9c666d5b21ed4bceffec5220;hb=refs/heads/master

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://tools.ietf.org/id/draft-varga-netconf-exi-capability-00.html#W3C.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://git.fd.io/honeycomb/tree/tools/archetype/src/main/resources/ar
chetype-resources/__rootArtifactId__-api/src/main/yang/__rootArtifactI
d__.yang

Here is relevant patch where you can find more info:
https://gerrit.fd.io/r/#/c/2429/

You can find more examples in:
https://docs.fd.io/honeycomb/1.18.10-SNAPSHOT/release-notes-aggregator
/release_notes.html#_devel_guide
https://git.fd.io/honeycomb/tree/samples

Please also take a look at https://wiki.fd.io/view/Hc2vpp 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. www.wipro.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#816):
https://lists.fd.io/g/honeycomb-dev/message/816
Mute This Topic: https://lists.fd.io/mt/25070762/675181
Group Owner: honeycomb-dev+owner@...
Unsubscribe: https://lists.fd.io/g/honeycomb-dev/unsub
[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. www.wipro.com


Re: <module>-impl project code file generation

saravanan.a75@wipro.com <saravanan.a75@...>
 

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://tools.ietf.org/id/draft-varga-netconf-exi-capability-00.html#W3C.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://git.fd.io/honeycomb/tree/tools/archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/yang/__rootArtifactId__.yang

Here is relevant patch where you can find more info:
https://gerrit.fd.io/r/#/c/2429/

You can find more examples in:
https://docs.fd.io/honeycomb/1.18.10-SNAPSHOT/release-notes-aggregator/release_notes.html#_devel_guide
https://git.fd.io/honeycomb/tree/samples

Please also take a look at https://wiki.fd.io/view/Hc2vpp 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. www.wipro.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#816):
https://lists.fd.io/g/honeycomb-dev/message/816
Mute This Topic: https://lists.fd.io/mt/25070762/675181
Group Owner: honeycomb-dev+owner@...
Unsubscribe: https://lists.fd.io/g/honeycomb-dev/unsub
[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. www.wipro.com


LF Service Desk ticketing changes

Trishan de Lanerolle
 

Service Desk migration

The Linux Foundation IT is migrating from email-based support system using Request Tracker to a web-based platform provided by Jira Service Desk. We are doing this in order to improve our level of service and your support experience.


The following are the primary improvements you should expect after migration is complete:


  1. Single Sign-On with other Linux Foundation sites, using the same LF ID credentials

  2. Integration with knowledge base articles to help identify possible self-service solutions

  3. Ability to track all your support requests across various projects via the same service desk interface

  4. Ability to see public issues created by other members of your project


The new service desk will become available to you starting Monday, June 17, 2019.


Any support requests that are already open in RT will be preserved and completed there, so there is no need to re-submit them again using the Jira Service Desk. Any new tickets created in RT will be automatically closed with a suggestion and instructions to use the new service desk procedure.


Starting Monday, June 17, please use the procedure described in the attached “Getting LF IT Help” document.


If you need help with anything IT-related for your FD.io project, please use our Service Desk
platform to open a support request: https://
support.linuxfoundation.org




Honeycomb & hc2vpp meeting

Peter Lapos
 

https://zoom.us/my/fastdata

 

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/5301185804 or https://zoom.us/my/fastdata

 

Or iPhone one-tap (US Toll):  +14086380968,,5301185804# or +16465588656,,5301185804#

 

Or Telephone:

    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)

    +1 855 880 1246 (US Toll Free)

    +1 877 369 0926 (US Toll Free)

    Meeting ID: 530 118 5804

    International numbers available: https://zoom.us/zoomconference?m=ppBOQMQTVxGYmbxNsVemC6KNo8eX2ptF

 


Honeycomb & hc2vpp meeting

Peter Lapos
 

https://zoom.us/my/fastdata

 

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/5301185804 or https://zoom.us/my/fastdata

 

Or iPhone one-tap (US Toll):  +14086380968,,5301185804# or +16465588656,,5301185804#

 

Or Telephone:

    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)

    +1 855 880 1246 (US Toll Free)

    +1 877 369 0926 (US Toll Free)

    Meeting ID: 530 118 5804

    International numbers available: https://zoom.us/zoomconference?m=ppBOQMQTVxGYmbxNsVemC6KNo8eX2ptF

 


Re: [discuss] Published: FD.io CSIT-1904 Benchmarking Report

Dave Wallace
 

Congratulations Maciek & the CSIT team as well as the greater FD.io communities.

Well done!
-daw-

On 5/10/2019 1:46 PM, Maciek Konstantynowicz (mkonstan) via Lists.Fd.Io wrote:

Hi All,

FD.io CSIT-1904 report has been published on FD.io docs site:

html: https://docs.fd.io/csit/rls1904/report/
pdf: https://docs.fd.io/csit/rls1904/report/_static/archive/csit_rls1904.pdf

Many thanks to All in CSIT, VPP and FD.io community who contributed and
worked hard to make CSIT-1904 happen!

FD.io VPP points of note in the report:

1. VPP release notes
   a. Changes in CSIT-1904: http://bit.ly/309V2oJ
   b. Known issues: http://bit.ly/2Q2K5AM

2. VPP performance graphs
   a. Throughput 64B frames: http://bit.ly/2VrdASG
   b. Speedup Multi-Core: http://bit.ly/2LAhjbS
   c. Latency: http://bit.ly/307AQUl

3. VPP performance comparisons
   a. VPP-19.04 vs. VPP-19.01: http://bit.ly/30ci12w
   b. Xeon Skylake vs. Xeon Haswell: http://bit.ly/2PWhLzT

4. VPP performance test details
   a. Detailed results 64B IMIX 1518B 9kB: http://bit.ly/2JuTjV3
   b. Configuration: http://bit.ly/2E4tvvA

DPDK Testpmd and L3fwd performance sections follow similar structure.

1. DPDK release notes:
  a. Changes in CSIT-1904: http://bit.ly/2VrOSBK
  b. Known issues: http://bit.ly/2VuO3ry

2. DPDK performance graphs for Testpmd and L3fwd demonstrator apps
  a. Throughput 64B frames: http://bit.ly/2Lxwa72
  b. Latency: http://bit.ly/2DZoKmO

Functional tests, including VPP_Device (functional device tests),
VPP_VIRL and HoneyComb are all included in the report.

Welcome all Comments, best by email to csit-dev@....

Cheers,
-Maciek
On behalf of FD.io CSIT Project

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#608): https://lists.fd.io/g/discuss/message/608
Mute This Topic: https://lists.fd.io/mt/31579561/675079
Group Owner: discuss+owner@...
Unsubscribe: https://lists.fd.io/g/discuss/unsub  [dwallacelf@...]
-=-=-=-=-=-=-=-=-=-=-=-


Published: FD.io CSIT-1904 Benchmarking Report

Maciek Konstantynowicz (mkonstan)
 

Hi All,

FD.io CSIT-1904 report has been published on FD.io docs site:

html: https://docs.fd.io/csit/rls1904/report/
pdf: https://docs.fd.io/csit/rls1904/report/_static/archive/csit_rls1904.pdf

Many thanks to All in CSIT, VPP and FD.io community who contributed and
worked hard to make CSIT-1904 happen!

FD.io VPP points of note in the report:

1. VPP release notes
a. Changes in CSIT-1904: http://bit.ly/309V2oJ
b. Known issues: http://bit.ly/2Q2K5AM

2. VPP performance graphs
a. Throughput 64B frames: http://bit.ly/2VrdASG
b. Speedup Multi-Core: http://bit.ly/2LAhjbS
c. Latency: http://bit.ly/307AQUl

3. VPP performance comparisons
a. VPP-19.04 vs. VPP-19.01: http://bit.ly/30ci12w
b. Xeon Skylake vs. Xeon Haswell: http://bit.ly/2PWhLzT

4. VPP performance test details
a. Detailed results 64B IMIX 1518B 9kB: http://bit.ly/2JuTjV3
b. Configuration: http://bit.ly/2E4tvvA

DPDK Testpmd and L3fwd performance sections follow similar structure.

1. DPDK release notes:
a. Changes in CSIT-1904: http://bit.ly/2VrOSBK
b. Known issues: http://bit.ly/2VuO3ry

2. DPDK performance graphs for Testpmd and L3fwd demonstrator apps
a. Throughput 64B frames: http://bit.ly/2Lxwa72
b. Latency: http://bit.ly/2DZoKmO

Functional tests, including VPP_Device (functional device tests),
VPP_VIRL and HoneyComb are all included in the report.

Welcome all Comments, best by email to csit-dev@....

Cheers,
-Maciek
On behalf of FD.io CSIT Project


Re: [hc2vpp] Honeycomb, HC2VPP Release 1904

Dave Wallace
 

Congratulations Michal. 

Well done!
-daw-

On 5/9/2019 2:25 AM, Michal Cmarada via Lists.Fd.Io wrote:

Hi Everyone,

 

Honeycomb and HC2VPP 1904 stable were successfully released.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

 

HC2VPP artifacts can be found on nexus:

https://nexus.fd.io/content/repositories/fd.io.release/io/fd/hc2vpp/

 

HC2VPP binary packages can be found on Package cloud:

https://packagecloud.io/app/fdio/release/search?q=honeycomb

 

Thanks to all contributors.

 

Michal

 



Michal Cmarada

Engineer - Software

mcmarada@...

Tel:

 

 

 


 



Cisco Systems, Inc.

 

 

 

Slovakia

cisco.com



Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.


 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#536): https://lists.fd.io/g/hc2vpp/message/536
Mute This Topic: https://lists.fd.io/mt/31552529/675079
Group Owner: hc2vpp+owner@...
Unsubscribe: https://lists.fd.io/g/hc2vpp/unsub  [dwallacelf@...]
-=-=-=-=-=-=-=-=-=-=-=-


Re: Honeycomb, HC2VPP Release 1904

Jerome Tollet
 

+1

 

De : <honeycomb-dev@...> au nom de "Peter Lapos via Lists.Fd.Io" <plapos=cisco.com@...>
Répondre à : "Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" <plapos@...>
Date : jeudi 9 mai 2019 à 09:17
À : "Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco)" <mcmarada@...>, "honeycomb-dev@..." <honeycomb-dev@...>, "hc2vpp@..." <hc2vpp@...>
Cc : "honeycomb-dev@..." <honeycomb-dev@...>
Objet : Re: [honeycomb-dev] Honeycomb, HC2VPP Release 1904

 

Great work, thank you Michal!

 

banner5

 

Peter Lapos

Project Manager

plapos@...

Tel:

Cisco Systems, Inc.

Apollo Business Centre II Prievozska 4D
BRATISLAVA
82109
Slovakia
cisco.com

 

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

From: hc2vpp@... <hc2vpp@...> On Behalf Of Michal Cmarada via Lists.Fd.Io
Sent: štvrtok, 9. mája 2019 8:26
To: honeycomb-dev@...; hc2vpp@...
Cc: hc2vpp@...
Subject: [hc2vpp] Honeycomb, HC2VPP Release 1904

 

Hi Everyone,

 

Honeycomb and HC2VPP 1904 stable were successfully released.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

 

HC2VPP artifacts can be found on nexus:

https://nexus.fd.io/content/repositories/fd.io.release/io/fd/hc2vpp/

 

HC2VPP binary packages can be found on Package cloud:

https://packagecloud.io/app/fdio/release/search?q=honeycomb

 

Thanks to all contributors.

 

Michal

 

 

Michal Cmarada

Engineer - Software

mcmarada@...

Tel:

 

 

 

 

Cisco Systems, Inc.

 

 

 

Slovakia

cisco.com

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

 


Re: Honeycomb, HC2VPP Release 1904

Peter Lapos
 

Great work, thank you Michal!

 

banner5

 

Peter Lapos

Project Manager

plapos@...

Tel:

Cisco Systems, Inc.

Apollo Business Centre II Prievozska 4D
BRATISLAVA
82109
Slovakia
cisco.com

 

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

From: hc2vpp@... <hc2vpp@...> On Behalf Of Michal Cmarada via Lists.Fd.Io
Sent: štvrtok, 9. mája 2019 8:26
To: honeycomb-dev@...; hc2vpp@...
Cc: hc2vpp@...
Subject: [hc2vpp] Honeycomb, HC2VPP Release 1904

 

Hi Everyone,

 

Honeycomb and HC2VPP 1904 stable were successfully released.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

 

HC2VPP artifacts can be found on nexus:

https://nexus.fd.io/content/repositories/fd.io.release/io/fd/hc2vpp/

 

HC2VPP binary packages can be found on Package cloud:

https://packagecloud.io/app/fdio/release/search?q=honeycomb

 

Thanks to all contributors.

 

Michal

 

 

Michal Cmarada

Engineer - Software

mcmarada@...

Tel:

 

 

 

 

Cisco Systems, Inc.

 

 

 

Slovakia

cisco.com

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

 


Honeycomb, HC2VPP Release 1904

Michal Cmarada
 

Hi Everyone,

 

Honeycomb and HC2VPP 1904 stable were successfully released.

Honeycomb artifacts can be found on nexus:
https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/

 

HC2VPP artifacts can be found on nexus:

https://nexus.fd.io/content/repositories/fd.io.release/io/fd/hc2vpp/

 

HC2VPP binary packages can be found on Package cloud:

https://packagecloud.io/app/fdio/release/search?q=honeycomb

 

Thanks to all contributors.

 

Michal

 

Michal Cmarada

Engineer - Software

mcmarada@...

Tel:

 

 

 

 

Cisco Systems, Inc.

 

 

 

Slovakia

cisco.com

Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Please click here for Company Registration Information.

 

 


Call for 2019 FD.io Internship Projects and Mentors

Trishan de Lanerolle
 

FD.io Technical Community,

We’re excited to open the call for the 2019 internship mentors and project ideas. We’re looking to sponsor four internship projects this year.

LFN Internships are for University or College students who are interested in contributing to real-world impactful Networking Open Source projects. Each intern will be working with a mentor from the FD.io project community to complete a project either in 3 months (full time 40 hours a week) or 6 months (part time 20 hours a week). This is a paid internship program that accepts applications throughout the year and the internship projects usually start on a quarterly schedule. As an open source project, each intern will work remotely from his or her location of choice.

If you’ve identified a project or task that’s suitable for an internship project and you’re interested in mentoring a student developer, please define the project by completing the internship project proposal template on the wiki by April 10th. (https://wiki.fd.io/view/Interns/Projects )

A few things to note as you plan to submit a project for consideration:
  • Multiple mentors supervising one intern per project would be desirable as this helps spread the workload and reduce the challenge of coverage caused by working remotely with an intern in a different time zone.
  • The mentor(s) need to be familiar with the project and is/are expected to directly supervise the intern’s technical work.
  • The proposed project needs to be clearly scoped and structured to be suitable for an internship project.
  • The project should be related to one of the current FD.io projects or tools.

Interns will be eligible to receive a stipend. The stipend will be paid in several installments provided that regular interval evaluations show the intern is making satisfactory progress. Additional details about LFN internships are available here

We look forward to your submission of a project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the FD.io community.

Regards,
Trishan












--
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle


Invitation to report out to the TSC

Trishan de Lanerolle
 

Hi,
The FD.io TSC would like to extend an invitation to community projects to provide a status updates on work, anticipated roadmap or any challenges they are working through. We hope this will be an opportunity to gain additional insights into the great work going on within our diverse community of projects. 

Please sign up for a slot and designate your project lead/representative for the meeting day of your choice.  


Anticipate one project to present per week.  A short presentation (10-12 minutes) during the weekly TSC call.  The TSC calls are always open to the community to attend. 

Regards, 
Trishan 





--
Trishan R. de Lanerolle
Program Manager,  Networking
Linux Foundation
voice: +1.203.699.6401
skype: tdelanerolle


Re: FD.io minisummit at Kubecon EU (May 21-23, Barcelona)

Edward Warnicke
 

+ hicn and sweetcomb, who's lists were misconfigured the first time I sent it :)

Ed

On Thu, Feb 21, 2019 at 1:04 PM Ed Warnicke <hagbard@...> wrote:
Traditionally in the past FD.io has held collocated minisummits at Kubecon (NA and EU).

We are fortunate to have budget to do Kubecon EU, Kubecon NA, and one other collocated event (probably best to be held in Asia and possibly at an embedded event).

In the course of discussing this, the FD.io Marketing group felt that doing a separate FD.io booth at Kubecon EU was a clear win, but raised the question:

- Is there a better choice for an EU event to collocate with for the FD.io minisummit?

This is a good question, and so wanted to open the discussion to the broader community, as it differs from what had previously been discussed in the community and decided on.

So, thoughts?  Opinions?  Ideas?

Ed

21 - 40 of 906