Date   

Re: OPENFLOWJAVA Nitrogen Status

Michal Rehák <michal.rehak@...>
 


Hi An,

apologies for late answer. As per [1] and [2] the project openflowjava will be absorbed by project openflowplugin during Nitrogen release.

Based on that openflowjava project intends to drop from Nitrogen Simultaneous Release.

I guess there are still some open questions regarding git history, documentation and openflowjava committers. But these are rather technical details which can be resolved later.


Based on further discussions I created termination proposal for openflowjava project [3]



Regards,

Michal


[1] https://lists.opendaylight.org/pipermail/openflowplugin-dev/2017-June/007276.html

[2] https://lists.opendaylight.org/pipermail/openflowplugin-dev/2017-June/007379.html

[3] https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Termination_Proposal


--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech


From: An Ho <An.Ho@...>
Sent: Saturday, June 24, 2017 1:30:02 AM
To: Colin Dixon; Casey Cain; openflowjava-dev@...; Michal Rehák
Subject: OPENFLOWJAVA Nitrogen Status
 
Hi Michal Rehak and OPENFLOWJAVA Team,

We would like to express our appreciation for your contribution to the Carbon Simultaneous Release and the wonderful innovations your team has brought to the OpenDaylight Project and its community.

We have not heard from your project regarding your intent to participate in the Nitrogen Simultaneous Release [1] which was due on June 21, 2017 [2].  Please take a moment to confirm if your project intends to drop from the Nitrogen Simultaneous Release.  We will assume your project does not intend to participate in the Nitrogen Simultaneous Release if we do not hear back by the end of this week.

Please note that projects participating in the Nitrogen Simultaneous Release are required to complete the Nitrogen Simultaneous Release Plan Requirements [3] as well as the Nitrogen Karaf 4 Migration Requirements [5], including:

* local karaf 4 distribution: projects build local karaf 4 distribution
** create karaf 4 features and local karaf 4 distribution
** test, and identify blocking issues
** examples: https://git.opendaylight.org/gerrit/#/c/55160/ (support only karaf 4) or https://git.opendaylight.org/gerrit/#/c/58726/ (support karaf 3 and karaf 4)
** create bugzilla issue such as https://bugs.opendaylight.org/show_bug.cgi?id=8638 and make it block https://bugs.opendaylight.org/show_bug.cgi?id=4219
* odlparent version 2: projects migrate themselves to odlparent version 2.0.0
** This means removing your Karaf 3 features (because odlparent 2.0.0 will not support Karaf 3 anymore)
** projects should make some minor adjustments in the code related to the switch to a newer Guava version.
* add to integration distribution: projects to add their karaf 4 features to integration distribution as per https://wiki.opendaylight.org/view/Karaf_4_migration#Step_7:_add_your_karaf_4_features_to_distribution

Best Regards,
An Ho

[1] https://lists.opendaylight.org/pipermail/release/2017-June/011123.html
[2] https://wiki.opendaylight.org/view/Simultaneous_Release:Nitrogen_Release_Plan#Schedule
[3] https://wiki.opendaylight.org/view/Simultaneous_Release:Nitrogen_Release_Plan#Requirements_for_Participation
[4] https://wiki.opendaylight.org/view/Simultaneous_Release/Nitrogen/Karaf#Nitrogen_Project_Requirements


 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
WEB / https://pantheon.tech
 
 


Re: Committers vote for archiving openflowjava project

Michal Rehák <michal.rehak@...>
 

+1


Congratulations, we've got 3 out of 4.

Hereby I pronounce openflowjava project to be destined for archive state.



--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech


From: Michal Polkorab <michal.polkorab@...>
Sent: Thursday, June 29, 2017 10:04:44 AM
To: Jozef Bacigál
Cc: Michal Rehák; openflowjava-dev@...
Subject: Re: [openflowjava-dev] Committers vote for archiving openflowjava project
 
Hi Michal,

I agree. +1 for me.

Michal Polkorab

2017-06-29 9:59 GMT+02:00 Jozef Bacigál <jozef.bacigal@...>:

+1


Jozef


Od: Michal Rehák <michal.rehak@...>
Odoslané: štvrtok, 29. júna 2017 9:54:48
Komu: openflowjava-dev@lists.opendaylight.org
Predmet: [openflowjava-dev] Committers vote for archiving openflowjava project
 

Hi openflowjava committers,

based on intend of openflowplugin project to adopt codebase of openflowjava [1] - which I agree with - let me start voting for moving openflowjava project into archive state [2].


Please vote

+1: agree with moving

-1: disagree with moving



Thank you.


Regards,

Michal



[1] https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen

[2] https://wiki.opendaylight.org/view/TSC:Main#Project_Archiving_and_Termination_Reviews



--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech

 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
 
 
 
Jozef Bacigál
Senior Software Engineer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / jozef.bacigal@...
 
 

_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
WEB / https://pantheon.tech
 
 


Re: Committers vote for archiving openflowjava project

Michal Polkorab <michal.polkorab@...>
 

Hi Michal,

I agree. +1 for me.

Michal Polkorab

2017-06-29 9:59 GMT+02:00 Jozef Bacigál <jozef.bacigal@...>:

+1


Jozef


Od: Michal Rehák <michal.rehak@...>
Odoslané: štvrtok, 29. júna 2017 9:54:48
Komu: openflowjava-dev@lists.opendaylight.org
Predmet: [openflowjava-dev] Committers vote for archiving openflowjava project
 

Hi openflowjava committers,

based on intend of openflowplugin project to adopt codebase of openflowjava [1] - which I agree with - let me start voting for moving openflowjava project into archive state [2].


Please vote

+1: agree with moving

-1: disagree with moving



Thank you.


Regards,

Michal



[1] https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen

[2] https://wiki.opendaylight.org/view/TSC:Main#Project_Archiving_and_Termination_Reviews



--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech

 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
 
 
 
Jozef Bacigál
Senior Software Engineer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / jozef.bacigal@...
 
 

_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev



Re: Committers vote for archiving openflowjava project

Jozef Bacigál <jozef.bacigal@...>
 

+1


Jozef


Od: Michal Rehák <michal.rehak@...>
Odoslané: štvrtok, 29. júna 2017 9:54:48
Komu: openflowjava-dev@...
Predmet: [openflowjava-dev] Committers vote for archiving openflowjava project
 

Hi openflowjava committers,

based on intend of openflowplugin project to adopt codebase of openflowjava [1] - which I agree with - let me start voting for moving openflowjava project into archive state [2].


Please vote

+1: agree with moving

-1: disagree with moving



Thank you.


Regards,

Michal



[1] https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen

[2] https://wiki.opendaylight.org/view/TSC:Main#Project_Archiving_and_Termination_Reviews



--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech

 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
WEB / https://pantheon.tech
 
 
 
Jozef Bacigál
Senior Software Engineer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / jozef.bacigal@...
WEB / https://pantheon.tech
 
 


Committers vote for archiving openflowjava project

Michal Rehák <michal.rehak@...>
 

Hi openflowjava committers,

based on intend of openflowplugin project to adopt codebase of openflowjava [1] - which I agree with - let me start voting for moving openflowjava project into archive state [2].


Please vote

+1: agree with moving

-1: disagree with moving



Thank you.


Regards,

Michal



[1] https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen

[2] https://wiki.opendaylight.org/view/TSC:Main#Project_Archiving_and_Termination_Reviews



--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech

 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
WEB / https://pantheon.tech
 
 


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

Michal Rehák <michal.rehak@...>
 


Hi all,

unfortunately the deadline for answer regarding Nitrogen participation is in 2 days. Based on openflowplugin communication and weather page [3] I presume that the decision to adopt codebase of openflowjava in Nitrogen has been met and now the discussion aims on finding the best way to do so. That's why I will now initiate voting of openflowjava committers to instigate moving openflowjava project to archived state involving termination review (according to [1]).


In case of positive result I will create termination proposal wiki (similar to [2]) and reply to tsc that openflowjava project intends to drop from Nitrogen release.


@Vishal: I believe that patch for integration/distribution will be provided by openflowplugin community soon.

@Robert: As the project content it not really terminated I guess that termination review could contain some extra points

   - open issues/enhancements and plan on how to cope with bugzilla (merge outstanding  bugs or just lock openflowjava space and from now on file all bugs under openflowplugin or wait for jira.. whatever)

   - the same for corresponding part of documentation project and wiki pages


I guess there is no urgent need to discuss adopting openflowjava committers to openflowplugin as there are just 3 active and 2 of them are openflowplugin committers already.



Any enhancement ideas or objections?


Regards,
Michal


[1] https://wiki.opendaylight.org/view/TSC:Main#Project_Archiving_and_Termination_Reviews
[2] https://wiki.opendaylight.org/view/TCPMD5:Termination_Proposal
[3] https://wiki.opendaylight.org/view/Weather#OpenFlowJava_being_merged_into_OpenFlowPlugin_in_Nitrogen

--

Michal Rehák
Software developer
Pantheon Technologies s.r.o.
Mlynské Nivy 56
821 05 Bratislava
Slovakia
Mobile:  +421 918 621 908
Mail:    michal.rehak@...
Web:     www.pantheon.tech


From: Vishal Thapar <vishal.thapar@...>
Sent: Wednesday, June 28, 2017 6:14:35 PM
To: Robert Varga; Colin Dixon; Tomáš Slušný
Cc: openflowjava-dev@...; release@...; Michal Rehák; openflowplugin-dev; Abhijit Kumbhare
Subject: RE: [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen
 
OpenflowJava/Plugin devs,

I believe openflowjava would still be adding patch to enable in integration/distribution as part of Karaf4 migration, before this merge? I didn't see any patch yet so wanted to know what the plans are with karaf4.

Regards,
Vishal.

-----Original Message-----
From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Robert Varga
Sent: 28 June 2017 21:36
To: Colin Dixon <colin@...>; Tomáš Slušný <tomas.slusny@...>
Cc: openflowjava-dev@...; release@...; Michal Rehák <michal.rehak@...>; openflowplugin-dev <openflowplugin-dev@...>; Abhijit Kumbhare <abhijit.kumbhare@...>
Subject: Re: [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

On 28/06/17 17:58, Colin Dixon wrote:
> As an aside, I'm assuming this means openflowjava will not participate
> in nitrogen. Is that right?

I would guess so. It also means we need to figure out something like a Termination Review process or something... Any ideas?

Regards,
Robert

 
Michal Rehák
Technical Leader
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / michal.rehak@...
WEB / https://pantheon.tech
 
 


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

Abhijit Kumbhare
 

Thanks Andy! Hopefully Sam can also make it.

On Wed, Jun 28, 2017 at 11:53 AM, Andrew Grimberg <agrimberg@...> wrote:
Abhijit,

Yes I can join this coming week.

-Andy-

On 06/28/2017 09:14 AM, Abhijit Kumbhare wrote:
> I talked with Jozef and Tomas right now - and we think it will be good
> to discuss this in the Monday OpenFlow Plugin meeting this process
> (steps provided by Andy, the process followed by Sam/NetVirt when they
> consumed VPN Service into NetVirt, history, etc.). That way we can
> ensure it is done right - have all the OpenFlow Plugin committers vote
> during the meeting if needed. And then initiate OpenFlow Java vote.
> Hence we will greatly appreciate if Andy (Grimberg) and Sam Hague can
> join the meeting. The meeting details are here:
>
> https://wiki.opendaylight.org/view/Weekly_Project_Meeting_List
>
> Also pasting below:
>
> Weekly on Mondays from 08:30-9:30 am PST/PDT | 11:30-12:30 EST/EDT |
> 15:30-16:30 UTC during Daylight Time/16:30-17:30 UTC during Standard Time
>
>   * Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/751766361
>   * Or iPhone one-tap (US Toll): +14086380968,751766361# or
>     +16465588656,751766361#
>   * Or Telephone:
>       o Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
>       o Meeting ID: 751 766 361
>       o International numbers
>         available: https://zoom.us/zoomconference?m=RnpzDoDRkdpjWl6TcLb7wYiYV2NYaEUw
>   * IRC: Freenode: #opendaylight-openflowplugin
>
>
>
>
> On Tue, Jun 27, 2017 at 11:15 AM, Abhijit Kumbhare
> <abhijitkoss@... <mailto:abhijitkoss@...>> 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 impact). Unfortunately I have been offline for
>     periods of time during the last week or two (on a vacation).
>     Tomorrow (Wednesday) I will be meeting Jozef Bacigal (OpenFlow Java
>     & Plugin committer) and Tomas Slusny (OpenFlow Plugin committer
>     working on this) to understand the latest status on how this has
>     evolved and based on that will figure out the best course of action
>     (after discussing with the other OFP/OFJ committers).
>
>     On Tue, Jun 27, 2017 at 7:23 AM, Ed Warnicke <hagbard@...
>     <mailto:hagbard@...>> wrote:
>
>         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 openflowjava
>         project, and it would have one if there was some dispute with
>         the openflowjava committers (which does not appear to be the
>         case).   All of that said, it is probably courteous to inform
>         the TSC :)
>                 Thank you for guiding this process :)
>
>         Ed
>
>         On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare
>         <abhijitkoss@... <mailto:abhijitkoss@...>> wrote:
>
>             Thanks Sam! We may have some questions as we go further into
>             the process.
>
>             On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...
>             <mailto:shague@...>> wrote:
>
>                 On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare
>                 <abhijitkoss@... <mailto:abhijitkoss@...>>
>                 wrote:
>                 > Hi folks,
>                 >
>                 > We have 2 projects for OpenFlow - OpenFlow Plugin
>                 (connection handling,
>                 > state management, apps like the FRM, etc.) & OpenFlow
>                 Java Library (library
>                 > for the low level wire protocol implementation). This
>                 increases the
>                 > logistics related to the OpenFlow southbound
>                 development (done in two
>                 > places) and project reporting overhead. The other
>                 southbounds like OVSDB,
>                 > NetConf, etc. do not have two different projects -
>                 even if some of them may
>                 > have a similar split internally (plugin & library).
>                 >
>                 > Also more importantly currently most community activity
>                 > (meetings/discussions for the new features) happen in
>                 the OpenFlow Plugin
>                 > community even though the implementation needs to be
>                 done in OF Plugin and
>                 > OFJ Library. Also going forward OFJ may have only a
>                 single active committer
>                 > (Jozef Bacigal).
>                 >
>                 > So some of us feel Nitrogen might be a good time to
>                 unify these two
>                 > projects.
>                 >
>                 > The current thought:
>                 >   Move all the code from OpenFlow Java Library to the
>                 OpenFlow Plugin.
>                 >
>                 > Advantages:
>                 > 1) This may not need a lot of work.
>                 > 2) All active OpenFlow Java committers are also
>                 committers on OpenFlow
>                 > Plugin.
>                 > 3) Since we are not creating a project & if we do not
>                 add any new committers
>                 > - this may not even need a TSC approval (but we will
>                 work with the TSC when
>                 > we have decided the exact action).
>                 >
>                 > Challenges / open questions:
>                 > 1) How do we retain history for the OpenFlow Java code
>                 for code done before
>                 > the code movement? The IT experts may have some ideas
>                 on this - Thanh, Anil
>                 > B, Andrew? Also is there a way to subsume a project
>                 into another project or
>                 > merge the repos?
>
>                 We kept history when we split ovsdb/netvirt and then
>                 merged netvirt
>                 and vpnservice. The flow Andy used copied all the files
>                 into NetVirt
>                 and the history was kept intact. I think I came up with
>                 the commands
>                 to use and Andy did the work - but I can't find those
>                 emails right
>                 now.
>
>                 You should also stop the jobs running for the old
>                 openflowjava repo
>                 and migrate them to use openflowplugin repo.
>
>                 >    One obvious solution, we can just keep the OpenFlow
>                 Java Library repo
>                 > still active - even if OpenFlow Java Library does not
>                 participate in future
>                 > simultaneous releases.
>                 > 2) How do handle the documentation of the 2 projects?
>                 Just move the OpenFlow
>                 > Java documentation inside the developer guide under
>                 OFP documentation?
>
>                 Yes, this is what we did - just pulled in the relvant
>                 docs to netvirt.
>
>                 > 3) How do we handle the inactive committers of
>                 OpenFlow Java Library? If we
>                 > keep OpenFlow Java Library project active without
>                 participating in
>                 > simultaneous release - we likely do not have to
>                 address this problem.
>                 >
>                 > If you have thoughts/suggestions/objections - please
>                 reply to this email.
>                 >
>                 > Thanks,
>                 > Abhijit
>                 >
>                 >
>                 > _______________________________________________
>                 > openflowjava-dev mailing list
>                 > openflowjava-dev@lists.opendaylight.org
>                 <mailto:openflowjava-dev@lists.opendaylight.org>
>                 >
>                 https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
>                 <https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev>
>                 >
>
>
>             _______________________________________________
>             openflowplugin-dev mailing list
>             openflowplugin-dev@lists.opendaylight.org
>             <mailto:openflowplugin-dev@lists.opendaylight.org>
>             https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>             <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
>
>
>
>

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



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

Andrew Grimberg <agrimberg@...>
 

Abhijit,

Yes I can join this coming week.

-Andy-

On 06/28/2017 09:14 AM, Abhijit Kumbhare wrote:
I talked with Jozef and Tomas right now - and we think it will be good
to discuss this in the Monday OpenFlow Plugin meeting this process
(steps provided by Andy, the process followed by Sam/NetVirt when they
consumed VPN Service into NetVirt, history, etc.). That way we can
ensure it is done right - have all the OpenFlow Plugin committers vote
during the meeting if needed. And then initiate OpenFlow Java vote.
Hence we will greatly appreciate if Andy (Grimberg) and Sam Hague can
join the meeting. The meeting details are here:

https://wiki.opendaylight.org/view/Weekly_Project_Meeting_List

Also pasting below:

Weekly on Mondays from 08:30-9:30 am PST/PDT | 11:30-12:30 EST/EDT |
15:30-16:30 UTC during Daylight Time/16:30-17:30 UTC during Standard Time

* Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/751766361
* Or iPhone one-tap (US Toll): +14086380968,751766361# or
+16465588656,751766361#
* Or Telephone:
o Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
o Meeting ID: 751 766 361
o International numbers
available: https://zoom.us/zoomconference?m=RnpzDoDRkdpjWl6TcLb7wYiYV2NYaEUw
* IRC: Freenode: #opendaylight-openflowplugin




On Tue, Jun 27, 2017 at 11:15 AM, Abhijit Kumbhare
<abhijitkoss@... <mailto:abhijitkoss@...>> 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 impact). Unfortunately I have been offline for
periods of time during the last week or two (on a vacation).
Tomorrow (Wednesday) I will be meeting Jozef Bacigal (OpenFlow Java
& Plugin committer) and Tomas Slusny (OpenFlow Plugin committer
working on this) to understand the latest status on how this has
evolved and based on that will figure out the best course of action
(after discussing with the other OFP/OFJ committers).

On Tue, Jun 27, 2017 at 7:23 AM, Ed Warnicke <hagbard@...
<mailto:hagbard@...>> wrote:

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 openflowjava
project, and it would have one if there was some dispute with
the openflowjava committers (which does not appear to be the
case). All of that said, it is probably courteous to inform
the TSC :)
Thank you for guiding this process :)

Ed

On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare
<abhijitkoss@... <mailto:abhijitkoss@...>> wrote:

Thanks Sam! We may have some questions as we go further into
the process.

On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...
<mailto:shague@...>> wrote:

On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare
<abhijitkoss@... <mailto:abhijitkoss@...>>
wrote:
> Hi folks,
>
> We have 2 projects for OpenFlow - OpenFlow Plugin
(connection handling,
> state management, apps like the FRM, etc.) & OpenFlow
Java Library (library
> for the low level wire protocol implementation). This
increases the
> logistics related to the OpenFlow southbound
development (done in two
> places) and project reporting overhead. The other
southbounds like OVSDB,
> NetConf, etc. do not have two different projects -
even if some of them may
> have a similar split internally (plugin & library).
>
> Also more importantly currently most community activity
> (meetings/discussions for the new features) happen in
the OpenFlow Plugin
> community even though the implementation needs to be
done in OF Plugin and
> OFJ Library. Also going forward OFJ may have only a
single active committer
> (Jozef Bacigal).
>
> So some of us feel Nitrogen might be a good time to
unify these two
> projects.
>
> The current thought:
> Move all the code from OpenFlow Java Library to the
OpenFlow Plugin.
>
> Advantages:
> 1) This may not need a lot of work.
> 2) All active OpenFlow Java committers are also
committers on OpenFlow
> Plugin.
> 3) Since we are not creating a project & if we do not
add any new committers
> - this may not even need a TSC approval (but we will
work with the TSC when
> we have decided the exact action).
>
> Challenges / open questions:
> 1) How do we retain history for the OpenFlow Java code
for code done before
> the code movement? The IT experts may have some ideas
on this - Thanh, Anil
> B, Andrew? Also is there a way to subsume a project
into another project or
> merge the repos?

We kept history when we split ovsdb/netvirt and then
merged netvirt
and vpnservice. The flow Andy used copied all the files
into NetVirt
and the history was kept intact. I think I came up with
the commands
to use and Andy did the work - but I can't find those
emails right
now.

You should also stop the jobs running for the old
openflowjava repo
and migrate them to use openflowplugin repo.

> One obvious solution, we can just keep the OpenFlow
Java Library repo
> still active - even if OpenFlow Java Library does not
participate in future
> simultaneous releases.
> 2) How do handle the documentation of the 2 projects?
Just move the OpenFlow
> Java documentation inside the developer guide under
OFP documentation?

Yes, this is what we did - just pulled in the relvant
docs to netvirt.

> 3) How do we handle the inactive committers of
OpenFlow Java Library? If we
> keep OpenFlow Java Library project active without
participating in
> simultaneous release - we likely do not have to
address this problem.
>
> If you have thoughts/suggestions/objections - please
reply to this email.
>
> Thanks,
> Abhijit
>
>
> _______________________________________________
> openflowjava-dev mailing list
> openflowjava-dev@...
<mailto:openflowjava-dev@...>
>
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
<https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev>
>


_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...
<mailto:openflowplugin-dev@...>
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
<https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>



--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation


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

Abhijit Kumbhare
 

I talked with Jozef and Tomas right now - and we think it will be good to discuss this in the Monday OpenFlow Plugin meeting this process (steps provided by Andy, the process followed by Sam/NetVirt when they consumed VPN Service into NetVirt, history, etc.). That way we can ensure it is done right - have all the OpenFlow Plugin committers vote during the meeting if needed. And then initiate OpenFlow Java vote. Hence we will greatly appreciate if Andy (Grimberg) and Sam Hague can join the meeting. The meeting details are here:


Also pasting below:

Weekly on Mondays from 08:30-9:30 am PST/PDT | 11:30-12:30 EST/EDT | 15:30-16:30 UTC during Daylight Time/16:30-17:30 UTC during Standard Time



On Tue, Jun 27, 2017 at 11:15 AM, Abhijit Kumbhare <abhijitkoss@...> 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 impact). Unfortunately I have been offline for periods of time during the last week or two (on a vacation). Tomorrow (Wednesday) I will be meeting Jozef Bacigal (OpenFlow Java & Plugin committer) and Tomas Slusny (OpenFlow Plugin committer working on this) to understand the latest status on how this has evolved and based on that will figure out the best course of action (after discussing with the other OFP/OFJ committers).

On Tue, Jun 27, 2017 at 7:23 AM, Ed Warnicke <hagbard@...> wrote:
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 openflowjava project, and it would have one if there was some dispute with the openflowjava committers (which does not appear to be the case).   All of that said, it is probably courteous to inform the TSC :)
        Thank you for guiding this process :)

Ed

On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
Thanks Sam! We may have some questions as we go further into the process.

On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...> wrote:
On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
> Hi folks,
>
> We have 2 projects for OpenFlow - OpenFlow Plugin (connection handling,
> state management, apps like the FRM, etc.) & OpenFlow Java Library (library
> for the low level wire protocol implementation). This increases the
> logistics related to the OpenFlow southbound development (done in two
> places) and project reporting overhead. The other southbounds like OVSDB,
> NetConf, etc. do not have two different projects - even if some of them may
> have a similar split internally (plugin & library).
>
> Also more importantly currently most community activity
> (meetings/discussions for the new features) happen in the OpenFlow Plugin
> community even though the implementation needs to be done in OF Plugin and
> OFJ Library. Also going forward OFJ may have only a single active committer
> (Jozef Bacigal).
>
> So some of us feel Nitrogen might be a good time to unify these two
> projects.
>
> The current thought:
>   Move all the code from OpenFlow Java Library to the OpenFlow Plugin.
>
> Advantages:
> 1) This may not need a lot of work.
> 2) All active OpenFlow Java committers are also committers on OpenFlow
> Plugin.
> 3) Since we are not creating a project & if we do not add any new committers
> - this may not even need a TSC approval (but we will work with the TSC when
> we have decided the exact action).
>
> Challenges / open questions:
> 1) How do we retain history for the OpenFlow Java code for code done before
> the code movement? The IT experts may have some ideas on this - Thanh, Anil
> B, Andrew? Also is there a way to subsume a project into another project or
> merge the repos?

We kept history when we split ovsdb/netvirt and then merged netvirt
and vpnservice. The flow Andy used copied all the files into NetVirt
and the history was kept intact. I think I came up with the commands
to use and Andy did the work - but I can't find those emails right
now.

You should also stop the jobs running for the old openflowjava repo
and migrate them to use openflowplugin repo.

>    One obvious solution, we can just keep the OpenFlow Java Library repo
> still active - even if OpenFlow Java Library does not participate in future
> simultaneous releases.
> 2) How do handle the documentation of the 2 projects? Just move the OpenFlow
> Java documentation inside the developer guide under OFP documentation?

Yes, this is what we did - just pulled in the relvant docs to netvirt.

> 3) How do we handle the inactive committers of OpenFlow Java Library? If we
> keep OpenFlow Java Library project active without participating in
> simultaneous release - we likely do not have to address this problem.
>
> If you have thoughts/suggestions/objections - please reply to this email.
>
> Thanks,
> Abhijit
>
>
> _______________________________________________
> openflowjava-dev mailing list
> openflowjava-dev@...light.org
> https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
>

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...aylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev





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

Vishal Thapar <vishal.thapar@...>
 

OpenflowJava/Plugin devs,

I believe openflowjava would still be adding patch to enable in integration/distribution as part of Karaf4 migration, before this merge? I didn't see any patch yet so wanted to know what the plans are with karaf4.

Regards,
Vishal.

-----Original Message-----
From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Robert Varga
Sent: 28 June 2017 21:36
To: Colin Dixon <colin@...>; Tomáš Slušný <tomas.slusny@...>
Cc: openflowjava-dev@...; release@...; Michal Rehák <michal.rehak@...>; openflowplugin-dev <openflowplugin-dev@...>; Abhijit Kumbhare <abhijit.kumbhare@...>
Subject: Re: [release] WEATHER - OpenFlowJava being merged into OpenFlowPlugin in Nitrogen

On 28/06/17 17:58, Colin Dixon wrote:
As an aside, I'm assuming this means openflowjava will not participate
in nitrogen. Is that right?
I would guess so. It also means we need to figure out something like a Termination Review process or something... Any ideas?

Regards,
Robert


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

Robert Varga <nite@...>
 

On 28/06/17 17:58, Colin Dixon wrote:
As an aside, I'm assuming this means openflowjava will not participate
in nitrogen. Is that right?
I would guess so. It also means we need to figure out something like a
Termination Review process or something... Any ideas?

Regards,
Robert


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

Colin Dixon
 

As an aside, I'm assuming this means openflowjava will not participate in nitrogen. Is that right?

--Colin


On Tue, Jun 27, 2017 at 6:13 AM, Tomáš Slušný <tomas.slusny@...> wrote:

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 repository to decrease the logistics related to the OpenFlow southbound development.


 
Tomáš Slušný
Software Developer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / tomas.slusny@...
 
 

_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release



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

Ed Warnicke <hagbard@...>
 

Perfect :)

Ed

On Tue, Jun 27, 2017 at 11:15 AM, Abhijit Kumbhare <abhijitkoss@...> 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 impact). Unfortunately I have been offline for periods of time during the last week or two (on a vacation). Tomorrow (Wednesday) I will be meeting Jozef Bacigal (OpenFlow Java & Plugin committer) and Tomas Slusny (OpenFlow Plugin committer working on this) to understand the latest status on how this has evolved and based on that will figure out the best course of action (after discussing with the other OFP/OFJ committers).

On Tue, Jun 27, 2017 at 7:23 AM, Ed Warnicke <hagbard@...> wrote:
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 openflowjava project, and it would have one if there was some dispute with the openflowjava committers (which does not appear to be the case).   All of that said, it is probably courteous to inform the TSC :)
        Thank you for guiding this process :)

Ed

On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
Thanks Sam! We may have some questions as we go further into the process.

On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...> wrote:
On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
> Hi folks,
>
> We have 2 projects for OpenFlow - OpenFlow Plugin (connection handling,
> state management, apps like the FRM, etc.) & OpenFlow Java Library (library
> for the low level wire protocol implementation). This increases the
> logistics related to the OpenFlow southbound development (done in two
> places) and project reporting overhead. The other southbounds like OVSDB,
> NetConf, etc. do not have two different projects - even if some of them may
> have a similar split internally (plugin & library).
>
> Also more importantly currently most community activity
> (meetings/discussions for the new features) happen in the OpenFlow Plugin
> community even though the implementation needs to be done in OF Plugin and
> OFJ Library. Also going forward OFJ may have only a single active committer
> (Jozef Bacigal).
>
> So some of us feel Nitrogen might be a good time to unify these two
> projects.
>
> The current thought:
>   Move all the code from OpenFlow Java Library to the OpenFlow Plugin.
>
> Advantages:
> 1) This may not need a lot of work.
> 2) All active OpenFlow Java committers are also committers on OpenFlow
> Plugin.
> 3) Since we are not creating a project & if we do not add any new committers
> - this may not even need a TSC approval (but we will work with the TSC when
> we have decided the exact action).
>
> Challenges / open questions:
> 1) How do we retain history for the OpenFlow Java code for code done before
> the code movement? The IT experts may have some ideas on this - Thanh, Anil
> B, Andrew? Also is there a way to subsume a project into another project or
> merge the repos?

We kept history when we split ovsdb/netvirt and then merged netvirt
and vpnservice. The flow Andy used copied all the files into NetVirt
and the history was kept intact. I think I came up with the commands
to use and Andy did the work - but I can't find those emails right
now.

You should also stop the jobs running for the old openflowjava repo
and migrate them to use openflowplugin repo.

>    One obvious solution, we can just keep the OpenFlow Java Library repo
> still active - even if OpenFlow Java Library does not participate in future
> simultaneous releases.
> 2) How do handle the documentation of the 2 projects? Just move the OpenFlow
> Java documentation inside the developer guide under OFP documentation?

Yes, this is what we did - just pulled in the relvant docs to netvirt.

> 3) How do we handle the inactive committers of OpenFlow Java Library? If we
> keep OpenFlow Java Library project active without participating in
> simultaneous release - we likely do not have to address this problem.
>
> If you have thoughts/suggestions/objections - please reply to this email.
>
> Thanks,
> Abhijit
>
>
> _______________________________________________
> openflowjava-dev mailing list
> openflowjava-dev@...light.org
> https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
>

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...aylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev





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

Abhijit Kumbhare
 

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 or two (on a vacation). Tomorrow (Wednesday) I will be meeting Jozef Bacigal (OpenFlow Java & Plugin committer) and Tomas Slusny (OpenFlow Plugin committer working on this) to understand the latest status on how this has evolved and based on that will figure out the best course of action (after discussing with the other OFP/OFJ committers).

On Tue, Jun 27, 2017 at 7:23 AM, Ed Warnicke <hagbard@...> wrote:
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 openflowjava project, and it would have one if there was some dispute with the openflowjava committers (which does not appear to be the case).   All of that said, it is probably courteous to inform the TSC :)
        Thank you for guiding this process :)

Ed

On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
Thanks Sam! We may have some questions as we go further into the process.

On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...> wrote:
On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
> Hi folks,
>
> We have 2 projects for OpenFlow - OpenFlow Plugin (connection handling,
> state management, apps like the FRM, etc.) & OpenFlow Java Library (library
> for the low level wire protocol implementation). This increases the
> logistics related to the OpenFlow southbound development (done in two
> places) and project reporting overhead. The other southbounds like OVSDB,
> NetConf, etc. do not have two different projects - even if some of them may
> have a similar split internally (plugin & library).
>
> Also more importantly currently most community activity
> (meetings/discussions for the new features) happen in the OpenFlow Plugin
> community even though the implementation needs to be done in OF Plugin and
> OFJ Library. Also going forward OFJ may have only a single active committer
> (Jozef Bacigal).
>
> So some of us feel Nitrogen might be a good time to unify these two
> projects.
>
> The current thought:
>   Move all the code from OpenFlow Java Library to the OpenFlow Plugin.
>
> Advantages:
> 1) This may not need a lot of work.
> 2) All active OpenFlow Java committers are also committers on OpenFlow
> Plugin.
> 3) Since we are not creating a project & if we do not add any new committers
> - this may not even need a TSC approval (but we will work with the TSC when
> we have decided the exact action).
>
> Challenges / open questions:
> 1) How do we retain history for the OpenFlow Java code for code done before
> the code movement? The IT experts may have some ideas on this - Thanh, Anil
> B, Andrew? Also is there a way to subsume a project into another project or
> merge the repos?

We kept history when we split ovsdb/netvirt and then merged netvirt
and vpnservice. The flow Andy used copied all the files into NetVirt
and the history was kept intact. I think I came up with the commands
to use and Andy did the work - but I can't find those emails right
now.

You should also stop the jobs running for the old openflowjava repo
and migrate them to use openflowplugin repo.

>    One obvious solution, we can just keep the OpenFlow Java Library repo
> still active - even if OpenFlow Java Library does not participate in future
> simultaneous releases.
> 2) How do handle the documentation of the 2 projects? Just move the OpenFlow
> Java documentation inside the developer guide under OFP documentation?

Yes, this is what we did - just pulled in the relvant docs to netvirt.

> 3) How do we handle the inactive committers of OpenFlow Java Library? If we
> keep OpenFlow Java Library project active without participating in
> simultaneous release - we likely do not have to address this problem.
>
> If you have thoughts/suggestions/objections - please reply to this email.
>
> Thanks,
> Abhijit
>
>
> _______________________________________________
> openflowjava-dev mailing list
> openflowjava-dev@...light.org
> https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
>

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...aylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev




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

Anil Vishnoi
 

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 <vishnoianil@...> wrote:
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ý <tomas.slusny@...> wrote:

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 integrate new OpenFlowJava code into OpenFlowPlugin build (as, being in subdirectory, cut from rest of project, distribution checks will pass because OpenFlowJava will not be built). And third one is cleanup. First patch can be easily abandoned and replaced with solution what Robert suggested, and that is merging (or in this case, using git subtree) instead of plain copy of OpenFlowJava code, then second one can be rebased on master after first step will be done and pushed into repository (with some small changes, and that are removing .gitignore and .gitreview from openflowjava subdirectory, as I copied code without these 2 files in original first patch).


Also, during testing this migration, I noticed that distribution checks do not allow to have "org.opendaylight.openflowjava.*" and "org.opendaylight.openflowplugin.*" in same project, so I changed "org.opendaylight.openflowjava" groupId to "org.opendaylight.openflowplugin.openflowjava", so with this thing in mind, I think it is also natural to switch to OpenFlowPlugin versioning from OpenFlowJava versioning.


Regards,

Tomas



Od: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>
Odoslané: utorok, 27. júna 2017 16:11
Komu: Robert Varga; Tomáš Slušný; release@...
Kópia: openflowjava-dev@...light.org; tsc@...; Michal Rehák; openflowplugin-dev
Predmet: 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 regarding ofjava version is required as first step (to keep or to overwrite with ofplugin version). Base on that the rest can be resolved easily.

I tried to create draft of the whole merge but gerrit rejected it because of many missing change-ids and one missing sign-off. So gerrit + merge way is probably too inconvenient.


Regards,
Michal

_____________________________________
From: openflowplugin-dev-bounces@lists.opendaylight.org <openflowplugin-dev-bounces@lists.opendaylight.org> on behalf of Robert Varga <nite@...>
Sent: Tuesday, June 27, 2017 13:14
To: Tomáš Slušný; release@...
Cc: openflowjava-dev@...light.org; tsc@...; Michal Rehák; openflowplugin-dev
Subject: 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 commit if I am not wrong. Or is there another method of
> doing this merge?

What we have done in the past was to ask Linux Foundation admins to
populate the repository, side-stepping gerrit. We have done this for
mdsal and netconf at least.

I am not sure if the same effect is doable with gerrit.

Regards,
Robert

 
Tomáš Slušný
Software Developer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / tomas.slusny@...
 
 

_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...light.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev




--
Thanks
Anil



--
Thanks
Anil


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

Anil Vishnoi
 

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ý <tomas.slusny@...> wrote:

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 integrate new OpenFlowJava code into OpenFlowPlugin build (as, being in subdirectory, cut from rest of project, distribution checks will pass because OpenFlowJava will not be built). And third one is cleanup. First patch can be easily abandoned and replaced with solution what Robert suggested, and that is merging (or in this case, using git subtree) instead of plain copy of OpenFlowJava code, then second one can be rebased on master after first step will be done and pushed into repository (with some small changes, and that are removing .gitignore and .gitreview from openflowjava subdirectory, as I copied code without these 2 files in original first patch).


Also, during testing this migration, I noticed that distribution checks do not allow to have "org.opendaylight.openflowjava.*" and "org.opendaylight.openflowplugin.*" in same project, so I changed "org.opendaylight.openflowjava" groupId to "org.opendaylight.openflowplugin.openflowjava", so with this thing in mind, I think it is also natural to switch to OpenFlowPlugin versioning from OpenFlowJava versioning.


Regards,

Tomas



Od: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>
Odoslané: utorok, 27. júna 2017 16:11
Komu: Robert Varga; Tomáš Slušný; release@...
Kópia: openflowjava-dev@lists.opendaylight.org; tsc@...; Michal Rehák; openflowplugin-dev
Predmet: 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 regarding ofjava version is required as first step (to keep or to overwrite with ofplugin version). Base on that the rest can be resolved easily.

I tried to create draft of the whole merge but gerrit rejected it because of many missing change-ids and one missing sign-off. So gerrit + merge way is probably too inconvenient.


Regards,
Michal

_____________________________________
From: openflowplugin-dev-bounces@lists.opendaylight.org <openflowplugin-dev-bounces@lists.opendaylight.org> on behalf of Robert Varga <nite@...>
Sent: Tuesday, June 27, 2017 13:14
To: Tomáš Slušný; release@...
Cc: openflowjava-dev@lists.opendaylight.org; tsc@...; Michal Rehák; openflowplugin-dev
Subject: 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 commit if I am not wrong. Or is there another method of
> doing this merge?

What we have done in the past was to ask Linux Foundation admins to
populate the repository, side-stepping gerrit. We have done this for
mdsal and netconf at least.

I am not sure if the same effect is doable with gerrit.

Regards,
Robert

 
Tomáš Slušný
Software Developer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / tomas.slusny@...
 
 

_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev




--
Thanks
Anil


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

Tomáš Slušný <tomas.slusny@...>
 

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 integrate new OpenFlowJava code into OpenFlowPlugin build (as, being in subdirectory, cut from rest of project, distribution checks will pass because OpenFlowJava will not be built). And third one is cleanup. First patch can be easily abandoned and replaced with solution what Robert suggested, and that is merging (or in this case, using git subtree) instead of plain copy of OpenFlowJava code, then second one can be rebased on master after first step will be done and pushed into repository (with some small changes, and that are removing .gitignore and .gitreview from openflowjava subdirectory, as I copied code without these 2 files in original first patch).


Also, during testing this migration, I noticed that distribution checks do not allow to have "org.opendaylight.openflowjava.*" and "org.opendaylight.openflowplugin.*" in same project, so I changed "org.opendaylight.openflowjava" groupId to "org.opendaylight.openflowplugin.openflowjava", so with this thing in mind, I think it is also natural to switch to OpenFlowPlugin versioning from OpenFlowJava versioning.


Regards,

Tomas



Od: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...>
Odoslané: utorok, 27. júna 2017 16:11
Komu: Robert Varga; Tomáš Slušný; release@...
Kópia: openflowjava-dev@...; tsc@...; Michal Rehák; openflowplugin-dev
Predmet: 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 regarding ofjava version is required as first step (to keep or to overwrite with ofplugin version). Base on that the rest can be resolved easily.

I tried to create draft of the whole merge but gerrit rejected it because of many missing change-ids and one missing sign-off. So gerrit + merge way is probably too inconvenient.


Regards,
Michal

_____________________________________
From: openflowplugin-dev-bounces@... <openflowplugin-dev-bounces@...> on behalf of Robert Varga <nite@...>
Sent: Tuesday, June 27, 2017 13:14
To: Tomáš Slušný; release@...
Cc: openflowjava-dev@...; tsc@...; Michal Rehák; openflowplugin-dev
Subject: 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 commit if I am not wrong. Or is there another method of
> doing this merge?

What we have done in the past was to ask Linux Foundation admins to
populate the repository, side-stepping gerrit. We have done this for
mdsal and netconf at least.

I am not sure if the same effect is doable with gerrit.

Regards,
Robert

 
Tomáš Slušný
Software Developer
 
PANTHEON technologies s.r.o.
Janka Kráľa 9, 974 01 Banská Bystrica
Slovakia
Tel / +421 220 665 111
 
MAIL / tomas.slusny@...
WEB / https://pantheon.tech
 
 


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

Thanh Ha <thanh.ha@...>
 

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 (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

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 regarding ofjava version is required as first step (to keep or to overwrite with ofplugin version). Base on that the rest can be resolved easily.

I tried to create draft of the whole merge but gerrit rejected it because of many missing change-ids and one missing sign-off. So gerrit + merge way is probably too inconvenient.


Regards,
Michal

_____________________________________
From: openflowplugin-dev-bounces@lists.opendaylight.org <openflowplugin-dev-bounces@lists.opendaylight.org> on behalf of Robert Varga <nite@...>
Sent: Tuesday, June 27, 2017 13:14
To: Tomáš Slušný; release@...
Cc: openflowjava-dev@lists.opendaylight.org; tsc@...; Michal Rehák; openflowplugin-dev
Subject: 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 commit if I am not wrong. Or is there another method of
> doing this merge?

What we have done in the past was to ask Linux Foundation admins to
populate the repository, side-stepping gerrit. We have done this for
mdsal and netconf at least.

I am not sure if the same effect is doable with gerrit.

Regards,
Robert

_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release


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

Ed Warnicke <hagbard@...>
 

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 openflowjava project, and it would have one if there was some dispute with the openflowjava committers (which does not appear to be the case).   All of that said, it is probably courteous to inform the TSC :)
        Thank you for guiding this process :)

Ed

On Thu, Jun 8, 2017 at 1:26 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
Thanks Sam! We may have some questions as we go further into the process.

On Thu, Jun 8, 2017 at 1:00 PM Sam Hague <shague@...> wrote:
On Wed, Jun 7, 2017 at 8:21 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
> Hi folks,
>
> We have 2 projects for OpenFlow - OpenFlow Plugin (connection handling,
> state management, apps like the FRM, etc.) & OpenFlow Java Library (library
> for the low level wire protocol implementation). This increases the
> logistics related to the OpenFlow southbound development (done in two
> places) and project reporting overhead. The other southbounds like OVSDB,
> NetConf, etc. do not have two different projects - even if some of them may
> have a similar split internally (plugin & library).
>
> Also more importantly currently most community activity
> (meetings/discussions for the new features) happen in the OpenFlow Plugin
> community even though the implementation needs to be done in OF Plugin and
> OFJ Library. Also going forward OFJ may have only a single active committer
> (Jozef Bacigal).
>
> So some of us feel Nitrogen might be a good time to unify these two
> projects.
>
> The current thought:
>   Move all the code from OpenFlow Java Library to the OpenFlow Plugin.
>
> Advantages:
> 1) This may not need a lot of work.
> 2) All active OpenFlow Java committers are also committers on OpenFlow
> Plugin.
> 3) Since we are not creating a project & if we do not add any new committers
> - this may not even need a TSC approval (but we will work with the TSC when
> we have decided the exact action).
>
> Challenges / open questions:
> 1) How do we retain history for the OpenFlow Java code for code done before
> the code movement? The IT experts may have some ideas on this - Thanh, Anil
> B, Andrew? Also is there a way to subsume a project into another project or
> merge the repos?

We kept history when we split ovsdb/netvirt and then merged netvirt
and vpnservice. The flow Andy used copied all the files into NetVirt
and the history was kept intact. I think I came up with the commands
to use and Andy did the work - but I can't find those emails right
now.

You should also stop the jobs running for the old openflowjava repo
and migrate them to use openflowplugin repo.

>    One obvious solution, we can just keep the OpenFlow Java Library repo
> still active - even if OpenFlow Java Library does not participate in future
> simultaneous releases.
> 2) How do handle the documentation of the 2 projects? Just move the OpenFlow
> Java documentation inside the developer guide under OFP documentation?

Yes, this is what we did - just pulled in the relvant docs to netvirt.

> 3) How do we handle the inactive committers of OpenFlow Java Library? If we
> keep OpenFlow Java Library project active without participating in
> simultaneous release - we likely do not have to address this problem.
>
> If you have thoughts/suggestions/objections - please reply to this email.
>
> Thanks,
> Abhijit
>
>
> _______________________________________________
> openflowjava-dev mailing list
> openflowjava-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev
>

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev



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

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

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 regarding ofjava version is required as first step (to keep or to overwrite with ofplugin version). Base on that the rest can be resolved easily.

I tried to create draft of the whole merge but gerrit rejected it because of many missing change-ids and one missing sign-off. So gerrit + merge way is probably too inconvenient.


Regards,
Michal

_____________________________________
From: openflowplugin-dev-bounces@... <openflowplugin-dev-bounces@...> on behalf of Robert Varga <nite@...>
Sent: Tuesday, June 27, 2017 13:14
To: Tomáš Slušný; release@...
Cc: openflowjava-dev@...; tsc@...; Michal Rehák; openflowplugin-dev
Subject: 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 commit if I am not wrong. Or is there another method of
doing this merge?
What we have done in the past was to ask Linux Foundation admins to
populate the repository, side-stepping gerrit. We have done this for
mdsal and netconf at least.

I am not sure if the same effect is doable with gerrit.

Regards,
Robert

21 - 40 of 861