Could you please paste the links for builds which are NOT-OK. I can take
look on Monday.
On Sunday, August 28, 2016, Jamo Luhrsen wrote:
> For the L2Switch release review Monday morning, I have the following
> analysis of their
> upstream CSIT for boron, using the most recent boron job result.
>
Thanks Luis,
I did try re-producing this manually but couldn't.
On Mon, Aug 29, 2016 at 4:36 PM, Luis Gomez wrote:
> Actually I think I figured out the issue with l2switch basic csit: For
> some reason after we changed to new OF plugin (old plugin is fine) the
> l2switch app does not work very
Luis / An,
Update from L2switch:-
The below build didn't run (no results were found). Most probably since the
VMs are not responding for SSH.
https://jenkins.opendaylight.org/releng/job/l2switch-csit-1node-switch-all-boron/350/console
The other build failures should be non-blocker.
On Tue, Sep
Thanks Jamo / An.
I have updated spreadsheet.
There is a known issue ( BUG 6575 -
https://bugs.opendaylight.org/show_bug.cgi?id=6575) which is not a blocker,
which i have marked in the spreadsheet.
Regards,
Sai MarapaReddy
On Tue, Sep 13, 2016 at 11:03 AM, Jamo Luhrsen wrote:
>
>
>
Hi Artur,
The known problem is still open. Also the reason for not updating the
attaching point is mentioned in the link.
Please feel free to open a bug and propose a solution including details so
that it can be tracked and worked towards resolution.
On Tue, Sep 20, 2016 at 8:40 AM, Luis Gomez
Zeller
6. Do you confirm that the list of Active Project Committers is updated and
accurate? Yes
[1] https://wiki.opendaylight.org/view/Simultaneous_Release:
Carbon_Release_Plan
Regards,
Sai MarapaReddy
Software Engineer
___
L2switch-dev mailing list
. Project PTL: Sai MarapaReddy
6. Do you confirm that the list of Active Project Committers is updated and
accurate? Yes
[1] https://wiki.opendaylight.org/view/Simultaneous_Release:
Carbon_Release_Plan
On Mon, Oct 3, 2016 at 10:43 AM, Sai MarapaReddy
wrote:
>
>
> 1. L2switc
This is not related to other l2switch bug.
Seems Alexis has patches for different patches including l2switch.
On Tue, Oct 18, 2016 at 10:06 AM, Abhijit Kumbhare
wrote:
> Adding L2 switch, etc.
>
> Shuva's comment: Given the conversations on the bug report, lets have the
> l2 folks have the firs
Thanks Luis.
Yes that is drop-all flow. Please let us know if you need any further help
from l2switch.
On Tue, Oct 18, 2016 at 1:03 PM, Luis Gomez wrote:
> Actually this is the drop flow so it is expected, anyway going deeper into
> l2switch test issues I see:
>
> - The address tracker issue is
ter
> restarting mininet? like what is today in the code to flush the address
> cache and why this is not working when mininet restarts?
>
> BR/Luis
>
> On Oct 18, 2016, at 6:56 PM, Sai MarapaReddy
> wrote:
>
> Thanks Luis.
>
> Yes that is drop-all flow. Pleas
ing mininet, so are you sure switch
> disconnect/connect does not impact address tracker cache?
>
> BR/Luis
>
> On Oct 19, 2016, at 3:37 AM, Sai MarapaReddy
> wrote:
>
> Hi Luis,
>
> Addresses will be removed if this condition [1] passes.
>
> Default value of
Done. Thanks Jamo.
On Thu, Oct 20, 2016 at 10:39 AM, Jamo Luhrsen wrote:
>
>
> On 10/19/2016 11:26 PM, Sai MarapaReddy wrote:
> > Address tracker tries [1] to read any existing address from data store.
> My guess is in the case of immediate restart of
> > mininet , addre
ns.opendaylight.org/releng/job/l2switch-csit-
> 1node-switch-only-boron/795/
>
> Please let us know if we can help with anything.
>
> BR/Luis
>
> On Oct 20, 2016, at 10:54 AM, Sai MarapaReddy
> wrote:
>
>
> Done. Thanks Jamo.
>
> On Thu, Oct 20, 2016 at 1
An Ho
>
>
>
> [1] https://bugs.opendaylight.org/show_bug.cgi?id=6575
>
> [2] https://git.opendaylight.org/gerrit/#/c/47186/
>
>
>
>
>
> *From:* Luis Gomez [mailto:ece...@gmail.com ]
> *Sent:* Monday, October 24, 2016 5:14 PM
> *To:* Sai MarapaReddy
> *Cc:*
Bug 6956 has been verified and comments are posted on the Bugzilla.
We should be good.
Regards,
Sai MarapaReddy
On Thu, Nov 3, 2016 at 8:46 AM, An Ho wrote:
> Hi Sai and L2SWITCH,
>
>
>
> I believe the following bugs have been verified as fixed in Boron SR1
> Build 20161030.
L2switch
1. Project Lead Contact: Sai MarapaReddy (sai.marapare...@gmail.com)
2. Project Contact: Sai MarapaReddy (sai.marapare...@gmail.com)
3. Test Contact: Sai MarapaReddy (sai.marapare...@gmail.com)
4. Documentation Contact: Sai MarapaReddy (sai.marapare...@gmail.com)
5. Draft Release
Hi An,
I didn't get time to work on the bug. I request to carry forward it to SR3.
On Thu, Dec 1, 2016 at 9:49 AM, An Ho wrote:
> Hi L2SWITCH and OPENFLOWPLUGIN Team,
>
> We would like to kindly request an update on this OPENFLOWPLUGIN/L2SWITCH
> Boron Blocker Bug? Please let us know the ETA f
*From:* openflowplugin-dev-boun...@lists.opendaylight.org [
> mailto:openflowplugin-dev-boun...@lists.opendaylight.org
> ] *On Behalf Of *Sai
> MarapaReddy
> *Sent:* Friday, December 02, 2016 2:33 AM
> *To:* An Ho
> *Cc:* l2switch-dev@lists.opendaylight.org; openflowplugin-dev@lists.
> opendaylight.
L2Switch Carbon M2 Status
-
1. Does your project have any updates on any previously-incomplete items
from prior milestone readouts? No
2. Were project-specific deliverables planned for this milestone delivered
successfully? Yes (although there were none)
Hi Anil Belur,
The error corresponds to port being used by another application.
I tried following steps in my local setup.
git clone https://git.opendaylight.org/gerrit/l2switch
cd l2switch; mvn clean install and it gives me a success build.
Could you please retry.
Regards,
Sai MarapaReddy
L2switch
Functionality Freeze:
1. Final list of externally consumable APIs defined: *Yes*
2. Are all your inter-project dependencies resolved (i.e., have the other
projects you were counting on given you what you needed)? *Yes*
3. Were there any project-specific deliverables planned for
uses ports
(that are supposedly used by controller) we see this error.
Regards,
Sai MarapaReddy
On Wed, Jan 25, 2017 at 3:57 PM, Thanh Ha
wrote:
> Hi Sai,
>
> Not sure I understand what you're saying here. Autorelease builds and
> tests all projects in ODL. If l2switch and an
Same is the case with l2switch [1]
[1]
https://lists.opendaylight.org/pipermail/l2switch-dev/2017-January/001350.html
On Wed, Feb 1, 2017 at 5:16 PM, Katie Zhang
wrote:
> Great ! Thanks a lot for contributing to the ODL community.
>
> Thanks
> Katie
>
> On Wed, Feb 1, 2017 at 5:15 PM, Ryan Goul
Thanks An.
It is merged.
On Fri, Feb 3, 2017 at 11:55 AM, An Ho wrote:
> Hi Sai MarapaReddy and L2SWITCH Team,
>
> https://git.opendaylight.org/gerrit/#/c/50867/
>
> We would like to kindly ask for your assistance in helping us merge the
> above patch [1], which is currently
l2switch
1. Please provide updates on any previously-incomplete items from prior
milestone readouts.
N/A
2. Has your project achieved API freeze such that all externally accessible
Stable or Provisional APIs will not be modified after now?
Yes, No new API.
3. Do you have content in your
gevity/stability for
each stable feature? (Yes/No)
* Yes https://jenkins.opendaylight.org/releng/view/l2switch/
Regards,
Sai MarapaReddy
___
L2switch-dev mailing list
L2switch-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
://github.com/opendaylight/l2switch/blob/master/loopremover/implementation/src/main/java/org/opendaylight/l2switch/loopremover/topology/NetworkGraphImpl.java#L39
Regards,
Sai MarapaReddy
On Sun, Apr 9, 2017 at 6:31 PM, Shahram Gohardehi <
shahram.gohard...@gmail.com> wrote:
> Hi
>
> This i
L2switch have some hooks for cluster [1], but has never been tested. I
would request to file a bug and contribute for the project.
[1]
https://github.com/opendaylight/l2switch/tree/master/hosttracker/implementation/src/main/java/org/opendaylight/l2switch/hosttracker/plugin/internal
Regards,
Sai
Thanks Jamo.
It is being tracked as part of Bug 6654.
Regards,
Sai MarapaReddy
On Thu, May 18, 2017 at 4:51 PM, Jamo Luhrsen wrote:
> Hi l2switch,
>
> this is just to provide some feedback for the release review forthcoming.
>
> I didn't find your release notes gerrit, so
Hi Fernando,
Please check if the rules are installed on switch.
As long as rules are installed on switch, the change in priority will be
applied for traffic flow.
If the action is drop, then packets can be discarded accordingly.
On Fri, May 26, 2017 at 6:32 PM, FERNANDO VINICIO BECERRA CAMACHO
Done. Thanks.
Regards,
Sai
On Wed, Jun 7, 2017 at 11:43 AM Colin Dixon wrote:
> There are two pending comments that need to be addressed here:
> https://git.opendaylight.org/gerrit/57401
>
> Cheers,
> --Colin
>
>
___
L2switch-dev mailing list
L2switch
Removing odl-l2switch-switch removes the features that are dependent, hope
this [1] helps.
[1] https://wiki.opendaylight.org/view/File:Feature_dependency_graph.PNG
Regards,
Sai MarapaReddy
On Sun, Jun 18, 2017 at 7:50 PM, Phil Robb
wrote:
> Hi Jorge:
>
> I'm also adding the L2 s
: Application
4. Do you confirm that the list of Active Project Committers is
updated and accurate? Yes
5. Project PTL Contact: Sai MarapaReddy / sai.marapareddy at gmail dot com / Sai
6. Project Contact: Sai MarapaReddy / sai.marapareddy at gmail dot com / Sai
7. Test Contact: Sai MarapaReddy
+1 for Evan.
On Mon, Mar 19, 2018 at 3:11 PM, Evan Zeller wrote:
> l2switch-dev,
>
> Per Sai's request I am beginning an election process for l2switch PTL. I
> hereby nominate myself as PTL. Given we are the only 2 active committers,
> if there are no other nominations I believe we can proceed t
Hi Luis,
When checking through below errors, I found the test plans contains
repetition of test suites here
https://github.com/opendaylight/integration-test/blob/master/csit/testplans/l2switch-switch.txt
Any idea why do we have that ?
Regards,
Sai MarapaReddy
Brocade
On Wed, Mar 2, 2016 at
back. It's sort of a lazy approach to
> looping
> the test :)
>
> Thanks,
> JamO
>
> On 03/02/2016 11:16 AM, Sai MarapaReddy wrote:
> > Hi Luis,
> >
> > When checking through below errors, I found the test plans contains
> repetition of test suites
Hi An Ho,
I am interested in contributing to l2switch features.
I will edit the page here (
https://wiki.opendaylight.org/view/L2_Switch:Main ) which accommodates the
Boron release plan.
Please let me know if i am missing something.
Regards,
Sai MarapaReddy
Brocade Communications
On Wed, Mar
ween
switches/hosts. (image is attached for easy reference).
Also
http://:8181/restconf/operational/network-topology:network-topology/
gives the output of network topology information.
Please let us know further information as Andre mentioned.
Regards,
Sai MarapaReddy
Brocade Communications
On Fri,
Tali,
ICMPv4 decoder will be good to have for Boron, but not committed feature.
Regards,
Sai Reddy
On Sun, Apr 3, 2016 at 4:29 AM, Ben-Meir, Tali
wrote:
> Hi,
>
>
>
> I am looking for a replacement for
> org.opendaylight.controller.sal.packet.ICMP and noticed Boron release plan
> will include
-rf :distribution-karaf
Regards,
Sai MarapaReddy
___
L2switch-dev mailing list
L2switch-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
; the new, correct artifacts, and go successful.
>
>
>
> Regards,
>
> Hideyuki Tai
>
>
>
> *From:* vtn-dev-boun...@lists.opendaylight.org [mailto:
> vtn-dev-boun...@lists.opendaylight.org] *On Behalf Of *Tai, Hideyuki
> *Sent:* Monday, April 11, 2016 13:20
> *To:* An Ho ; Sai M
Hi Luis,
Please correct me if i am wrong here.
You have checked below Case 3 & Case 4 and found errors.
Case 3 errors :-
https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/291/robot/report/log.html
Case 4 erros :-
https://jenkins.opendaylight.org/rele
<https://meetings.opendaylight.org/opendaylight-meeting/2016/l2_switch_interest_call/opendaylight-meeting-l2_switch_interest_call.2016-04-20-20.02.txt>*
Feel free to watch/contribute to the meeting minutes at
#opendaylight-meeting during the meeting time.
Please let me know if you have any questions.
,
Sai MarapaReddy
Brocade Communications
___
L2switch-dev mailing list
L2switch-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
ase give it one more try with these patches ?
Regards
Sai MarapaReddy
Brocade Communications
On Fri, Apr 15, 2016 at 3:57 PM, Luis Gomez wrote:
> I think the table is more like this:
>
> Case 1: Current L2 switch (should point to OFP-He) & Current OFP
> (default plugin is
Thanks Yasuda.
On Wed, Apr 20, 2016 at 5:40 PM, Shigeru Yasuda
wrote:
> Hi Sai,
>
> On [Wed, 20 Apr 2016 15:51:03 -0700],
> Sai MarapaReddy wrote:
>
> >> I have a question regarding on bug 2501 (
> >> https://bugs.opendaylight.org/show_bug.cgi?id=25
@Amit/Abhijit - Agree with you, we will likely abandon patch.
@Luis - I will rebase and push a patch so that it is ready for merge.
Regards,
Sai MarapaReddy
On Thu, Apr 21, 2016 at 10:12 AM, Amit Mandke (ammandke) wrote:
> Please abandon the patch on beryllium if decision is made to not cha
to the pom and feature changes in this patch. I
> don’t see those anymore in the commit? How would this change in to Li
> feature? Am I missing something?
> >
> > -Amit
> >
> >
> > From: Sai MarapaReddy
> > Date: Thursday, April 21, 2016 at 10:
Hi Luis,
Patch (https://git.opendaylight.org/gerrit/#/c/33303/) is good now.
Could you please run check once.
Regards,
Sai MarapaReddy
On Fri, Apr 22, 2016 at 4:22 PM, Amit Mandke (ammandke)
wrote:
> Oh ok.
>
> -Amit
>
>
>
>
>
>
>
>
> On 4/22/16, 11:31 A
ny questions.
Regards,
Sai MarapaReddy
Software Engineer
Brocade Communications
___
L2switch-dev mailing list
L2switch-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
org.opendaylight.alto.basic:alto-simple-ecs-impl:xml:config:0.2.2-beryllium-daily-v201604270031
in defaultlocal
(file:/tmp/distribution-karaf-0.4.2-beryllium-daily-v201604270031/system/)
Please let us know your view.
Regards,
Sai MarapaReddy
Brocade Communications
ets=22,
n_bytes=1680, priority=2,in_port=2
actions=output:1,output:3,CONTROLLER:65535
Regards,
Sai MarapaReddy
Brocade Communications
On Mon, Apr 25, 2016 at 11:06 AM, Luis Gomez wrote:
> OK, here is the resulting distribution:
>
>
> https://jenkins.opendaylight.org/releng/view/
Thanks Luis.
Filed bug -> https://bugs.opendaylight.org/show_bug.cgi?id=5822
Regards,
Sai MarapaReddy
On Thu, Apr 28, 2016 at 11:19 PM, Abhijit Kumbhare
wrote:
> Adding OpenFlow plugin.
>
> On Thu, Apr 28, 2016 at 8:25 PM, Luis Gomez wrote:
>
>> After further manual t
Hi Tali,
My knowledge says there are no packet encoders, and i don't see it in
roadmap (https://wiki.opendaylight.org/view/L2_Switch:Boron_Release_Plan).
Please feel free to contribute.
Regards,
Sai Reddy
Brocade Communications
On Sun, May 1, 2016 at 8:16 AM, Ben-Meir, Tali
wrote:
> Hi,
>
>
>
://meetings.opendaylight.org/opendaylight-l2switch/2016/l2switch_interest_call/opendaylight-l2switch-l2switch_interest_call.2016-05-04-20.06.txt
Feel free to watch/contribute to the meeting minutes at
#opendaylight-l2switch duing during the meeting time.
Please let me know if you have any questions.
Regards,
Sai
Hi Abhijit,
I moved bug 5822 to openflowplugin project. (
https://bugs.opendaylight.org/show_bug.cgi?id=5822 )
This may be a blocker for He to Li migration.
Regards,
Sai MarapaReddy
Brocade Communications
On Fri, Apr 29, 2016 at 4:48 PM, Sai MarapaReddy
wrote:
> Thanks Luis.
>
>
ovs & controller but not in the l2 switch code.
"Unable to contact the remote controller at :6633"
Regards,
Sai MarapaReddy
Brocade Communications
On Wed, May 4, 2016 at 3:15 AM, Rui Q wrote:
> Hello,
>
> Can someone give me a hand on this:
>
> *Problem:* L2switch no
-
http://pastebin.com/3vCkupYm
- Hence no successful mininet / ovs connection to controller
- I am not sure if these due to ongoing release
Please let us know if you are in the same boat or is it a different issue
altogether.
Regards,
Sai MarapaReddy
Brocade Communications
On Wed, May 4, 2016 a
Rui,
I used master branch initially ( when the ping worked ). I will try to
get stable/beryllium working by the eod.
Ajay L,
Thank you, it is the same. I will cherry pick by eod.
Regards,
Sai MarapaReddy
Brocade Communications.
On Thursday, May 5, 2016, Ajay L wrote:
> Hi Sai
>
> Ar
Hi Jamo/Rui,
The distribution works good. Issue is when we build the l2switch
stable/beryllium project.
Here is the fix for stable/beryllium ->
https://git.opendaylight.org/gerrit/#/c/38489/
since stable/beryllium is locked down, it cannot be pushed today.
Regards,
Sai MarapaReddy
Broc
ortly, so beryllium quality is top of mind for me.
>
> Thanks,
> JamO
>
> [0]
> https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-beryllium/1716/
>
> On 05/05/2016 05:41 PM, Sai MarapaReddy wrote:
> > Hi Jamo/Rui,
> >
>
and then pushing a patch to fix those
> issues. I want to know why these issues are not seen upstream in our
> stable/beryllium tests? that worries me.
>
> JamO
>
> On 05/05/2016 11:27 PM, Sai MarapaReddy wrote:
> > Hi Jamo,
> >
> > I pushed a patch and got jenk
89/2/distribution/karaf/pom.xml )
we let the karaf version flow from parent.
In distribution the karaf version is not hard coded, that is the reason why
it works when ran through distribution but not through l2switch project.
Please let me know if you need further clarification.
Regards,
Sai MarapaR
Hi An,
Seems mail is intended for BGP team. ( wrong mailing list) ?
Regards,
Sai MarapaReddy
On Mon, May 9, 2016 at 11:26 AM, An Ho wrote:
> Hi BGPCEP Team,
>
> There are some distribution test failures in Beryllium SR2 related to your
> project. Could you or someone from your
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
___
L2switch-dev mailing list
L2switc
ree to watch/contribute to the meeting minutes at
#opendaylight-l2switch duing during the meeting time.
Please let me know if you have any questions.
Regards,
Sai MarapaReddy
Software Engineer
Brocade Communications
___
L2switch-dev mailing list
L2swit
which is same.
Here are the output from mininet console where ping worked succesfully for
the second time (since reactive mode will be learning hosts during first
time ping won't succeed for the first time.)
http://pastebin.com/YHm2raXD
Please let me know if you any questions further.
Regard
you any questions further.
Regards,
Sai MarapaReddy
Brocade Communications
On Tue, May 17, 2016 at 11:03 PM, Selvakumar Murugasekaran <
selvakumar.murugaseka...@veryxtech.com> wrote:
> Hello Luis Gomez,
>
> Good day to you.
>
> Thank you for your information.
>
>
e delivered
successfully?
- Yes
6. Will your project have top-level features not requiring system test?
- No
7. Will your project use the OpenDaylight CI infrastructure for testing
top-level features requiring system test?
- Yes
Regards,
Sai MarapaReddy
On Fri, May 20, 2016 at 5:24 PM, A
Dorani,
The link still holds true, which indicates specifying default values in
yang doesn't work.
However abstract module classes created by
org.opendaylight.controller.config.yangjmxgenerator.plugin.JMXGenerator
from the config yang files do use the default value specified.
On Sun, May 22, 201
stallation or only
> with mininet?
> >
> > I'm asking because when i tried it with mininet (same version of OVS) it
> worked well but when using a dedicated OVS machine it just doesn't work.
> >
> > 2016-05-06 20:06 GMT+01:00 Sai MarapaReddy <mailto:sai.
Hi Thanh,
I see red builds here
https://jenkins.opendaylight.org/releng/job/l2switch-clm-beryllium/
If i download and build locally everything seems ok, Could you please shed
more light on why the tests were failing ?
Regards,
Sai MarapaReddy
Brocade Communications
t clm job? I don't see red there.
>
> JamO
>
> On 05/31/2016 10:24 AM, Sai MarapaReddy wrote:
> > Hi Thanh,
> >
> > I see red builds here
> https://jenkins.opendaylight.org/releng/job/l2switch-clm-beryllium/
> >
> > If i download and build locally
gt;
>> Phil (now CC'd) is our go to guy for CLM jobs. I notice that the
>> "Report" [0] is not coming up either. I think something basic
>> might be broken with these jobs.
>>
>> JamO
>>
>> [0]
>> https://jenkins.opendaylight.org/releng/jo
these.
Regards,
Sai MarapaReddy
On Thu, Jun 23, 2016 at 6:23 AM, CLAPP, GEORGE H (GEORGE H) <
cl...@research.att.com> wrote:
> I have exactly the same problem as Nithin and would greatly appreciate
> learning a solution.
>
>
>
> Thanks,
>
> George
>
Thanks An.
I will evaluate and let you know if any concerns.
On Mon, Jul 11, 2016 at 1:02 PM, An Ho wrote:
> Hi L2SWITCH Committers,
>
>
>
> There are plans to upgrade ietf-inet-types@2010-09-24 and
> ietf-yang-types@2010-09-24 (RFC 6021) to ietf-inet-types-2013-07-15 and
> ietf-yang-types@2013
An,
It is done. Thanks.
On Tue, Jul 12, 2016 at 3:28 PM, An Ho wrote:
> Hi Sai MarapaReddy,
>
>
>
> Thank you for evaluating. If you have no further concerns, please vote +2
> at this link:
>
>
>
> https://git.opendaylight.org/gerrit/#/c/41052/
>
>
>
Thank you An. Done.
On Mon, Aug 1, 2016 at 10:21 AM, An Ho wrote:
> Hi L2SWITCH Team,
>
> There are some distribution test failures in Beryllium SR3 Build 20160730
> related to your project. Could you or someone from your team please take a
> moment to mark these issues in the spreadsheet [1] a
ind it.
>
> Thanks,
> JamO
>
> On 08/01/2016 03:06 PM, Sai MarapaReddy wrote:
> > Thank you An. Done.
> >
> > On Mon, Aug 1, 2016 at 10:21 AM, An Ho an...@huawei.com>> wrote:
> >
> > Hi L2SWITCH Team,
> >
> > There are some dis
79 matches
Mail list logo
