[L2switch-dev] [groupbasedpolicy-dev] [release] [openflowplugin-dev] migration of openflow related modules and applications from controller into ofplugin repo


Colin Dixon <colin@...>
 

For what it's worth, I've started maintaining a github repo with my for-all.pl script and a list of all current ODL repos as well as all ODL repos that are currently participating in the Lithium release here:
https://github.com/nilok/odlutils

You'll note that I've commented out the lines for affinity and net-virt-platform in the odl-repos.txt since I'm pretty sure they aren't pushing patches anymore.

--Colin


On Wed, Feb 25, 2015 at 11:32 AM, Luis Gomez <ecelgp@...> wrote:
Hi Michal and all,

I do not why we keep on showing not active projects in the ODL project list wiki [1], if we cannot remove them at least a note saying "not active or not available this release". This is not only confusing external people but confusing ourselves. I heard something about retiring old projects in past TSC call but I will bring the topic again next call.

BR/Luis




On Feb 24, 2015, at 11:38 PM, Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco) <mirehak@...> wrote:

Hi Luis,
I did not realize about affinity. We just pushed fixes to all ODL projects which were affected by migration. So then just packetcable is pending.

Regards,
Michal


From: Luis Gomez [ecelgp@...]
Sent: Wednesday, February 25, 2015 02:06
To: Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco)
Cc: release@...; openflowplugin-dev; aaa-dev@...; ovsdb-dev@...; groupbasedpolicy-dev@...; affinity-dev@...; l2switch-dev@...
Subject: Re: [groupbasedpolicy-dev] [release] [openflowplugin-dev] migration of openflow related modules and applications from controller into ofplugin repo

Why is affinity in the list? this project was not in Helium and will not be in Lithium.


On Feb 24, 2015, at 1:41 PM, Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco) <mirehak@...> wrote:

Greetings,
here is update regarding migration:

  * aaa -> NOOP
 * l2switch -> DONE
    merged: https://git.opendaylight.org/gerrit/#/c/14518
    https://bugs.opendaylight.org/show_bug.cgi?id=2647 
 * ovsdb -> DONE
    merged: https://git.opendaylight.org/gerrit/#/c/15643 
    https://bugs.opendaylight.org/show_bug.cgi?id=2654 
 * affinity -> INCOMPLETE
    pending: https://git.opendaylight.org/gerrit/#/c/14572 
 * packetcable -> INCOMPLETE
    pending: https://git.opendaylight.org/gerrit/#/c/14576 
    https://bugs.opendaylight.org/show_bug.cgi?id=2675 
 * grupbasedpolicy -> DONE
    abandoned: https://git.opendaylight.org/gerrit/#/c/14598 (used transient dependency to models)
 * sfc -> DONE
    merged: https://git.opendaylight.org/gerrit/#/c/15657
    abandoned: https://git.opendaylight.org/gerrit/#/c/14605 
 * 
openflowplugin -> DONE
   https://bugs.opendaylight.org/show_bug.cgi?id=2611 

After all downstream project are merged and confirmed working there is one last step - clean up models, features and apps in controller:https://bugs.opendaylight.org/show_bug.cgi?id=2751

Currently pending actions are only by projects AFFINITY and PACKETCABLE.


Regards,
Michal



From: release-bounces@... [release-bounces@...] on behalf of Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco)
Sent: Thursday, January 15, 2015 20:27
To: release@...
Cc: openflowplugin-dev; aaa-dev@...; ovsdb-dev@...; groupbasedpolicy-dev@...; affinity-dev@...; l2switch-dev@...
Subject: Re: [release] [openflowplugin-dev] migration of openflow related modules and applications from controller into ofplugin repo

Greetings,
here is the update of goals and deadlines:

With Amit from l2switch we came to agreement that all NSF apps will be moved to openflowplugin. And we might later change mind and move it elsewhere but for now in order not to increase current delay we want proceed.

Here are shifted deadlines for migration steps:
  • copy corresponding projects from controller into openflowplugin
  • change project and package names where necessary (without changing model content) (deadline:16.01.2015)
  • adapt downstream project in order to use those model projects (deadline: 23.01.2015)
  • remove models from controller repository (deadline: 30.01.2015)

Regards,
Michal



From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of Michal Rehak -X (mirehak - Pantheon Technologies SRO at Cisco)
Sent: Wednesday, January 07, 2015 17:09
To: release@...
Cc: openflowplugin-dev; aaa-dev@...; ovsdb-dev@...; groupbasedpolicy-dev@...; affinity-dev@...; l2switch-dev@...
Subject: [openflowplugin-dev] migration of openflow related modules and applications from controller into ofplugin repo

Greetings,
there are already some activities going on which are aimed to migrate openflow related models and applications from controller to openflowplugin repository.

Migration will take following steps:
  • copy corresponding projects from controller into openflowplugin
  • change project and package names where necessary (without changing model content) (deadline:09.01.2015)
  • adapt downstream project in order to use those model projects (deadline: 16.01.2015)
  • remove models from controller repository (deadline: 23.01.2015)

Models to migrate:
  • model/model-flow-base 
  • model/model-flow-service 
  • model/model-flow-statistics

Apps to migrate
  • statistics-manager 
  • forwardingrules-manager 
  • inventory-manager 
  • topology-lldp-discovery 
  • topology-manager

Donwstream projects (so far)
  • aaa 
  • l2switch 
  • ovsdb 
  • openflowplugin 
  • affinity 
  • packetcable 
  • grupbasedpolicy
If you have questions, contributions, comments then please feel free to respond. 
The reason for models to move into openflowplugin is that those models are openflow specific and mostly driven by openflowplugin development. And controller project plans to go more abstract/general way. 
With applications the situation is similar with one difference - there is no direct downstream project, there are just projects depending on dataStore result of those applications.

There are no deadlines for applications yet but moving them together with models might spare us some renaming work.

Thank you.
Regards,
Michal


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


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