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

2016-05-09 Thread Isaku Yamahata 
Ack from Neutron northbound.

On Mon, May 09, 2016 at 02:34:56PM -0400,
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

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


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

Re: [openflowplugin-dev] table features

2016-05-09 Thread Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Cisco) 
You propose to leave the flag (skip table features) false ? Just not to change 
default behavior?


Jozef


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

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) mailto:jbaci...@cisco.com>> 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 mailto:vishnoia...@gmail.com>>
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 
mailto:abhijitk...@gmail.com>> wrote:
OK.

On Tue, Apr 26, 2016 at 12:18 AM, Jozef Bacigal -X (jbacigal - PANTHEON 
TECHNOLOGIES at Cisco) mailto:jbaci...@cisco.com>> 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 mailto:abhijitk...@gmail.com>>
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 
mailto: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) mailto:jbaci...@cisco.com>> 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

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

2016-05-09 Thread 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

2016-05-09 Thread Yang, Yi Y 
Ok, all the comments are in https://git.opendaylight.org/gerrit/#/c/37937/, I 
have added my comments, I just pasted them here for your reference. You and 
Anil aren’t in this discussion context, so you don’t know them.


“””


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 ☺

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.


Even NSH isn't standardized, it is now IETF draft, so NSH itself will be 
possibly subject to change :-), we're struggling to upstream it to ovs, but the 
progress is very low, Redhat guy has paved the road for VxLAN-gpe in Linux 
net-next, we're refactoring our NSH kernel patch based on this VxLAN-gpe 
implementation, this low progress obviously impacts on our ODL use.

This patch is to finalize Openflow interface, the final upstreamed version in 
ovs will follow these Openflow interface. We need to use these to fix our 
ovsdb/netvirt and sfc integration issue.

We are only one NSH implementer, don't worry other people will change it.

Because NSH support isn't upstreamed to ovs, so it is impossible to be 
compatible backwards with Beryllium, Openflowplugin must be changed to adapt to 
ovs changes, action ID and match field ID are always changing before upstream.

We're trying our best to make sure the final upstreamed version in ovs won't 
need changes in Openflowplugin or just need tiny changes, such as action ID and 
match field ID (this depends on when they are upstreamed, the more we need to 
change, the later they are upstreamed).
“””

From: Abhijit Kumbhare [mailto:abhijitk...@gmail.com]
Sent: Tuesday, May 10, 2016 9:46 AM
To: Yang, Yi Y ; openflowplugin-dev@lists.opendaylight.org
Subject: Re: [openflowplugin-dev] OpenFlow Plugin Meeting Minutes May 9, 2016

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 
mailto:yi.y.y...@intel.com>> 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/opendaylight-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

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

2016-05-09 Thread 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)

2016-05-09 Thread 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)

2016-05-09 Thread 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

2016-05-09 Thread 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
> https://lists.opendaylight.org/mailman/listinfo/release
>
>
>
>
>
>
>
>
>
> ___
> openflowplugin-dev mailing list
> openflowplugin-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>
>
___
openfl

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

2016-05-09 Thread Manikantan, Anandhi 
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 
; rele...@lists.opendaylight.org; 
didm-...@lists.opendaylight.org; openflowplugin-dev 
; Thanh Ha 

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 
mailto:thanh...@linuxfoundation.org>> wrote:
Thanks Alexis,

Can someone review and merge the patch?

Thanks,
Thanh


On 6 May 2016 at 08:45, Alexis de Talhouët 
mailto:adetalho...@inocybe.com>> 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 
mailto:adetalho...@inocybe.com>> 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 
mailto:thanh...@linuxfoundation.org>> 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 
mailto:thanh...@linuxfoundation.org>> 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 
mailto:jluhr...@gmail.com>> 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 
> mailto:thanh...@linuxfoundation.org> 
> >> 
> wrote:
>
> On 5 May 2016 at 00:31, Thanh Ha 
> mailto:thanh...@linuxfoundation.org> 
> >> 
> 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 
> >
> 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
https://lists.opendaylight.org/mailman/listinfo/release




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

Re: [openflowplugin-dev] [controller-dev] Southbound plugin listeners?

2016-05-09 Thread Ryan Dietrich 
Alternative approaches to get a PacketInMessage into my southbound plugin.

1. Figure out how to add a second OpenflowProtocolListener to 
“ConnectionManagerImpl”. (It appears this can only have a single value).  Also 
looked at ConnectionAdapterImpl, as that is where PacketInMessages are 
dispatched from.
2. Try to figure out how to transform a “PacketReceived” into a 
“PacketInMessage”.  There are plenty of classes that do the opposite 
(openflowplugin/openflowplugin-impl/src/main/java/org/opendaylight/openflowplugin/impl/translator/PacketReceivedTranslator.java)
3. Try to figure out how to access MDController from within my plugin, so I can 
register an additional Translator for PacketInMessage. (The tests use the 
getMessageTranslators function, but MDController doesn’t seem to be a singleton 
that I can access from within my plugin, I looked in OpenflowPluginProvider).
4. Figure out how a PacketInMessage is instantiated, and work backwards from 
there.  I started with PacketInMessageBuilder, then to PacketInMessageFactory, 
then to MessageDeserializerInitializer.  (I got lost while trying to figure out 
what is calling the 
5. See if “MessageSpy” lets me subscribe to PacketInMessages?

I’m still digging.  I’ve been reading the docs as well, the file below 
confirmed the tracing I had done by hand, but didn’t show my any entry points 
where a southbound plugin can access or the data as it is being processed.  (my 
primary goal is to not alter any source code of any of my dependencies, just 
have my own little plugin off to the side)

docs/manuals/developer-guide/src/main/asciidoc/openflowjava/odl-openflowjava-protocol-dev.adoc

Again, any direction on how to receive PacketInMessages in a southbound plugin, 
or how to transform a “PacketReceived” into a “PacketInMessage” would be 
appreciated.

-Ryan Dietrich


> On May 6, 2016, at 3:13 PM, Luis Gomez  wrote:
> 
> cc-ing openflow people.
> 
>> On May 6, 2016, at 1:41 PM, Ryan Dietrich > > wrote:
>> 
>> So, I have a working southbound plugin using the PacketProcessingListener.  
>> My goal is to read the payload of the OpenFlow 1.3 “PacketIn” message.
>> This “per packet” approach seems unwieldy, as I am parsing both the Ethernet 
>> header as well as the IP and TCP headers.  Is there a “shortcut” ?
>> 
>> I went searching for a simpler approach and found this file:
>> 
>> controller/opendaylight/md-sal/sal-binding-broker/src/main/java/org/opendaylight/controller/md/sal/binding/impl/BindingDOMNotificationServiceAdapter.java
>> 
>> This is what my plugin calls when it registers itself as a packet handler 
>> (implementing the “onPacketReceived”).
>> 
>> 1. I tried to create another listener using the “OpenflowProtocolListener”, 
>> and used the same approach to register it, but it is never called (I have an 
>> OVS pointed to my controller, and the PacketProcessingListener is logging 
>> like crazy).  Do I need to add anything to my yang file beyond the 
>> notification service?  Or some other configuration that is not immediately 
>> apparent?
>> 
>> 2. Can you even listen to PacketInMessage using the notification service?  
>> Or are they considered RPC, and do you implement that differently (similar 
>> to how Toaster implements RPC)?
>> 
>> …
>> 
>> Long story short, I’m currently using the PacketProcessingListener, and I 
>> tried to use OpenflowProtocolListener the same way, to get the 
>> “onPacketInMessage” to fire, but it is not working, and I’m not sure if it 
>> is configuration related, or me doing something totally incorrect.
>> 
>> Thanks to anyone who can give me a pointer in the right direction.
>> 
>> -Ryan Dietrich
>> ___
>> controller-dev mailing list
>> controller-...@lists.opendaylight.org 
>> 
>> https://lists.opendaylight.org/mailman/listinfo/controller-dev
> 

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

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

2016-05-09 Thread 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] [Action Needed] OPENFLOWPLUGIN Beryllium SR2 Distribution Test Failures

2016-05-09 Thread Abhijit Kumbhare 
I understand that there were only the 2 distribution test failures (found
to be non-issues)  that you mentioned that were also in the previous SR2
builds. Since we are not having those earlier failures from last week for
Li clustering as per the integration tests - then it means that
https://bugs.opendaylight.org/show_bug.cgi?id=5523 is fixed.

On Mon, May 9, 2016 at 11:42 AM, An Ho  wrote:

> 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

Re: [openflowplugin-dev] L2Switch Project Dependency

2016-05-09 Thread 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] L2Switch Project Dependency

2016-05-09 Thread Sai MarapaReddy 
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] [Action Needed] OPENFLOWPLUGIN Beryllium SR2 Distribution Test Failures

2016-05-09 Thread 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

2016-05-09 Thread 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

2016-05-09 Thread 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

[openflowplugin-dev] FaaS project dependency - Boron release

2016-05-09 Thread Xingjun Chu 
Hi All,

The 'FaaS' project is dependent on the following projects -


1.   YANG Tools

2.   MDSAL

3.   OVSDB

4.   OpenflowPlugin

5.   Odlparent

6.   Controller

7.   Netconf

Please acknowledge the dependency to support our M2 status update.

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

Re: [openflowplugin-dev] table features

2016-05-09 Thread 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 .

2016-05-09 Thread 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

2016-05-09 Thread 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 
mailto:monica.rajaseka...@us.fujitsu.com>> 
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 
mailto:monica.rajaseka...@us.fujitsu.com>>
Cc: 
controller-...@lists.opendaylight.org;
 
openflowplugin-dev@lists.opendaylight.org;
 Icaro Camelo mailto:icam...@inocybe.ca>>

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 
mailto:monica.rajaseka...@us.fujitsu.com>>
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 
mailto:michal.polko...@pantheon.tech>>
Cc: Rajasekaran, Monica 
mailto:monica.rajaseka...@us.fujitsu.com>>; 
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 
mailto:michal.polko...@pantheon.tech>> 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 implementation.



Michal




From: Rajasekaran, Monica 
mailto:monica.rajaseka...@us.fujitsu.com>>
Sent: 03 May 2016 17:13
To: Michal Polkoráb; 
controller-...@lists.opendaylight.org

Re: [openflowplugin-dev] table features

2016-05-09 Thread 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 
mailto:abhijitk...@gmail.com>> wrote:
OK.

On Tue, Apr 26, 2016 at 12:18 AM, Jozef Bacigal -X (jbacigal - PANTHEON 
TECHNOLOGIES at Cisco) mailto:jbaci...@cisco.com>> 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 mailto:abhijitk...@gmail.com>>
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 
mailto: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) mailto:jbaci...@cisco.com>> 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] table features

2016-05-09 Thread Anil Vishnoi 
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
___
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

2016-05-09 Thread 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
> Statistics Collec
> odl-openflowplugin-all   | 0.2.0-Beryllium  | x |
>