Re: [openflowplugin-dev] [sfc-dev] [netvirt-dev] Enabling netvirt karaf4 and dependencies in integration/distribution

Hi Luis, I can do it for OVSDB, Genius and Netvirt and others with a bit of help. I have some questions/doubts on what all needs to be done, so will probably raise a patch for OVSDB first as an exercise. Regards, Vishal. From: Luis Gomez [mailto:ece...@gmail.com] Sent: 28 June 2017 02:15 To: A

Re: [openflowplugin-dev] [sfc-dev] [netvirt-dev] Enabling netvirt karaf4 and dependencies in integration/distribution

If someone knows enough about all these projects to do a single patch, please go ahead. This will save integration work. > On Jun 26, 2017, at 10:51 PM, Anil Vishnoi wrote: > > Option 2 might be quicker than option 1, but probably it's good to consult > integration team for their opinion. >

Re: [openflowplugin-dev] [openflowjava-dev] OpenFlow Plugin and OpenFlow Java Library

Perfect :) Ed On Tue, Jun 27, 2017 at 11:15 AM, Abhijit Kumbhare wrote: > Agree with you Ed about having a vote in OpenFlow Java committer community > - and in general the TSC role if we plan to archive. Had planned on that > based on how we have decided to proceed (based on Tomas's study of im

Re: [openflowplugin-dev] [openflowjava-dev] OpenFlow Plugin and OpenFlow Java Library

Agree with you Ed about having a vote in OpenFlow Java committer community - and in general the TSC role if we plan to archive. Had planned on that based on how we have decided to proceed (based on Tomas's study of impact). Unfortunately I have been offline for periods of time during the last week

Re: [openflowplugin-dev] [openflowjava-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

So looks like we don't need a TSC approval for this merge. Only committers needs to agree on it. Though it's good to have an official vote from openflowjava committer about this merger. So i think overall we are good. On Tue, Jun 27, 2017 at 10:46 AM, Anil Vishnoi wrote: > Just for a my clarity,

Re: [openflowplugin-dev] [openflowjava-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

Just for a my clarity, merging these two project won't require TSC approval and permission from the openflowjava project PTL/Committer? I think we have the latter, but not the first if requires. On Tue, Jun 27, 2017 at 10:42 AM, Tomáš Slušný wrote: > Hi Michal, > > > these conflicts can be resol

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

Hi Michal, these conflicts can be resolved by using git subtree instead of git merge, as subtree can "merge" repository/branch into subdirectory. I prepared this OpenFlowJava merge in 3 patches, first one is just adding OpenFlowJava to subdirectory "openflowjava", second one is actually to int

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

Yes please open a helpdesk ticket for this. I see 2 routes we can go from there: 1) Ask LF to do it 2) LF gives committers temporary push permissions and they can do it themselves I think 1) might give LF more comfort though. Regards, Thanh On Tue, Jun 27, 2017 at 10:11 AM, Michal Rehak -X (mir

Re: [openflowplugin-dev] Inconsistency between flows in config, operational, and the OVS bridge

Im bumping this thread, since I never heard back about it. Brady -Original Message- From: Brady Allen Johnson mailto:brady%20allen%20johnson%20%3cbrady.allen.john...@ericsson.com%3e>> To: openflowplugin-dev@lists.opendaylight.org mailto:%22openflowplugin-...@lists.opendaylight.org%22%2

Re: [openflowplugin-dev] [openflowjava-dev] OpenFlow Plugin and OpenFlow Java Library

Abhijit, This strikes me as good news overall. It might be a good idea to get a vote from the OpenflowJava Committers, particularly as they will need to vote to archive the openflowjava project, and it also makes everything very clear. As to the TSCs role, it has one for archiving the ope

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

Hi all, merging ofjava with ofplugin yields some conflicts: Conflicts: .gitignore .gitreview artifacts/pom.xml parent/pom.xml pom.xml .git* and aggregate/pom are trivial to solve. Inspecting artifacts/pom and parent/pom I came to conclusion that decision

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

On 27/06/17 12:52, Tomáš Slušný wrote: > Hello Robert, > > > I can import OpenFlowJava using `git subtree` to not lose history (and I > actually have it already prepared in my local repository, because that > was first thing I tried), but then it would create Gerrit patch for each > OpenFlowJava

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

HI all, just thoughts we can still keep the history in frozen project, with the description on the first commit that the projects were merged together. And with the information where the old history can be found. If I am not wrong merging two repositories with git subtree creates a huge amo

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

Hello Robert, I can import OpenFlowJava using `git subtree` to not lose history (and I actually have it already prepared in my local repository, because that was first thing I tried), but then it would create Gerrit patch for each OpenFlowJava commit if I am not wrong. Or is there another meth

Re: [openflowplugin-dev] [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

On 27/06/17 12:13, Tomáš Slušný wrote: > > > https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen > > > OpenFlowJava being merged into OpenFlowPlugin in Nitrogen[edit > >

[openflowplugin-dev] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen OpenFlowJava being merged into OpenFlowPlugin in Nitrogen[edit] * Description: Merge OpenFlowJava into OpenFlowPlugin

Re: [openflowplugin-dev] Proposed Reconciliation framework

Sorry for jumping late on this thread. Very productive discussion. I do understand the need of offloading the flow/group/meter reconciliation to the application, given that they know their business logic and they know what all flows need to be installed. But i see some discussion about the priorit