Re: [openflowplugin-dev] [OpenDaylight Discuss] Important: Inventory model migration proposal (instead of inventory to topology model migration)

[Anil Vishnoi]

On Mon, May 9, 2016 at 2:42 PM, Robert Varga  wrote:

> On 05/02/2016 11:52 PM, Abhijit Kumbhare wrote:
> > Hi folks,
> >
>
> [snip]
>
> > This will require some change by the dependent projects (some
> > modifications in the dependency declaration in the pom files) - however
> > it will be less change than a complete migration to the topology model.
> > *If you have any thoughts about the change - please provide your
> thoughts*.
> >
> > We inside of OpenFlow Plugin project like this change (as opposed to the
> > inventory to topology model migration change for which there were no
> > volunteers due to the effort and lack of obvious benefits).
>
> I have to disagree on the 'lack of benefits' part. Having aligned base
> models is critical for end user experience. The topology model is
> implemented by multiple SB plugins to expose exactly the same semantics
> as the inventory model.
>
> From modeling perspective, the inventory model is a strict subset of
> concepts expressed in the topology model.
>
> Keeping two models for the same thing is pure overhead from maintenance
> and interoperability point of view.
>
​I don't really see any major maintenance and interoperability issues and i
believe once we move inventory model to openflowplugin, we avoid any future
issues as well.
If i weigh the benefit of removing these models and disrupting the
downstream projects ​Vs containing it within plugin with minimal
disruption, i don't really see any value in removing inventory models.

>
> The inventory model must be eliminated if we ever hope to have any sort
> of consistence across SB plugins. This has been discussed and agreed
> multiple times, can we please stick to the plan?
> ​
>
​I am not sure we can achieve 100% consistency across SB plugin, because
IMO we can't force any southbound plugin from using these inventory models
in future as well.
About sticking to the plan, sure we can, i am just throwing alternate
options, where we can manage this situation without doing any major
disruption and i don't really see any major issue with it. ​


> ​
>
>

>
> Since there is a proposal to eliminate the OFP version-agnostic model
> (which is tied to topology via the new plugin), I think it would be very
> logical to attach the OFJ models to topology as a replacement and simple
> gradually desupport the inventory model -- old stuff works as long as
> old models do.
>
​This looks like a middle path, but i believe it's bit long term​ solution,
but make sense to me.

>
> Thanks,
> Robert
>
>
> ___
> Discuss mailing list
> disc...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/discuss
>
>


-- 
Thanks
Anil
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] OpenFlow Plugin Meeting Minutes May 9, 2016

[Abhijit Kumbhare]

I guess I did not capture the details in the minutes - here they are:

Anil raised some concerns about the patch that this is dependent on work in
Linux kernel and OVS - and that the upstream changes will incur changes to
this patch in the future. His concern was that currently this patch does
not keep backward compatibility for Srini's and Ed's patches earlier - but
he thinks that may be OK as the earlier work is not used somewhere. On the
other hand the concern he had was that the code may have to be changed in
the future (depending on OVS & Linux kernel) - and in future it may be hard
to keep backward compatibility to this current work that you have done. He
was planning to send an email to the OpenFlow plugin mailing list about
this for their concerns - and then merge.

On Mon, May 9, 2016 at 6:27 PM, Yang, Yi Y  wrote:

> Hi, Abhijit
>
>
>
> So what is next step for https://git.opendaylight.org/gerrit/#/c/37937/ ?
>
>
>
> *From:* openflowplugin-dev-boun...@lists.opendaylight.org [mailto:
> openflowplugin-dev-boun...@lists.opendaylight.org] *On Behalf Of *Abhijit
> Kumbhare
> *Sent:* Tuesday, May 10, 2016 2:09 AM
> *To:* openflowplugin-dev@lists.opendaylight.org
> *Subject:* [openflowplugin-dev] OpenFlow Plugin Meeting Minutes May 9,
> 2016
>
>
>
> -
>
> Browser Friendly format meeting minutes:
>
> -
>
>
> http://meetings.opendaylight.org/opendaylight-openflowplugin/2016/openflow_plugin_may_9__2016/o
> pendaylight-openflowplugin-openflow_plugin_may_9__2016.2016-05-09-16.04.html
>
>
>
>
> --
>
> Text format friendly for direct linking of lists.opendaylight.org
>  archives:
>
>
> --
>
> Meeting summary
>
> ---
>
> * Agenda  (abhijitkumbhare, 16:05:14)
>
>   * M3 items - bugs for the new design for projects  (abhijitkumbhare,
>
> 16:05:44)
>
>   * NSH patch from Yi Yang  (abhijitkumbhare, 16:06:16)
>
>   * BluePrint  (abhijitkumbhare, 16:06:48)
>
>   * TWS topic - merge of OpenFlow projects  (abhijitkumbhare, 16:07:34)
>
>   * Merges pending / code reviews  (abhijitkumbhare, 16:08:05)
>
>
>
> * BluePrint  (abhijitkumbhare, 16:08:47)
>
>   * TomP has couple of draft patches for BluePrint  (abhijitkumbhare,
>
> 16:10:49)
>
>
>
> * M3 items - bugs for the new design from the dependent projects
>
>   (abhijitkumbhare, 16:22:24)
>
>   * L2 switch blocker - goes to the switch but not the stats:
>
> https://bugs.opendaylight.org/show_bug.cgi?id=5822
>
> (abhijitkumbhare, 16:26:40)
>
>   * 5822 needed for migration  (abhijitkumbhare, 16:28:27)
>
>   * Regression of the functionality - target for M4  (abhijitkumbhare,
>
> 16:29:41)
>
>   * 5659 - not related to Li Migration  (abhijitkumbhare, 16:31:23)
>
>   * Bug 5602: Blocker for Li migration for VTN project
>
> (abhijitkumbhare, 16:34:08)
>
>   * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=5692  (hideyuki,
>
> 16:39:23)
>
>   * Blocker bugs for Li migration default change would be: 5692, 5602 &
>
> 4671  (abhijitkumbhare, 16:43:52)
>
>   * ACTION: eshuvka_ to take a quick look at 5602; after that will
>
> likely need jbacigal to take over  (abhijitkumbhare, 16:46:37)
>
>   * ACTION: jbacigal looking into 4671 with michal_rehak
>
> (abhijitkumbhare, 16:47:07)
>
>   * ACTION: hideyuki to take a look into 5692 if it can wait after the
>
> migration - since the estimate from Tomas Slusny for this M4
>
> (abhijitkumbhare, 16:48:20)
>
>
>
> * NSH patch from Yi Yang  (abhijitkumbhare, 16:49:22)
>
>   * vishnoianil has some concerns - there was some previous work by
>
> Srini and Ed  (abhijitkumbhare, 16:49:57)
>
>   * Yi’s patch undoes some of the work by Srini & Ed  (abhijitkumbhare,
>
> 16:50:26)
>
>   * Yi’s patch modifies some of the existing extensions from Beryllium
>
> (abhijitkumbhare, 16:51:28)
>
>   * LINK: https://git.opendaylight.org/gerrit/#/c/37937/  (vishnoianil,
>
> 16:56:04)
>
> Meeting ended at 17:00:25 UTC.
>
>
>
> Action items, by person
>
> ---
>
> * eshuvka_
>
>   * eshuvka_ to take a quick look at 5602; after that will likely need
>
> jbacigal to take over
>
> * hideyuki
>
>   * hideyuki to take a look into 5692 if it can wait after the migration
>
> - since the estimate from Tomas Slusny for this M4
>
> * jbacigal
>
>   * eshuvka_ to take a quick look at 5602; after that will likely need
>
> jbacigal to take over
>
>   * jbacigal looking into 4671 with michal_rehak
>
>
>
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] [OpenDaylight Discuss] Important: Inventory model migration proposal (instead of inventory to topology model migration)

[Abhijit Kumbhare]

In-line.

On Mon, May 9, 2016 at 2:42 PM, Robert Varga  wrote:

> On 05/02/2016 11:52 PM, Abhijit Kumbhare wrote:
> > Hi folks,
> >
>
> [snip]
>
> > This will require some change by the dependent projects (some
> > modifications in the dependency declaration in the pom files) - however
> > it will be less change than a complete migration to the topology model.
> > *If you have any thoughts about the change - please provide your
> thoughts*.
> >
> > We inside of OpenFlow Plugin project like this change (as opposed to the
> > inventory to topology model migration change for which there were no
> > volunteers due to the effort and lack of obvious benefits).
>
> I have to disagree on the 'lack of benefits' part. Having aligned base
> models is critical for end user experience. The topology model is
> implemented by multiple SB plugins to expose exactly the same semantics
> as the inventory model.
>

Abhijit>> I mentioned "lack of obvious benefits" rather than "lack of
benefits" :).


> From modeling perspective, the inventory model is a strict subset of
> concepts expressed in the topology model.
>
> Keeping two models for the same thing is pure overhead from maintenance
> and interoperability point of view.
>
> The inventory model must be eliminated if we ever hope to have any sort
> of consistence across SB plugins. This has been discussed and agreed
> multiple times, can we please stick to the plan?
>

Abhijit>> The biggest problem with this has been that no one seems to have
warmed up enough to the idea to start working on it - especially in Boron.
I myself will welcome it if there were folks working on it to make it
happen.


>
> Since there is a proposal to eliminate the OFP version-agnostic model
> (which is tied to topology via the new plugin), I think it would be very
> logical to attach the OFJ models to topology as a replacement and simple
> gradually desupport the inventory model -- old stuff works as long as
> old models do.
>

Abhijit>> I think what you are saying is - that we keep the inventory as-is
in Boron (due to no one picking up the work); and merge this as part of
cleanup of the OFP-OFJ models (assuming that proposal becomes a reality).
This sounds an interesting idea - I have added it as a bullet to the
proposal as a point of discussion. If this does not become a reality - then
we can come back to Anil's proposal.


> Thanks,
> Robert
>
>
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] [OpenDaylight Discuss] Important: Inventory model migration proposal (instead of inventory to topology model migration)

[Robert Varga]

On 05/02/2016 11:52 PM, Abhijit Kumbhare wrote:
> Hi folks,
> 

[snip]

> This will require some change by the dependent projects (some
> modifications in the dependency declaration in the pom files) - however
> it will be less change than a complete migration to the topology model.
> *If you have any thoughts about the change - please provide your thoughts*.
> 
> We inside of OpenFlow Plugin project like this change (as opposed to the
> inventory to topology model migration change for which there were no
> volunteers due to the effort and lack of obvious benefits).

I have to disagree on the 'lack of benefits' part. Having aligned base
models is critical for end user experience. The topology model is
implemented by multiple SB plugins to expose exactly the same semantics
as the inventory model.

From modeling perspective, the inventory model is a strict subset of
concepts expressed in the topology model.

Keeping two models for the same thing is pure overhead from maintenance
and interoperability point of view.

The inventory model must be eliminated if we ever hope to have any sort
of consistence across SB plugins. This has been discussed and agreed
multiple times, can we please stick to the plan?

Since there is a proposal to eliminate the OFP version-agnostic model
(which is tied to topology via the new plugin), I think it would be very
logical to attach the OFJ models to topology as a replacement and simple
gradually desupport the inventory model -- old stuff works as long as
old models do.

Thanks,
Robert



signature.asc
Description: OpenPGP digital signature
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] [release] [didm-dev] didm-hp module failing to compile

[Abhijit Kumbhare]

Thanks Alexis & Anandhi!

On Mon, May 9, 2016 at 1:37 PM, Manikantan, Anandhi <
anandhi.manikan...@hpe.com> wrote:

> Hi Subhash,
>
>
>
> I reviewed the code and comments. Alex has responded to the comments and
> feels that this needs to be tested before merge.
>
> Since I don’t have the setup now, would you be able to test and let me
> know so that I can merge.
>
> I can help you with test guidelines if needed
>
> Please shoot me an e-mail offline.
>
>
>
> Thanks
>
> Anandhi
>
>
>
> *From:* Subhash Singh [mailto:subhash_si...@criterionnetworks.com]
> *Sent:* Friday, May 06, 2016 8:08 AM
> *To:* Manikantan, Anandhi 
> *Cc:* Alexis de Talhouët ; Jamo Luhrsen <
> jluhr...@gmail.com>; rele...@lists.opendaylight.org;
> didm-...@lists.opendaylight.org; openflowplugin-dev <
> openflowplugin-dev@lists.opendaylight.org>; Thanh Ha <
> thanh...@linuxfoundation.org>
> *Subject:* Re: [release] [didm-dev] didm-hp module failing to compile
>
>
>
> Hello Anandhi,
>
>
>
> Could you please review the patch, as you are more familiar with this part
> of the implementation and also I don't have the rights to merge.
>
>
>
> --
>
> Thanks and Regards,
>
> Subhash Kumar Singh
>
>
>
> On Fri, May 6, 2016 at 7:27 PM, Thanh Ha 
> wrote:
>
> Thanks Alexis,
>
>
>
> Can someone review and merge the patch?
>
>
>
> Thanks,
>
> Thanh
>
>
>
>
>
> On 6 May 2016 at 08:45, Alexis de Talhouët 
> wrote:
>
> And the candidate fix:
>
> https://git.opendaylight.org/gerrit/#/c/38507/
>
>
>
> Thanks,
>
> Alexis
>
>
>
> On May 6, 2016, at 8:21 AM, Alexis de Talhouët 
> wrote:
>
>
>
> FYI, this is the reason one DIDM is broken: changed of OFP yang model:
>
>
>
>
> https://git.opendaylight.org/gerrit/#/c/36559/5/model/model-flow-service/src/main/yang/flow-node-inventory.yang
>
>
>
> Thanks,
>
> Alexis
>
>
>
> On May 5, 2016, at 8:03 PM, Thanh Ha  wrote:
>
>
>
> FYI we've disabled DIDM from autorelease-boron so that the job can
> continue testing until this bug is sorted out.
>
>
>
> Regards,
>
> Thanh
>
>
>
> On 5 May 2016 at 16:39, Thanh Ha  wrote:
>
> To be clear it's the root cause of why we can't reproduce the failure
> locally since ofp hasn't been pushing to Nexus their latest artifacts.
>
>
>
> didm-hp will still fail to compile so we still need someone to look into
> why getTableFeature() is failing.
>
>
>
> Regards,
>
> Thanh
>
>
>
>
>
> On 5 May 2016 at 15:11, Jamo Luhrsen  wrote:
>
> after more debugging with Thanh, we think the root cause is because
> openflowplugin's
> merge job started failing because of the http vs https issue when
> uploading artifacts
> to nexus.
>
> this patch in openflowplugin should fix that:
> https://git.opendaylight.org/gerrit/38436
>
> JamO
>
>
> On 05/05/2016 11:38 AM, Subhash Singh wrote:
> > +[Anandhi]
> >
> > Hello Thanh,
> >
> > Anandhi is familiar with didm-hp module (using getTableFeature), I think
> she could add clarification on this issue.
> >
> > --
> > Regards,
> > Subhash Kumar Singh
> >
> > On Thu, May 5, 2016 at 11:46 PM, Thanh Ha  > wrote:
> >
> > On 5 May 2016 at 00:31, Thanh Ha  > wrote:
> >
> > Hi didm-devs,
> >
> > Autorelease has been failing since April 27th due to didm-hp
> module failing to compile due to some unresolvable symbols (missing or
> changed
> > dependencies?). Can someone take a look?
> >
> > I opened bug 5843 to track this issue [0].
> >
> > Regards,
> > Thanh
> >
> > [0] https://bugs.opendaylight.org/show_bug.cgi?id=5843
> >
> >
> >
> > Hi Everyone,
> >
> > So taking a look at this closer with Jamo just now. We noticed that
> this patch [0] in openflowplugin removed something that sounds like
> > getTableFeatures() but I'm not at all familiar with how yang maps to
> Java so I could be wrong but could this be the cause of getTableFeatures()
> > being missing?
> >
> > If so how do we fix this?
> >
> > Regards,
> > Thanh
> >
> > [0]
> https://git.opendaylight.org/gerrit/#/c/36559/5/model/model-flow-statistics/src/main/yang/opendaylight-flow-table-statistics.yang
> >
> > ___
> > didm-dev mailing list
> > didm-...@lists.opendaylight.org  didm-...@lists.opendaylight.org>
> > https://lists.opendaylight.org/mailman/listinfo/didm-dev
> >
> >
> >
> >
> > ___
> > release mailing list
> > rele...@lists.opendaylight.org
> > https://lists.opendaylight.org/mailman/listinfo/release
> >
>
>
>
>
>
> ___
> release mailing list
> rele...@lists.opendaylight.org
> 

Re: [openflowplugin-dev] [ovsdb-dev] NetVirt Project Dependencies - Boron Release

[Abhijit Kumbhare]

Ack from OpenFlow plugin.

On Mon, May 9, 2016 at 11:34 AM, Sam Hague  wrote:

> Hi,
>
> would representatives from the following projects respond with an
> acknowledgement of NetVirt's dependence on them:
>
> - ovsdb
> - genius
> - neutron northbound
> - openflowplugin
>
> Thanks, Sam
>
>
>
> ___
> ovsdb-dev mailing list
> ovsdb-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>
>
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] L2Switch Project Dependency

[Abhijit Kumbhare]

Ack.

On Mon, May 9, 2016 at 11:45 AM, Sai MarapaReddy 
wrote:

> Hi Team,
>
> L2switch project depends on the following project:
>
> * OpenFlow Plugin
>
>
> We'd like to get the acknowledgement from the project.
>
>
>
> Regards,
> Sai MarapaReddy
> Brocade Communications
>
> ___
> openflowplugin-dev mailing list
> openflowplugin-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>
>
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

[openflowplugin-dev] [Action Needed] OPENFLOWPLUGIN Beryllium SR2 Distribution Test Failures

[An Ho]

Hi OPENFLOWPLUGIN Team,

There are some distribution test failures in Beryllium SR2 related to your 
project.  My analysis indicates that the failure also appeared in the previous 
SR2-Build-20160430 and SR2-Build-20160425.  

https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-helium-design-only-beryllium/234/

Another action item for the OpenFlowPlugin team: could someone from your team 
verify if the bug has been fixed in the latest build for Beryllium SR2?

https://bugs.opendaylight.org/show_bug.cgi?id=5523

Best Regards,
An Ho

[1] 
https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=185051143
[2] 
https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Beryllium_SR2_Download




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

[openflowplugin-dev] NetVirt Project Dependencies - Boron Release

[Sam Hague]

Hi,

would representatives from the following projects respond with an
acknowledgement of NetVirt's dependence on them:

- ovsdb
- genius
- neutron northbound
- openflowplugin

Thanks, Sam
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

[openflowplugin-dev] OpenFlow Plugin Meeting Minutes May 9, 2016

[Abhijit Kumbhare]

-
Browser Friendly format meeting minutes:
-
http://meetings.opendaylight.org/opendaylight-openflowplugin/2016/openflow_plugin_may_9__2016/o
pendaylight-openflowplugin-openflow_plugin_may_9__2016.2016-05-09-16.04.html


--
Text format friendly for direct linking of lists.opendaylight.org archives:


--

Meeting summary

---

* Agenda  (abhijitkumbhare, 16:05:14)

  * M3 items - bugs for the new design for projects  (abhijitkumbhare,

16:05:44)

  * NSH patch from Yi Yang  (abhijitkumbhare, 16:06:16)

  * BluePrint  (abhijitkumbhare, 16:06:48)

  * TWS topic - merge of OpenFlow projects  (abhijitkumbhare, 16:07:34)

  * Merges pending / code reviews  (abhijitkumbhare, 16:08:05)


* BluePrint  (abhijitkumbhare, 16:08:47)

  * TomP has couple of draft patches for BluePrint  (abhijitkumbhare,

16:10:49)


* M3 items - bugs for the new design from the dependent projects

  (abhijitkumbhare, 16:22:24)

  * L2 switch blocker - goes to the switch but not the stats:

https://bugs.opendaylight.org/show_bug.cgi?id=5822

(abhijitkumbhare, 16:26:40)

  * 5822 needed for migration  (abhijitkumbhare, 16:28:27)

  * Regression of the functionality - target for M4  (abhijitkumbhare,

16:29:41)

  * 5659 - not related to Li Migration  (abhijitkumbhare, 16:31:23)

  * Bug 5602: Blocker for Li migration for VTN project

(abhijitkumbhare, 16:34:08)

  * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=5692  (hideyuki,

16:39:23)

  * Blocker bugs for Li migration default change would be: 5692, 5602 &

4671  (abhijitkumbhare, 16:43:52)

  * ACTION: eshuvka_ to take a quick look at 5602; after that will

likely need jbacigal to take over  (abhijitkumbhare, 16:46:37)

  * ACTION: jbacigal looking into 4671 with michal_rehak

(abhijitkumbhare, 16:47:07)

  * ACTION: hideyuki to take a look into 5692 if it can wait after the

migration - since the estimate from Tomas Slusny for this M4

(abhijitkumbhare, 16:48:20)


* NSH patch from Yi Yang  (abhijitkumbhare, 16:49:22)

  * vishnoianil has some concerns - there was some previous work by

Srini and Ed  (abhijitkumbhare, 16:49:57)

  * Yi’s patch undoes some of the work by Srini & Ed  (abhijitkumbhare,

16:50:26)

  * Yi’s patch modifies some of the existing extensions from Beryllium

(abhijitkumbhare, 16:51:28)

  * LINK: https://git.opendaylight.org/gerrit/#/c/37937/  (vishnoianil,

16:56:04)

Meeting ended at 17:00:25 UTC.


Action items, by person

---

* eshuvka_

  * eshuvka_ to take a quick look at 5602; after that will likely need

jbacigal to take over

* hideyuki

  * hideyuki to take a look into 5692 if it can wait after the migration

- since the estimate from Tomas Slusny for this M4

* jbacigal

  * eshuvka_ to take a quick look at 5602; after that will likely need

jbacigal to take over

  * jbacigal looking into 4671 with michal_rehak
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] table features

[Anil Vishnoi]

okay, although it's been done for li plugin, but i think it will change the
default behavior between two SR (SR2 and SR-3).

On Mon, May 9, 2016 at 1:48 AM, Jozef Bacigal -X (jbacigal - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> Nope, in stable/beryllium we add just this on/off flag, with default
> setting on OFF table features.
>
>
> https://git.opendaylight.org/gerrit/#/c/36506/3
>
>
> Jozef
> --
> *From:* Anil Vishnoi 
> *Sent:* Monday, May 9, 2016 10:37 AM
> *To:* Abhijit Kumbhare
> *Cc:* Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco);
> raphael.amo...@hpe.com; Abhijit Kumbhare; Subhash Singh;
> openflowplugin-dev@lists.opendaylight.org; Luis Gomez Palacios
>
> *Subject:* Re: [openflowplugin-dev] table features
>
> was this patch merged to stable/beryllium as well?
>
> On Tue, Apr 26, 2016 at 8:21 AM, Abhijit Kumbhare 
> wrote:
>
>> OK.
>>
>> On Tue, Apr 26, 2016 at 12:18 AM, Jozef Bacigal -X (jbacigal - PANTHEON
>> TECHNOLOGIES at Cisco)  wrote:
>>
>>> Hi Abhijit,
>>>
>>>
>>> I thought I get an answer from NIC and DIDM guys, but in this case, I
>>> would propose we just make the on/off flag in beryllium SR3 and this
>>> solution we merge only into master M3 as we agreed with Luiz.
>>>
>>>
>>> Jozef
>>> --
>>> *From:* Abhijit Kumbhare 
>>> *Sent:* Monday, April 25, 2016 9:20 PM
>>> *To:* Subhash Singh
>>> *Cc:* Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco);
>>> Abhijit Kumbhare; raphael.amo...@hpe.com;
>>> openflowplugin-dev@lists.opendaylight.org
>>> *Subject:* Re: [openflowplugin-dev] table features
>>>
>>> Hi Jozef,
>>>
>>> Will you be putting https://git.opendaylight.org/gerrit/#/c/36559 into
>>> stable/beryllium after sometime has passed or do you think its better to
>>> avoid it altogether in stable/beryllium?
>>>
>>> Thanks,
>>> Abhijit
>>>
>>> On Mon, Apr 25, 2016 at 5:33 AM, Subhash Singh <
>>> subhash_si...@criterionnetworks.com> wrote:
>>>
 +[Anandhi]

 --
 Regards,
 Subhash Kumar Singh

 On Mon, Apr 25, 2016 at 2:42 PM, Jozef Bacigal -X (jbacigal - PANTHEON
 TECHNOLOGIES at Cisco)  wrote:

> Hi everyone, mainly guys from NIC and DIDM,
>
> I would ask you if you can read and talk about the bug 5464 table
> features
>
> https://bugs.opendaylight.org/show_bug.cgi?id=5464
>
> There are two proposals, first (berylium SR2) that we merge the skip
> flag, which is I would say some "workaround" and set the flag to TRUE so 
> we
> default skip the table features
>
> https://git.opendaylight.org/gerrit/#/c/36506/
>
> and second (boron M3)  this solution of the problem which would lead
> to changes into your projects
>
> https://git.opendaylight.org/gerrit/#/c/36559
>
> We would much appreciate you answers
>
> Jozef
>
>
>

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


>>>
>>
>> ___
>> openflowplugin-dev mailing list
>> openflowplugin-dev@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>>
>>
>
>
> --
> Thanks
> Anil
>



-- 
Thanks
Anil
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

[openflowplugin-dev] tapapp model .

[Ayushi Kumar]

Hi ,

Could you please tell me what are the below files used for in tapapp model.
On the tutorial site it asked to

5.4 Solutions

In the impl directory of the two applications, you will see *.solution
files that implement the two applications. Copy them over the .java files
and recompile to see it in action.

TutorialTapProvider.bidirectional.solution

TutorialTapProvider.unidirectional.solution

is The TutorialTappProvider,java just skeleton and the above two are the
real solutions???

Please help

Regards
Ayushi
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] [controller-dev] New OF message - Serialization and Deserialization Factories

[Michal Polkoráb]

Hi Icaro,


please keep following the second link. If you experience any problems, share 
them or even update the wiki if you solve them.


Michal


From: Icaro Camelo 
Sent: 06 May 2016 22:28
To: Rajasekaran, Monica
Cc: Michal Polkoráb; controller-...@lists.opendaylight.org; 
openflowplugin-dev@lists.opendaylight.org
Subject: Re: [controller-dev] New OF message - Serialization and 
Deserialization Factories

Michal,

Could you please tell me which wiki page (#1 or #2) is the most accurate to the 
Beryllium version?
I'm following the link #2 and I'm getting Java type errors, since you told me 
that the augmentation type has changed since Lithium.

1. 
https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Openflow_Protocol_Library's_extensibility:Basic_Principle_%26_Example
2. 
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Architecture:Extensibility:Action

On Fri, May 6, 2016 at 12:14 PM, Rajasekaran, Monica 
> 
wrote:
Hi Michal,

Got it, I will do that. How does OFJava pick up my module that is defined 
separately ? Do I just import this module and corresponding augment into the 
newly created message factories under serialization & deserialization ?

Thanks

From: Michal Polkoráb 
[mailto:michal.polko...@pantheon.tech]
Sent: Friday, May 06, 2016 2:53 AM
To: Rajasekaran, Monica 
>
Cc: 
controller-...@lists.opendaylight.org;
 
openflowplugin-dev@lists.opendaylight.org;
 Icaro Camelo >

Subject: Re: [controller-dev] New OF message - Serialization and 
Deserialization Factories


Hi Monica,



you should create your own module just like Icaro in his example. Openflowjava 
provides only structures (model) defined in openflow (v1.0 & v1.3) 
specification - specific types should be defined in separate modules.



Michal


From: Rajasekaran, Monica 
>
Sent: 06 May 2016 04:01
To: Michal Polkoráb
Cc: 
controller-...@lists.opendaylight.org;
 
openflowplugin-dev@lists.opendaylight.org;
 Icaro Camelo
Subject: RE: [controller-dev] New OF message - Serialization and 
Deserialization Factories

Hi Michal,

Thanks for your reply. Okay, so in order to do the translation between MD-SAL 
and OFJava, I should add my own augment to “openflow-augments.yang” ? Or should 
I create a separate module for my message as done by Icaro ? I’m a newbie to 
ODL development, so please excuse me if the questions seem basic.

Thanks,
Monica

From: Icaro Camelo [mailto:icam...@inocybe.ca]
Sent: Wednesday, May 04, 2016 2:46 PM
To: Michal Polkoráb 
>
Cc: Rajasekaran, Monica 
>; 
controller-...@lists.opendaylight.org;
 
openflowplugin-dev@lists.opendaylight.org
Subject: Re: [controller-dev] New OF message - Serialization and 
Deserialization Factories

I have followed the aforementioned link and I'm getting an error about not 
finding the augmented target using the same yang file content:

Here's my yang: http://pastebin.com/yhFtbBQw

[ERROR] Failed to execute goal 
org.opendaylight.yangtools:yang-maven-plugin:1.0.0-SNAPSHOT:generate-sources 
(binding) on project of-extension-noviflow-api: yang-to-sources: Unable to 
parse yang files from 
/Users/icarocamelo/Development/inocybe/noviflow-plugin/of-extension-noviflow/of-extension-noviflow-api/src/main/yang:
 Augment target 
'Absolute{path=[(urn:opendaylight:openflow:common:action?revision=2015-02-03)actions-container,
 (urn:opendaylight:openflow:common:action?revision=2015-02-03)action]}' not 
found [at META-INF/yang/of-extension-noviflow.yang:15:4]

Could you please give some insight?

On Wed, May 4, 2016 at 4:17 AM, Michal Polkoráb 
> wrote:

​Hi Monica,



the steps you have already done ensure only the translation between low level 
model (OFJava) and wire protocol. You also need to ensure translation between 
semantic high level model (MD-SAL) and protocol oriented low level model 
(OFJava)​. Please see this wiki page: 
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Architecture:Extensibility
 for more information & also check *-extension-* modules in openflowplugin. The 
combination of openflowplugin code and wiki page should be enough for you to be 
able to finish your 

Re: [openflowplugin-dev] table features

[Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco)]

Nope, in stable/beryllium we add just this on/off flag, with default setting on 
OFF table features.


https://git.opendaylight.org/gerrit/#/c/36506/3


Jozef


From: Anil Vishnoi 
Sent: Monday, May 9, 2016 10:37 AM
To: Abhijit Kumbhare
Cc: Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco); 
raphael.amo...@hpe.com; Abhijit Kumbhare; Subhash Singh; 
openflowplugin-dev@lists.opendaylight.org; Luis Gomez Palacios
Subject: Re: [openflowplugin-dev] table features

was this patch merged to stable/beryllium as well?

On Tue, Apr 26, 2016 at 8:21 AM, Abhijit Kumbhare 
> wrote:
OK.

On Tue, Apr 26, 2016 at 12:18 AM, Jozef Bacigal -X (jbacigal - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:

Hi Abhijit,


I thought I get an answer from NIC and DIDM guys, but in this case, I would 
propose we just make the on/off flag in beryllium SR3 and this solution we 
merge only into master M3 as we agreed with Luiz.


Jozef


From: Abhijit Kumbhare >
Sent: Monday, April 25, 2016 9:20 PM
To: Subhash Singh
Cc: Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco); Abhijit 
Kumbhare; raphael.amo...@hpe.com; 
openflowplugin-dev@lists.opendaylight.org
Subject: Re: [openflowplugin-dev] table features

Hi Jozef,

Will you be putting https://git.opendaylight.org/gerrit/#/c/36559 into 
stable/beryllium after sometime has passed or do you think its better to avoid 
it altogether in stable/beryllium?

Thanks,
Abhijit

On Mon, Apr 25, 2016 at 5:33 AM, Subhash Singh 
>
 wrote:
+[Anandhi]

--
Regards,
Subhash Kumar Singh

On Mon, Apr 25, 2016 at 2:42 PM, Jozef Bacigal -X (jbacigal - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:
Hi everyone, mainly guys from NIC and DIDM,

I would ask you if you can read and talk about the bug 5464 table features

https://bugs.opendaylight.org/show_bug.cgi?id=5464

There are two proposals, first (berylium SR2) that we merge the skip flag, 
which is I would say some "workaround" and set the flag to TRUE so we default 
skip the table features

https://git.opendaylight.org/gerrit/#/c/36506/

and second (boron M3)  this solution of the problem which would lead to changes 
into your projects

https://git.opendaylight.org/gerrit/#/c/36559

We would much appreciate you answers

Jozef




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




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




--
Thanks
Anil
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Re: [openflowplugin-dev] Fwd: openflow plugin - statistics collecting time

[Anil Vishnoi]

you can install odl-openflowplugin-flow-services-rest and then configure
the stats collection value in the mentioned xml file, that should solve
your problem.

Anil

On Fri, May 6, 2016 at 8:08 AM, Shuva Jyoti Kar <
shuva.jyoti@ericsson.com> wrote:

> For the difference:
>
>
> https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:He_vs_Li_comparison
>
>
>
> for other related topics:
>
> https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Main
>
>
>
> *From:* Rui Q [mailto:mail.to.esta...@gmail.com]
> *Sent:* Friday, May 06, 2016 4:42 PM
>
> *To:* Shuva Jyoti Kar
> *Cc:* openflowplugin-dev@lists.opendaylight.org;
> openflowplugin-us...@lists.opendaylight.org
> *Subject:* Re: [openflowplugin-dev] Fwd: openflow plugin - statistics
> collecting time
>
>
>
> Didn't know that. Thanks for the info.
>
> Can you tell me what's the difference? or point me to some page/wiki.
>
> Thanks
>
>
>
> 2016-05-06 3:31 GMT+01:00 Shuva Jyoti Kar :
>
> Yes Rui, you are correct.  But you need to install odl-openflowplugin-all
> feature for this.
>
>
>
> Please donot install both odl-openflowplugin-all  and
> odl-openflowplugin-all-li, as both of these are two separate models of the
> ofplugin.
>
>
>
> *From:* Rui Q [mailto:mail.to.esta...@gmail.com]
> *Sent:* Thursday, May 05, 2016 8:21 PM
>
>
> *To:* Shuva Jyoti Kar
> *Cc:* openflowplugin-dev@lists.opendaylight.org;
> openflowplugin-us...@lists.opendaylight.org
> *Subject:* Re: [openflowplugin-dev] Fwd: openflow plugin - statistics
> collecting time
>
>
>
> What about the solution described in here:
>
>
> https://ask.opendaylight.org/question/3354/rest-api-response-time/?comment=11534#comment-11534
>
> "
> Once you have installed the controller and deployed the features that
> enable the openflow services you will find a config file in the
> distribution subfolder "etc/opendaylight/karaf/30-statistics-manager.xml"
> In that file you change the default from 3000ms (3s) to something smaller
> or larger as needed. I believe a restart of the controller is needed after
> changing that file, and that file will not be created until the feature(s)
> that use it are enabled.
> "
>
> do you think it would work?
>
>
>
> 2016-05-05 15:49 GMT+01:00 Rui Q :
>
> If I was using another model(?)/version(?) do you think it would be
> possible?
>
>
>
> Thanks
>
>
>
>
>
> 2016-05-05 11:54 GMT+01:00 Shuva Jyoti Kar :
>
> You are using the lithium mode of the ofplugin. I donot see any place of
> tuning statistics as of today, we can definitely make it configurable, but
> as of today that’s not the case.
>
>
>
> Thanks
>
> Shuva
>
>
>
> *From:* Rui Q [mailto:mail.to.esta...@gmail.com]
> *Sent:* Thursday, May 05, 2016 4:21 PM
> *To:* Shuva Jyoti Kar
> *Cc:* openflowplugin-dev@lists.opendaylight.org;
> openflowplugin-us...@lists.opendaylight.org
> *Subject:* Re: [openflowplugin-dev] Fwd: openflow plugin - statistics
> collecting time
>
>
>
> Thanks for replying Shuva.
>
> I'm not sure if I can answer you.
>
> Maybe this print can help:
>
> opendaylight-user@root>feature:list -i | grep openflow
>
> odl-openflowjava-protocol| 0.7.0-Beryllium  | x |
> odl-openflowjava-0.7.0-Beryllium | OpenDaylight :: Openflow Java ::
> Protocol
> odl-openflowplugin-all-li| 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> All
> odl-openflowplugin-southbound-li | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> Li southBound A
> odl-openflowplugin-flow-services-li  | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> Flow Services
> odl-openflowplugin-nsf-services-li   | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: OpenflowPlugin ::
> NSF :: Services
> odl-openflowplugin-nsf-model-li  | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: OpenflowPlugin ::
> NSF :: Model
> odl-openflowplugin-flow-services-rest-li | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> Flow Services :
> odl-openflowplugin-flow-services-ui-li   | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> Flow Services :
> odl-openflowplugin-app-config-pusher-li  | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> app - default c
> odl-openflowplugin-app-lldp-speaker-li   | 0.2.0-Beryllium  | x |
> openflowplugin-li-0.2.0-Beryllium| OpenDaylight :: Openflow Plugin ::
> app lldp-speake
> odl-tsdr-openflow-statistics-collector   | 1.1.0-Beryllium  | x |
> odl-tsdr-1.1.0-Beryllium | OpenDaylight :: TSDR :: Openflow
> 

Re: [openflowplugin-dev] [opnfv-tech-discuss] [SFC] [sfc-dev] ovs nsh patches are available for public use

[Anil Vishnoi]

Hi Yi,

let's have this discussion over the gerrit, to capture the context for
other interested folks.

Thanks
Anil

On Sun, May 8, 2016 at 11:19 PM, Yang, Yi Y  wrote:

> Hi, Anil
>
>
>
> Maybe you don't know the context, the previous nsh support in
> Openflowplugin project is for the old nsh implemented CISCO guy Pretish
> did, but now CISCO has agreed Intel to take over their work, ovs didn't
> include any code for nsh so far, Intel is doing this, but the road to go is
> long, CISCO and Redhat and Intel have had an agreement on this, we are NSH
> implementation owner, the part in ODL (this patch you reviewed) is part of
> this effort.
>
>
>
> Nobody or no organization is defining NSH Openflow interface standard, our
> NSH implementation is standard J
>
>
>
> Current issue is CISCO ovs nsh support patch isn’t maintained any more, so
> I published one new version based on the latest ovs, it is just to make
> sure we can have a new version available for ODL integration, all the
> people are anticipating it.
>
>
>
> *From:* Anil Vishnoi [mailto:vishnoia...@gmail.com]
> *Sent:* Monday, May 09, 2016 2:00 PM
>
> *To:* Yang, Yi Y 
> *Cc:* Dave Neary ; Thomas F Herbert <
> therb...@redhat.com>; Brady Allen Johnson <
> brady.allen.john...@ericsson.com>; Sam Hague ; Benc,
> Jiri ; opendaylight sfc ;
> ovsdb-...@lists.opendaylight.org; opnfv-tech-disc...@lists.opnfv.org;
> openflowplugin-dev@lists.opendaylight.org
> *Subject:* Re: [openflowplugin-dev] [opnfv-tech-discuss] [SFC] [sfc-dev]
> ovs nsh patches are available for public use
>
>
>
> Yes, I just want to make sure that the OpenFlow interfaces (NXM extension
> for NSH) are finalized, so that once we push this work to openflowplugin
> repo, it's based on the standard and approved interfaces, rather than
> patches sitting under review where there is a scope of change later. Are
> these patches being discussed with upstream OVS, atleast the extension
> (match's/actions) or are they still present in your local repo?
>
>
>
> So looking at the patch, it is removing some of the NSH related work
> (extensions for match/action NSH field work done by srini and set NSHC
> fields work by Ed).
>
>
>
> https://git.opendaylight.org/gerrit/#/c/12418/ (I believe this work is
> based on the existing Nicira extension, set NSH Service Path ID and NSH
> Service Path Index ).
>
> https://git.opendaylight.org/gerrit/#/c/20155/ (actions/match on 4
> context headers for md_type=0x1, not sure we have nicira extension defined
> for NSH context headers)
>
>
>
> Although I looked at the nicira-ext.h, but i didn't find any extensions
> related to above patches. You removed/renamed some of these existing
> extension (set_nsh --> push_nsh), so it's bit of confusing to me the
> current status of NSH support in OVS.
>
>
>
> Srini,Ed, can you please provide some more details about your patches,
> because YI's patch will have impact on your patches.
>
>
>
> Lets discuss this further over the Yi's (37937) patch.
>
>
>
> Thanks
>
> Anil
>
>
>
>
>
> On Sun, May 8, 2016 at 10:33 PM, Yang, Yi Y  wrote:
>
> I have abandoned them.
>
>
>
> For the last question you asked, I’m not sure what NSH extension you said
> means. Current NSH implementation isn’t upstreamed to ovs and Linux kernel,
> this will take very long time, we can’t control, but its interface to
> Openflow is finalized, that is why  I published
>
> ​​ 
>
> https://github.com/yyang13/ovs_nsh_patches and pushed
> https://git.opendaylight.org/gerrit/#/c/37937/. Can this answer your last
> question?
>
>
>
> *From:* Anil Vishnoi [mailto:vishnoia...@gmail.com]
> *Sent:* Monday, May 09, 2016 12:11 PM
>
>
> *To:* Yang, Yi Y 
> *Cc:* Dave Neary ; Thomas F Herbert <
> therb...@redhat.com>; Brady Allen Johnson <
> brady.allen.john...@ericsson.com>; Sam Hague ; Benc,
> Jiri ; opendaylight sfc ;
> ovsdb-...@lists.opendaylight.org; opnfv-tech-disc...@lists.opnfv.org;
> openflowplugin-dev@lists.opendaylight.org
> *Subject:* Re: [openflowplugin-dev] [opnfv-tech-discuss] [SFC] [sfc-dev]
> ovs nsh patches are available for public use
>
>
>
> Shall I abandon 30481 and 27643?
>
>
>
> Can you please answer my last question in the previous mail.
>
>
>
> Anil
>
>
>
> On Sun, May 8, 2016 at 8:57 PM, Yang, Yi Y  wrote:
>
> Hi, Anil
>
>
>
> https://git.opendaylight.org/gerrit/#/c/37937/ is the final version, it
> included everything for NSH support, not any other thing is needed any
> more.I have verified it in our sfc103 demo and my Eth+NSH demo, everything
> is ok.
>
>
>
>
>
> *From:* Anil Vishnoi [mailto:vishnoia...@gmail.com]
> *Sent:* Monday, May 09, 2016 11:50 AM
> *To:* Yang, Yi Y 
> *Cc:* Dave Neary