Date   

Problem developing generic plugin

mrsebastienpradier@...
 

Hello,

I'm working on SDN network with ONOS and I've a problem developing the generic plugin.
I've installed maven and when I'm typing this command : mvn -X archetype:generate -DarchetypeGroupId=io.fd.honeycomb.tools -DarchetypeArtifactId=honeycomb-plugin-archetype -DarchetypeVersion=1.19.01
It sends me an error (I've linked the error) and when I check the reasons it tells me that the error comes from the plugin and not from maven.

Does somebody has had the same error and is able to help me ?

Thank you !
Sébastien Pradier.


Re: FD.io - Decommission SonarQube Instance

Vanessa Valderrama
 

Reminder

On 7/14/20 2:40 PM, Vanessa Valderrama wrote:

What:  LF will decomission the FD.io SonarQue instance

When:   2020-07-22 at 1700 UTC

Impact:  sonar.fd.io and code quality reports and history will no longer be accessible

Why:  LF has migrated to SonarCloud. All FD.io project yaml files have been configured for SonarCloud jobs.

Thank you,
Vanessa


FD.io - Decommission SonarQube Instance

Vanessa Valderrama
 

What:  LF will decomission the FD.io SonarQue instance

When:   2020-07-22 at 1700 UTC

Impact:  sonar.fd.io and code quality reports and history will no longer be accessible

Why:  LF has migrated to SonarCloud. All FD.io project yaml files have been configured for SonarCloud jobs.

Thank you,
Vanessa


Re: SonarQube Question

Jerome Tollet
 

I don't think we need it.
Jerome

Le 15/06/2020 22:45, « honeycomb-dev@... au nom de Vanessa Valderrama » <honeycomb-dev@... au nom de vvalderrama@...> a écrit :

LF is migrating from SonarQube to SonarCloud. Does Honeycomb need the
history in sonar.fd.io?

Thank you,
Vanessa


SonarQube Question

Vanessa Valderrama
 

LF is migrating from SonarQube to SonarCloud. Does Honeycomb need the
history in sonar.fd.io?

Thank you,
Vanessa


Reminder Deadline Feb 28th: Invitation for FD.io Project Proposals to LFN Mentorship Program

Trishan de Lanerolle
 

We’re excited to open the call for mentors and project proposals for the 2020 LF Networking Mentorship Program. This is the first year we're bringing all community intern/mentor projects, under an integrated program schedule. This is intended to provide a formal structure to connect mentors and student developers from around the globe, to contribute their enthusiasm, time, and experience toward building sustainable LFN communities.

  I am interested in mentoring but how do I get started? 

Why should you consider mentoring for LF Networking Mentorship Program?
  • You believe in the value of mentorship in helping new developers to navigate open source development, the culture, the tooling and infrastructure to be a productive member of the community.  
  • You are passionate about teaching and guiding student developers, many of whom may be first time open-source contributors, 
  • You are eager to bring in new perspectives, new ideas, and new talent into your community and projects.
  • You have a narrowly scoped mentorship project with clear learning objectives/outcomes and a mentee's work and potential contributions could add value to the project or community of which you're an active developer or maintainer.     

What are the elements the LFN Mentorship Program will implement to maximize mentor/mentee collaboration success?
  • Mentor and mentee onboarding will be conducted at the start of the Program
  • Mentor and mentee guide will be available as part of the Linux Foundation CommunityBridge Mentorship initiative
  • Project planning that includes deliverables, milestones, and tasks will be completed collaboratively between the mentors and mentees during the first two weeks of the program and posted on the wiki to increase transparency and accountability.
  • Mentee presentations will be required to sharpen both presentation skills and to cultivate the ability to provide constructive feedback and critique that’s the norm in the open source community for developing technologies collaboratively and openly.
  • Mentee evaluation will be conducted on a regular cadence tied to milestone deliverable schedules to help mentors and LFN staff formalize and respond to progress.
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD but will be during Q3 or Q4 of this year or Q1 of the following year).

If you have any questions, please contact mentorship@...

We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities.

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


Invitation for FD.io Project Proposals to LFN Mentorship Program

Trishan de Lanerolle
 

We’re excited to open the call for mentors and project proposals for the 2020 LF Networking Mentorship Program. This is the first year we're bringing all community intern/mentor projects, under an integrated program schedule. This is intended to provide a formal structure to connect mentors and student developers from around the globe, to contribute their enthusiasm, time, and experience toward building sustainable LFN communities.

  I am interested in mentoring but how do I get started? 

Why should you consider mentoring for LF Networking Mentorship Program?
  • You believe in the value of mentorship in helping new developers to navigate open source development, the culture, the tooling and infrastructure to be a productive member of the community.  
  • You are passionate about teaching and guiding student developers, many of whom may be first time open-source contributors, 
  • You are eager to bring in new perspectives, new ideas, and new talent into your community and projects.
  • You have a narrowly scoped mentorship project with clear learning objectives/outcomes and a mentee's work and potential contributions could add value to the project or community of which you're an active developer or maintainer.     

What are the elements the LFN Mentorship Program will implement to maximize mentor/mentee collaboration success?
  • Mentor and mentee onboarding will be conducted at the start of the Program
  • Mentor and mentee guide will be available as part of the Linux Foundation CommunityBridge Mentorship initiative
  • Project planning that includes deliverables, milestones, and tasks will be completed collaboratively between the mentors and mentees during the first two weeks of the program and posted on the wiki to increase transparency and accountability.
  • Mentee presentations will be required to sharpen both presentation skills and to cultivate the ability to provide constructive feedback and critique that’s the norm in the open source community for developing technologies collaboratively and openly.
  • Mentee evaluation will be conducted on a regular cadence tied to milestone deliverable schedules to help mentors and LFN staff formalize and respond to progress.
While mentors will be on a voluntary basis, the hired mentees will be eligible to receive a stipend. As an added bonus, each mentee who successfully completes the Program will be invited and financially sponsored by LF Networking to attend an event/conference and present their work to the broader community (specific event TBD but will be during Q3 or Q4 of this year or Q1 of the following year).

If you have any questions, please contact mentorship@...

We look forward to your submission of a mentorship project and thank you in advance for volunteering your time to contribute to the training of the new talent pool in the LF Networking communities.

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


Final call: removing HoneyComb tests from CSIT master [Was: Honeycomb test code in CSIT - status and way forward]

Maciek Konstantynowicz (mkonstan)
 

Hi,

Honeycomb code is about to be removed from CSIT repo.

Thanks to Peter Mikus for preparing this patch: https://gerrit.fd.io/r/c/csit/+/23363

We are looking to merge this patch before embarking on Python 3.x migration next week, as discussed on CSIT weekly call.

Let us know if any issues with above.

Cheers,
-Maciek

On 5 Sep 2019, at 09:09, Michal Cmarada <michal.cmarada@...> wrote:

Hi,

I am not aware of any plans for Honeycomb. Try asking Jerome and Peter directly.

Michal

-----Original Message-----
From: Maciek Konstantynowicz (mkonstan) via Lists.Fd.Io <mkonstan=cisco.com@...>
Sent: Tuesday, September 3, 2019 6:00 PM
To: honeycomb-dev <honeycomb-dev@...>
Cc: csit-dev@...
Subject: [csit-dev] Honeycomb test code in CSIT - status and way forward

Hi honeycomb-dev,

We need advice what to do with honeycomb test code in CSIT.

AFAICT there is no honeycomb release for VPP v19.08, so no honeycomb tests are running in CSIT-1908 release (they were running in CSIT-1904).

Are there plans to update honeycomb code to align with VPP v19.08, and adjust honeycomb tests in CSIT accordingly?

Cheers,
-Maciek




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

View/Reply Online (#892): https://lists.fd.io/g/honeycomb-dev/message/892
Mute This Topic: https://lists.fd.io/mt/33128143/675185
Group Owner: honeycomb-dev+owner@...
Unsubscribe: https://lists.fd.io/g/honeycomb-dev/unsub  [mkonstan@...]
-=-=-=-=-=-=-=-=-=-=-=-


Re: apache maven wagon

Vanessa Valderrama
 

I've complied the list of jobs and pom files that are pinning version wagon 2.9. Please upgrade or unpin the version of wagon.

Here's the search used to compile the list
https://github.com/search?p=1&q=org%3AFDio+wagon-webdav-jackrabbit&type=Code

CSIT

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/csit/csit.yaml
   - jobs calling the script
     csit-docs-merge-{stream_timed}

Script
 - https://github.com/FDio/ci-management/blob/8acba0b988a3a6220340df3b0d79451fb52e93e9/jjb/csit/include-raw-csit-docs.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/csit/csit.yaml
   - jobs calling the script
     csit-report-merge-{stream}

Script
 - https://github.com/FDio/ci-management/blob/8acba0b988a3a6220340df3b0d79451fb52e93e9/jjb/csit/include-raw-csit-report.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/csit/csit.yaml
   - jobs calling scripts
     csit-trending-daily-master

Script
 - https://github.com/FDio/ci-management/blob/77a5851cb279501c101e42df35d501f8afc14135/jjb/csit/include-raw-csit-cpta.sh

NSH_SFC

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/nsh_sfc/nsh_sfc.yaml
   - jobs calling the script
     nsh_sfc-merge-docs-{stream}
     nsh_sfc-verify-docs-{stream}

Script
 - https://github.com/FDio/ci-management/blob/8acba0b988a3a6220340df3b0d79451fb52e93e9/jjb/nsh_sfc/include-raw-nsh_sfc-docs.sh

VPP

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/vpp/vpp.yaml
   - jobs calling the script
     vpp-docs-merge-{stream}
     vpp-docs-verify-{stream}

Script
 - https://github.com/FDio/ci-management/blob/0c7d6e34945abfd03fe965ee4bbeaa7c290379dc/jjb/vpp/include-raw-vpp-docs.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/vpp/docs.yaml
   - jobs calling the script
     vpp-docs-verify-{stream}
     vpp-docs-merge-{stream}

Script
 - https://github.com/FDio/ci-management/blob/0c7d6e34945abfd03fe965ee4bbeaa7c290379dc/jjb/vpp/include-raw-vpp-docs.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/vpp/docs.yaml
   - jobs calling the script
     vpp-docs-merge-{stream}
     vpp-sphinx-docs-merge-{stream}

Script
 - https://github.com/FDio/ci-management/blob/0c7d6e34945abfd03fe965ee4bbeaa7c290379dc/jjb/vpp/include-raw-vpp-sphinx-docs.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/vpp/docs.yaml
   - jobs calling the script
     vpp-make-test-docs-verify-{stream}
     vpp-make-test-docs-merge-{stream}

Script
 - https://github.com/FDio/ci-management/blob/2cf6f067c034ab1544d96b286358c4c46484cd62/jjb/vpp/include-raw-vpp-make-test-docs.sh

CICN

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/cicn/cicn.yaml
   - jobs calling script
     cicn-libparc-docs-merge-{stream}
     cicn-libparc-docs-verify-{stream}

Script
 - https://github.com/FDio/ci-management/blob/8acba0b988a3a6220340df3b0d79451fb52e93e9/jjb/cicn/include-raw-cicn-libparc-docs.sh

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/cicn/cicn.yaml
   - jobs calling script
     cicn-longbow-docs-merge-{stream}
     cicn-longbow-docs-verify-{stream}

Script
 - https://github.com/FDio/ci-management/blob/8acba0b988a3a6220340df3b0d79451fb52e93e9/jjb/cicn/include-raw-cicn-longbow-docs.sh

HICN

Job configuration
 - https://git.fd.io/ci-management/tree/jjb/hicn/hicn-docs.yaml
   - jobs calling scripts
     hicn-docs-verify-{stream}
     hicn-docs-merge-{stream}

Script
 - https://github.com/FDio/ci-management/blob/eadf733ffe3c679e2eaaff83f2929c61d0f5daf5/jjb/hicn/include-raw-hicn-docs.sh

Honeycomb

https://github.com/FDio/honeycomb/blob/a776d7ff3e6f155a37b182dabaa0429fb2c04c3c/common/honeycomb-parent/pom.xml

        <!-- To support site push-->
        <extensions>
            <extension>
                <groupId>org.apache.maven.wagon</groupId>
                <artifactId>wagon-webdav-jackrabbit</artifactId>
                <version>2.9</version>
            </extension>
        </extensions>
    </build>

Thank you,
Vanessa

On 10/15/2019 03:17 PM, Vanessa Valderrama wrote:
Please modify build scripts and pom files to use apache maven wagon
version 3.x. Previous versions appear to conflict with Nexus causing
java.net.SocketTimeoutException: Read timed out errors.

Thank you,

Vanessa




apache maven wagon

Vanessa Valderrama
 

Please modify build scripts and pom files to use apache maven wagon
version 3.x. Previous versions appear to conflict with Nexus causing
java.net.SocketTimeoutException: Read timed out errors.

Thank you,

Vanessa


VPP 19.08 artifacts deferral notice and 19.08.1 schedule

Dave Wallace
 

Dear FD.io Project Members,

[ Note: FD.io <project>-dev email lists BCC'd to reduce noise ]

As discussed in this week's VPP Bi-Weekly Community Meeting, there
is the necessity to introduce a critical fix that breaks VPP API
compatibility. Therefore we need to defer ALL 19.08 release artifacts
and publish 19.08.1 as soon as practicable.

We apologize in advance for this inconvenience. The details are
in the VPP 19.08.1 release note change set [0].

We plan to merge the API-breaking fix into stable/1908 on Monday
9 September 2019 at 9am CET, and would like to cut the VPP 19.08.1
release on Thursday 12 September. The timing is rather tight to
avoid accumulating too many additional commits to stable/1908 and
to minimize the changes between 19.08 and 19.08.1.

Please review the release note change set [0] and add yourself as
a reviewer to be informed of any changes to the plan.

PTLs, please indicate that your project is okay with these dates or
add your desired dates on-gerrit and save the changes to [0].

We would also kindly ask that even if you are okay with these dates,
that you add 1 or 2 persons from your project as reviewers to [0],
to be able to efficiently communicate any changes to the plan to all
interested project teams.

Thanks,
Andrew & Dave
"Your Friendly VPP Release Managers"

[0] https://gerrit.fd.io/r/#/c/vpp/+/21829/


Re: Honeycomb test code in CSIT - status and way forward

Michal Cmarada
 

Hi,

I am not aware of any plans for Honeycomb. Try asking Jerome and Peter directly.

Michal

-----Original Message-----
From: Maciek Konstantynowicz (mkonstan) via Lists.Fd.Io <mkonstan=cisco.com@...>
Sent: Tuesday, September 3, 2019 6:00 PM
To: honeycomb-dev <honeycomb-dev@...>
Cc: csit-dev@...
Subject: [csit-dev] Honeycomb test code in CSIT - status and way forward

Hi honeycomb-dev,

We need advice what to do with honeycomb test code in CSIT.

AFAICT there is no honeycomb release for VPP v19.08, so no honeycomb tests are running in CSIT-1908 release (they were running in CSIT-1904).

Are there plans to update honeycomb code to align with VPP v19.08, and adjust honeycomb tests in CSIT accordingly?

Cheers,
-Maciek


Published: FD.io CSIT-1908 Release Report

Maciek Konstantynowicz (mkonstan)
 

Hi All,

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

html: https://docs.fd.io/csit/rls1908/report/
pdf: https://docs.fd.io/csit/rls1908/report/_static/archive/csit_rls1908.pdf

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

Below two summaries:
- CSIT-1908 Release Summary, a high-level summary.
- Points of Note in CSIT-1908 Report, with specific links to report.

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

Cheers,
-Maciek

------------------------------------------------------------------------
CSIT-1908 Release Summary
------------------------------------------------------------------------
1. CSIT-1908 Report

- html link: https://docs.fd.io/csit/rls1908/report/
- pdf link: https://docs.fd.io/csit/rls1908/report/_static/archive/csit_rls1908.pdf

2. New Tests

- VM/VNF service chains with DPDK Testpmd and VPP L2/IPv4 workloads
and external VXLAN encapsulation.
- IPsec with new VPP native cipher algorithms, baseline and large
scale (up to 60k tunnels).
- VM/VNF service chains with VPP IPsec workloads, baseline and
horizontal scaling (experimental, in-testing).
- GBP (Group Based Policy) with external dot1q encapsulation.
- Extended test coverage with VPP native AVF driver: IPv4 scale tests.
- Refreshed VPP TCP/HTTP tests.
- Number of VPP functional device tests running in container based
environment.
- Good VPP PAPI (Python API) test coverage, PAPI used for all VPP
tests.

3. Benchmarking

- Added new processor micro-architectures: ARM/AArch64 (TaiShan) and
Atom (Denverton).

- New testbeds onboarded into FD.io CSIT CI/CD functional and
performance test pipelines.
- Daily trending with throughput changes monitoring, analytics and
anomaly auto-detection.
- Release reports with benchmarking data including throughput,
latency, test repeatibility.

- Updated CSIT benchmarking report specification

- Consistent selection of tests across all testbeds and processor
microarchitectures present in FD.io labs (Xeon, Atom, ARM) for
iterative benchmarking tests to verify results repeatibility. Data
presented in graphs conveying NDR (non-drop rate, zero packet
loss) and PDR (partial drop rate) throughput statistics.
Multi-core speedup and latency are also presented.
- Consistent comparison of NDR and PDR throughput results across the
releases.
- Updated graph naming and test grouping to improve browsability and
access to test data.

- Increased test coverage in 2-node testbed environment (2n-skx).

- Updated soak testing methodology and new results, aligned with
latest IETF draft specification draft-vpolak-bmwg-plrsearch-02.

4. Infrastructure

- API
- PAPI (Python API) used for all VPP tests, migrated away from VAT
(VPP API Test).
- VPP API change detection and gating in VPP and CSIT CI/CD.

- Test Environments
- VPP functional device tests: migrated away from VIRL (VM based) to
container environment (with Nomad).
- Added new physical testbeds: ARM/AArch64 (TaiShan) and Atom
(Denverton).

- CSIT Framework
- Conifguration keyword alignment across 2-node and 3-node testbeds to
ease test portability across environments.

- Installer
- Updated bare-metal CSIT performance testbed installer (ansible).

------------------------------------------------------------------------
Points of Note in CSIT-1908 Report
------------------------------------------------------------------------
Indexed specific links listed at the bottom.

1. VPP release notes
a. Changes in CSIT-1908: [1]
b. Known issues: [2]

2. VPP performance - 64B/IMIX throughput graphs (selected NIC models):
a. Graphs explained: [3]
b. L2 Ethernet Switching: [4]
c. IPv4 Routing: [5]
d. IPv6 Routing: [6]
e. SRv6 Routing: [7]
f. IPv4 Tunnels: [8]
g. KVM VMs vhost-user: [9]
h. LXC/DRC Container Memif: [10]
e. IPsec IPv4 Routing: [11]
f. Virtual Topology System: [12]

3. VPP performance - multi-core and latency graphs:
a. Speedup Multi-Core: [13]
b. Latency: [14]

4. VPP system performance - NFV service density and TCP/IP:
a. VNF (VM) Service Chains: [15]
b. CNF (Container) Service Chains: [16]
c. CNF (Container) Service Pipelines: [17]
d. HTTP and TCP/IP: [18]

4. VPP performance comparisons
a. VPP-19.08 vs. VPP-19.04: [19]

5. VPP performance test details - all NICs:
a. Detailed results 64B IMIX 1518B 9kB: [20]
b. Configuration: [21]

DPDK Testpmd and L3fwd performance sections follow similar structure.

6. DPDK applications:
a. Release notes: [22]
b. DPDK performance - 64B throughput graphs: [23]
c. DPDK performance - latency graphs: [24]
d. DPDK performance - DPDK-1905 vs. DPDK-19.01: [25]

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

Specific links within the report:

[1] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/csit_release_notes.html#changes-in-csit-release
[2] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/csit_release_notes.html#known-issues
[3] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/index.html
[4] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/l2.html
[5] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/ip4.html
[6] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/ip6.html
[7] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/srv6.html
[8] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/ip4_tunnels.html
[9] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/vm_vhost.html
[10] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/container_memif.html
[11] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/ipsec.html
[12] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_throughput_graphs/vts.html
[13] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/throughput_speedup_multi_core/index.html
[14] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/packet_latency_graphs/index.html
[15] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/nf_service_density/vnf_service_chains.html
[16] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/nf_service_density/cnf_service_chains.html
[17] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/nf_service_density/cnf_service_pipelines.html
[18] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/http_server_performance/index.html
[19] https://docs.fd.io/csit/rls1908/report/vpp_performance_tests/comparisons/current_vs_previous_release.html
[20] https://docs.fd.io/csit/rls1908/report/detailed_test_results/vpp_performance_results/index.html
[21] https://docs.fd.io/csit/rls1908/report/test_configuration/vpp_performance_configuration/index.html
[22] https://docs.fd.io/csit/rls1908/report/dpdk_performance_tests/csit_release_notes.html
[23] https://docs.fd.io/csit/rls1908/report/dpdk_performance_tests/packet_throughput_graphs/index.html
[24] https://docs.fd.io/csit/rls1908/report/dpdk_performance_tests/packet_latency_graphs/index.html
[25] https://docs.fd.io/csit/rls1908/report/dpdk_performance_tests/comparisons/current_vs_previous_release.html
------------------------------------------------------------------------


Honeycomb test code in CSIT - status and way forward

Maciek Konstantynowicz (mkonstan)
 

Hi honeycomb-dev,

We need advice what to do with honeycomb test code in CSIT.

AFAICT there is no honeycomb release for VPP v19.08, so no honeycomb
tests are running in CSIT-1908 release (they were running in CSIT-1904).

Are there plans to update honeycomb code to align with VPP v19.08, and
adjust honeycomb tests in CSIT accordingly?

Cheers,
-Maciek


Does honeycomb support call-home feature,How is it configured?Thanks

dengxunaaa@...
 

Does honeycomb support call-home feature,How is it configured?Thanks


A question about honeycomb startup, thanks

dengxunaaa@...
 

when i start by excute ./sh /home/hc2vpp/vpp-integration-distribution-1.19.04/honeycomb
there is an error below occur。How can i solve the problem ? thanks for answer


2019-07-31 01:09:30.413 UTC [main] INFO  i.f.h.binding.init.ProviderTrait - Providing: io.fd.honeycomb.infra.distro.data.PersistingDataTreeProvider$ConfigPersistingDataTreeProvider@6ec3a4c2
2019-07-31 01:09:30.422 UTC [main] INFO  i.f.h.binding.init.ProviderTrait - Providing: io.fd.honeycomb.infra.distro.data.ShutdownHandlerProvider@6cd66f6a
2019-07-31 01:09:30.425 UTC [main] INFO  i.f.h.binding.init.ProviderTrait - Providing: io.fd.hc2vpp.common.integration.JVppRegistryProvider@48ee3c2d
Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/libjvpp_registry.so1524549794623320926.tmp: libvppinfra.so.19.04: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824)
at java.lang.Runtime.load0(Runtime.java:809)
at java.lang.Runtime.load(Runtime.java:797)
at io.fd.jvpp.NativeLibraryLoader.loadStream(NativeLibraryLoader.java:62)
at io.fd.jvpp.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:53)
at io.fd.jvpp.VppJNIConnection.<clinit>(VppJNIConnection.java:41)
at io.fd.jvpp.JVppRegistryImpl.<init>(JVppRegistryImpl.java:45)
at io.fd.hc2vpp.common.integration.JVppRegistryProvider.create(JVppRegistryProvider.java:61)
at io.fd.hc2vpp.common.integration.JVppRegistryProvider.create(JVppRegistryProvider.java:41)
at io.fd.honeycomb.binding.init.ProviderTrait.get(ProviderTrait.java:30)
at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
 


FD.io - Gerrit 2.16 Changes

Vanessa Valderrama
 

Changes that will happen with Gerrit:

1) The 'New UI' for Gerrit will become the default UI

2) The Draft work flow is removed and replaced with 'Work in Progress'
aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
support either of these workflows directly. Utilizing them means either
pushing your changes the manual way for either system or pushing them up
with git-review and then marking the change via the UI into either of
the workflows.

To push a private change you may do so as follows:
git push origin HEAD:refs/for/master%private

To pull it out of private you may do so as follows:
git push origin HEAD:refs/for/master%remove-private

To push a WIP you may do so as follows:
git push origin HEAD:refs/for/master%wip

To mark it ready for review you may do so as follows:
git push origin HEAD:refs/for/master%ready

Once a change is in either private or WIP state it does not switch the
change to a ready state until the current state has been removed.

In both cases, the state can be set via the UI by selecting the tripple
dot menu option on the change and selecting the appropriate option.

To remove WIP state press the 'START REVIEW' button. To remove the
private state you must do so via the menu.

NOTE: We are not moving to Gerrit 3 at this time. That is on the road
map but we need to come to the latest 2.x as we have to do various
migrations that are only available at the 2.16 level before we can move
to Gerrit 3.

Thank you,
Vanessa


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