Re: [netvirt-dev] The correct approach to integrate NetVirt own sub-module into ODL?

Sam Hague <shague@...>

On Tue, Aug 7, 2018 at 11:51 AM Irving <418624178@...> wrote:

I build my own distribution of ODL as RPM package for deployment. The situation goes like:

1. Build my own sub-module for HWvTEP L3 support under netvirt.

2. Re-modified topology-manager under openflowplugin for DLUX displaying multi-layer topology (VM, OvS, ToR, and other layers).

3. There are other re-modified patches under Genius ITM and OVSDB. But their location are flexible, I haven't decide yet (could do it in some Genius util classes, or netvirt own sub-module).

So I try to build different RPMs for each project (controller, netvirt, Openflowplugin, ovsdb), than I am able to use RPMs for integration. However it looks like a dead-end.

Anyone has ideas about how to integrate multi re-modifications cross multi projects in ODL? Or should I try to integrate the codes as a all-in-one sub-module for deployment via RPM?
Do you need separate RPMs per module? Or can you just built a typical ODL zip and use that? If the latter, then you can just keep your branches per projects, along with patches and just build a distribution. That's all ODL is today. Build all your modules one by one with netvirt last. netvirt will build a karaf distribution with all the project artifacts just built.

netvirt-dev mailing list

Join { to automatically receive all group messages.