Hi All,

Apologize for late reply I was really busy :). I tried again with SNAPSHOOT
[0] and Boron SR3, same issue br-sfc going to slave and not connected. will
try to debug and give more logs

[0]
https://jenkins.opendaylight.org/releng/job/openflowplugin-distribution-check-carbon/lastSuccessfulBuild/artifact/distribution-karaf-0.6.0-SNAPSHOT.zip

[1]
https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/integration/distribution-karaf/0.5.3-Boron-SR3/distribution-karaf-0.5.3-Boron-SR3.tar.gz

BR

On Wed, Apr 5, 2017 at 9:15 AM, Kochba, Alon <[email protected]> wrote:

> Hey Mohamed,
>
>
>
> Any update on this?
>
> Tomas what's the status of the patch, just waiting for verification?
>
>
>
> --alon
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Mohamed ElSerngawy
> *Sent:* Tuesday, 28 March 2017 17:18
> *To:* Jamo Luhrsen <[email protected]>
> *Cc:* [email protected]; openflowplugin-dev@lists.
> opendaylight.org; Tomáš Slušný <[email protected]>
> *Subject:* Re: [sfc-dev] [openflowplugin-dev] br-sfc become slave and
> disconnect from ODL
>
>
>
> Hi Jamo,
>
>
>
> I saw the patch, will give it try today.
>
>
>
> Thanks
>
>
>
> On Tue, Mar 28, 2017 at 2:28 AM, Jamo Luhrsen <[email protected]> wrote:
>
> Mohamed,
>
> just in case you didn't see the update/request from Tomas on the bug, we
> are wondering if
> you could try your reproduction setup with the following unmerged patch:
>
> https://git.opendaylight.org/gerrit/#/c/50603
>
> The patch gives us a distribution that you can use:
> https://jenkins.opendaylight.org/releng/job/openflowplugin-
> distribution-check-carbon/1504/artifact/distribution-
> karaf-0.6.0-SNAPSHOT.zip
>
>
> Hopefully your reproduction steps are still manageable (time-wise) and
> consistent.
>
> Thanks,
> JamO
>
> On 03/10/2017 06:55 AM, Mohamed ElSerngawy wrote:
> > Hi Tomas,
> >
> > I'm using OVS 2.5.9 version, also tried with Boron SR2 and latest
> distribution [0] . In previous email, I attached a Vagrant
> > file to reproduce the environment may you can use it. I reproduces it
> yesterday without setting the manager.
> >
> >
> > Hi Anil,
> >
> > Thanks for the response, I believe the issue is not form the switch side
> cause simply if you stop/start ODL all the br-sfc
> > will be connected fine to ODL. Will try to send the logs later today.
> >
> > [0] https://nexus.opendaylight.org/content/repositories/
> opendaylight.snapshot/org/opendaylight/integration/
> distribution-karaf/0.6.0-SNAPSHOT/
> >
> > On Fri, Mar 10, 2017 at 9:26 AM, Tomáš Slušný <[email protected]
> <mailto:[email protected]>> wrote:
> >
> >     Hi Mohamed,
> >
> >     I tried reproducing your issue in a bit simplified environment. Here
> are steps that I did:
> >
> >     1. Build openflowplugin from last master [0]
> >     2. Start karaf and install odl-openflowplugin-flow-services-rest
> >     3. Run 4 docker containers running Open vSwitch 2.4.0 using this
> docker image: [1]
> >     4. Run these commands on each of docker images
> >       * ovs-vsctl add-br br-sfc
> >       * ovs-vsctl set-controller br-sfc tcp:10.0.2.15:6653 <
> http://10.0.2.15:6653>
> >       * ovs-vsctl list Controller | ag '_uuid|role|status|target'
> >       * ovs-vsctl show
> >
> >     Here is output from each docker container:
> >     1. [2]
> >     2. [3]
> >     3. [4]
> >     4. [5]
> >
> >     For me, everything is working and I failed to reproduce your problem.
> >     I do not ran "ovs-vsctl set-manager ...:6640" because we do not have
> anything running on port 6640 after installing
> >     openflowplugin
> >     karaf feature, so it is probably coming from somewhere else.
> >     Let me know if I forgot to test something, or if I tested it wrong
> please.
> >
> >     Regards,
> >     Tomas Slusny
> >
> >
> >     [0] https://github.com/opendaylight/openflowplugin/tree/
> f82db7a1c0b8cf795e3976beafd5852a293ae9fe
> >     <https://github.com/opendaylight/openflowplugin/tree/
> f82db7a1c0b8cf795e3976beafd5852a293ae9fe>
> >     [1] https://github.com/socketplane/docker-ovs <https://github.com/
> socketplane/docker-ovs>
> >     [2] https://hastebin.com/vaxenuzipu <https://hastebin.com/vaxenuzipu
> >
> >     [3] https://hastebin.com/ugimomozab <https://hastebin.com/ugimomozab
> >
> >     [4] https://hastebin.com/nogehuveba <https://hastebin.com/nogehuveba
> >
> >     [5] https://hastebin.com/egagujonaq <https://hastebin.com/egagujonaq
> >
> >
> >
> >     Od: Anil Vishnoi <[email protected] <mailto:
> [email protected]>>
> >     Odoslané: 10. marca 2017 2:11
> >     Komu: Mohamed ElSerngawy
> >     Kópia: [email protected] <mailto:sfc-dev@lists.
> opendaylight.org>; [email protected]
> >     <mailto:[email protected]>
> >     Predmet: Re: [openflowplugin-dev] br-sfc become slave and disconnect
> from ODL
> >
> >
> >
> >     Hi Mohamed,
> >
> >
> >     Looks like plugin is sending the role request to the switch (br-sfc)
> but switch is not accepting it and then plugin give
> >     up after 10 seconds or so. Can you capture the wireshark trace where
> your switch is running?  This will give us some
> >     insight on what request controller is sending and why switch is not
> responding properly. Also please fire ovsdb-client
> >     dump command on the machine where OVS is running and provide the
> output.
> >
> >
> >     If the switch won't accept the master role, plugin can't configure
> any flow/group/meter on that switch, so we need to see
> >     why switch is acting this way.
> >
> >
> >     On Thu, Mar 9, 2017 at 2:21 PM, Mohamed ElSerngawy  <
> [email protected] <mailto:[email protected]>> wrote:
> >
> >     Hi Jamo,
> >
> >
> >     I confirm it also happen with ODL Carbon distribution (the one u
> sent above) . I created a bug at [0] for it.
> >
> >
> >     [0] https://bugs.opendaylight.org/show_bug.cgi?id=7948 <
> https://bugs.opendaylight.org/show_bug.cgi?id=7948>
> >
> >
> >     Thanks
> >
> >
> >
> >
> >     On Thu, Mar 9, 2017 at 3:50 PM, Jamo Luhrsen  <[email protected]
> <mailto:[email protected]>> wrote:
> >      Mohamed,
> >
> >     would you have time for two things?
> >
> >     a) could you try your test with a recent Carbon distribution? here's
> one [0]
> >
> >     b) could you open a bug in openflowplugin?
> >
> >
> >     for a) if we can show that it's happening in Carbon, easily with
> your steps,
> >     and in addition to the fact that we saw it in our upstream CSIT
> which is doing
> >     pretty normal user facing tests, we can potentially push harder for
> a fix on b)
> >
> >     Thanks,
> >     JamO
> >
> >     [0]
> >     https://nexus.opendaylight.org/content/repositories/
> opendaylight.snapshot/org/opendaylight/integration/
> distribution-karaf/0.6.0-SNAPSHOT/distribution-karaf-0.
> 6.0-20170309.102115-4296.zip
> >     <https://nexus.opendaylight.org/content/repositories/
> opendaylight.snapshot/org/opendaylight/integration/
> distribution-karaf/0.6.0-SNAPSHOT/distribution-karaf-0.
> 6.0-20170309.102115-4296.zip>
> >
> >
> >     On 03/09/2017 09:37 AM, Abhijit Kumbhare wrote:
> >     > Thanks for your instructions on how to replicate the issue. We
> discussed this in the meeting today - however there are
> >     > several clustering related issues - so Jozef & Tomas will look at
> this the next week. In the meantime - if there is any
> >     other
> >     > volunteer who wants to help out on these OpenFlow clustering
> related issues - you are always welcome :)
> >     >
> >     >
> >     >
> >     > On Thu, Mar 9, 2017 at 9:15 AM, Mohamed ElSerngawy <
> [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>>
> wrote:
> >     >
> >     >     Hi Brady,
> >     >
> >     >     Thanks for your response, I agree it is OpenflowPlugin issue.
> In fact, I tried to reproduced it with only
> >     Openflowplugin
> >     >     feature installed but it didn't come up from the first time,
> but now I tried again with
> >     >     only odl-openflowplugin-flow-services-ui installed in ODL and
> it show up every time.
> >     >
> >     >     Hi Openflowplugin Team,
> >     >
> >     >     Can anyone advice on the issue we mentioned above, I can
> reproduce it every time I go through same procedures.
> >     >
> >     >     Thanks
> >     >
> >     >
> >     >
> >     >
> >     >     On Thu, Mar 9, 2017 at 8:19 AM, Brady Allen Johnson <
> [email protected]
> >     <mailto:[email protected]>
> >     >     <mailto:[email protected] <mailto:
> [email protected]>>> wrote:
> >     >
> >     >
> >     >         Mohamed,
> >     >
> >     >         Sorry to hear the demo isnt working well for you in Boron.
> I havent tried it in Boron lately, but have used it
> >     >         successfully recently in master (Carbon). Do you have to
> use Boron, or can you switch to Carbon?
> >     >
> >     >         I'll try running it from Boron now. I'll let you know how
> it goes for me in Boron. Either way, it looks like the
> >     >         problem is in the OpenflowPlugin, and Im not sure we'll be
> able to do much from SFC.
> >     >
> >     >         Regards,
> >     >
> >     >         Brady
> >     >
> >     >         -----Original Message-----
> >     >         *From*: Mohamed ElSerngawy <[email protected]
> <mailto:[email protected]>
> >     <maiyouhrsen%20%[email protected] <mailto:maiyouhrsen%2520%
> [email protected]>%3e>>,
> >     >         [email protected] <mailto:sfc-dev@lists.
> opendaylight.org> <mailto:[email protected]
> >     <mailto:[email protected]>> <
> [email protected] <mailto:[email protected]>
> >     >         <mailto:%[email protected]
> >     <mailto:[email protected]>%22%20%3csfc-
> [email protected]
> >     <mailto:22%2520%[email protected]>%3e>>
> >     >         *Cc*: Openflowplugin-dev <openflowplugin-dev@lists.
> opendaylight.org
> >     <mailto:[email protected]>
> >     >         <mailto:Openflowplugin-dev%20%3copenflowplugin-dev@lists.
> opendaylight.org
> >     <mailto:Openflowplugin-dev%2520%253copenflowplugin-dev@
> lists.opendaylight.org>%3e>>
> >     >         *Subject*: Re: [openflowplugin-dev] br-sfc become slave
> and disconnect from ODL
> >     >         *Date*: Wed, 8 Mar 2017 15:51:29 -0500
> >     >
> >     >         Hi, following up on this thread
> >     >
> >     >         In order to reproduce it, I attached with the email a
> vagrant file that will spawn 5 VMs: odl, classifier1/2
> >     and sff1/2.
> >     >         After spawn all the VMs:
> >     >
> >     >         1- In the odl VM start odl and install the following
> features:
> >     >         vagrant@odl:~/$ distribution-karaf-0.5.2-
> Boron-SR2/bin/karaf
> >     >         opendaylight-user@root>feature:install odl-sfc-ui
> odl-sfclisp odl-sfc-scf-openflow odl-sfc-sb-rest odl-sfc-ovs
> >     >         odl-sfc-netconf odl-sfcofl2*
> >     >         *
> >     >
> >     >         2- in the other VMs classifier1/2 and sff1/2 set the OVS
> instance manager and create br-sfc:
> >     >         vagrant@classifier1:~$ sudo ovs-vsctl set-manager tcp:
> 10.10.1.5:6640 <http://10.10.1.5:6640>
> >     <http://10.10.1.5:6640>
> >     >
> >     >         vagrant@classifier1:~$ sudo ovs-vsctl add-br br-sfc
> >     >
> >     >         vagrant@classifier1:~$ sudo ovs-vsctl set-controller
> br-sfc tcp:10.10.1.5:6653 <http://10.10.1.5:6653>
> >     <http://10.10.1.5:6653>
> >     >
> >     >         usually it show up after the third VM, check the ODL logs
> it should show the same error that i sent in the first
> >     >         email [1]
> >     >
> >     >         if we checked the ovs status the manager is connected but
> the br-sfc is not
> >     >         vagrant@classifier1:~$ sudo ovs-vsctl show
> >     >         0b5ce3d8-12f8-4298-98fa-0009450b9b2a
> >     >             Manager "tcp:10.10.1.5:6640 <http://10.10.1.5:6640> <
> http://10.10.1.5:6640>"
> >     >                 is_connected: true
> >     >             Bridge br-sfc
> >     >                 Port veth-br
> >     >                     Interface veth-br
> >     >                 Port br-sfc
> >     >                     Interface br-sfc
> >     >                         type: internal
> >     >             ovs_version: "2.5.90"
> >     >
> >     >
> >     >         Once I stop/start odl it works fine and all br-sfc are
> connected !!!. I tried to debug and look in deep but didn't
> >     >         really help. Any idea why this happening ?
> >     >
> >     >         Thanks
> >     >
> >     >
> >     >         [1]  2017-03-06 23:27:43,369 | WARN  | pool-38-thread-1 |
> DeviceContextImpl                | 312 -
> >     >         org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
> New role BECOMESLAVE was not propagated to device
> >     >         openflow:112250352583491 during 10 sec
> >     >
> >     >         2017-03-06 23:27:43,369 | ERROR | pool-38-thread-1 |
> SalRoleServiceImpl               | 312 -
> >     >         org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
> SetRoleService set Role BECOMESLAVE for Node:
> >     >         KeyedInstanceIdentifier{targetType=interface
> >     >         
> > org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node,
> path=[org.opendaylight.yang.ge
> >     <http://org.opendaylight.yang.ge>
> >     >         <http://org.opendaylight.yang.ge <
> http://org.opendaylight.yang.ge>>n.v1.urn.opendaylight.
> inventory.rev130819.Nodes,
> >     >         org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.
> rev130819.nodes.Node[key=NodeKey [_id=Uri
> >     >         [_value=openflow:112250352583491]]]]} fail . Reason
> java.util.concurrent.CancellationException: Task was cancelled.
> >     >
> >     >         2017-03-06 23:27:43,369 | WARN  | pool-38-thread-1 |
> DeviceManagerImpl                | 312 -
> >     >         org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
> Was not able to set role SLAVE to device on node
> >     >         openflow:112250352583491
> >     >
> >     >         2017-03-06 23:28:25,569 | INFO  | pool-38-thread-1 |
> StatisticsManagerImpl            | 312 -
> >     >         org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
> Statistics collection for node openflow:2913975747405
> >     still
> >     >         in progress even after 50 secs
> >     >
> >     >         2017-03-06 23:28:25,577 | WARN  | pool-38-thread-1 |
> StatisticsManagerImpl            | 312 -
> >     >         org.opendaylight.openflowplugin.impl - 0.3.2.Boron-SR2 |
> Statistics gathering for single node
> >     openflow:2913975747405
> >     >         was not successful: Task was cancelled.
> >     >
> >     >
> >     >         On Mon, Mar 6, 2017 at 7:01 PM, Jamo Luhrsen <
> [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>>> wrote:
> >     >>         ok, well if it's the same issue then it's something thats
> been around for a while. The job
> >     >>         I was debugging is a recent carbon.
> >     >>
> >     >>         JamO
> >     >>
> >     >>         On 03/06/2017 04:00 PM, Mohamed ElSerngawy wrote:
> >     >>         > I'm using boron sr2
> >     >>         >
> >     >>         > On Monday, March 6, 2017, Jamo Luhrsen <
> [email protected] <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:[email protected]>> <mailto:
> [email protected] <mailto:[email protected]>
>
> >     >>         <mailto:[email protected] <mailto:[email protected]>>>>
> wrote:
> >     >>         >
> >     >>         >     What distro are you using?
> >     >>         >
> >     >>         >     netvirt CSIT had a bad failure  I was trying to
> debug today that looks just like this.
> >     >>         >     email thread here [0]
> >     >>         >
> >     >>         >     I hadn't seen it before so thought it might not be
> reproducible very easily...
> >     >>         >
> >     >>         >     JamO
> >     >>         >
> >     >>         >     [0]  https://lists.opendaylight.
> org/pipermail/netvirt-dev/2017-March/003566.html
> >     <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html>
> >     >>         <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html
> >     <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html>>
> >     >>         >     <https://lists.opendaylight.
> org/pipermail/netvirt-dev/2017-March/003566.html
> >     <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html>
> >     >>         <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html
> >     <https://lists.opendaylight.org/pipermail/netvirt-dev/
> 2017-March/003566.html>>>
> >     >>         >
> >     >>         >
> >     >>         >     On 03/06/2017 03:35 PM, Mohamed ElSerngawy wrote:
> >     >>         >     > Hi Team,
> >     >>         >     >
> >     >>         >     > I'm having issue with openflow in the sfc103
> demo, the bridge br-sfc is not connected to ODL raising error
> >     >>         at [1]. Can
> >     >>         >     anyone
> >     >>         >     > advice, why is the bridge become slave and not
> connected to ODL ?
> >     >>         >     >
> >     >>         >     >
> >     >>         >     > [1]  2017-03-06 23:27:43,369 | WARN  |
> pool-38-thread-1 | DeviceContextImpl                | 312 -
> >     >>         >     > org.opendaylight.openflowplugin.impl -
> 0.3.2.Boron-SR2 | New role BECOMESLAVE was not propagated to device
> >     >>         >     > openflow:112250352583491 during 10 sec
> >     >>         >     >
> >     >>         >     > 2017-03-06 23:27:43,369 | ERROR |
> pool-38-thread-1 | SalRoleServiceImpl               | 312 -
> >     >>         >     > org.opendaylight.openflowplugin.impl -
> 0.3.2.Boron-SR2 | SetRoleService set Role BECOMESLAVE for Node:
> >     >>         >     > KeyedInstanceIdentifier{targetType=interface
> >     >>         org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.
> rev130819.nodes.Node,
> >     >>         >     > path=[org.opendaylight.yang.ge <
> http://org.opendaylight.yang.ge>
>
> >     >>         <http://org.opendaylight.yang.ge
> >     <http://org.opendaylight.yang.ge>>n.v1.urn.opendaylight.inventory.
> rev130819.Nodes,
> >     >>         >     > org.opendaylight.yang.gen.v1.
> urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri
> >     >>         >     > [_value=openflow:112250352583491]]]]} fail .
> Reason java.util.concurrent.CancellationException: Task was
> >     >>         cancelled.
> >     >>         >     >
> >     >>         >     > 2017-03-06 23:27:43,369 | WARN  |
> pool-38-thread-1 | DeviceManagerImpl                | 312 -
> >     >>         >     > org.opendaylight.openflowplugin.impl -
> 0.3.2.Boron-SR2 | Was not able to set role SLAVE to device on node
> >     >>         >     > openflow:112250352583491
> >     >>         >     >
> >     >>         >     > 2017-03-06 23:28:25,569 | INFO  |
> pool-38-thread-1 | StatisticsManagerImpl            | 312 -
> >     >>         >     > org.opendaylight.openflowplugin.impl -
> 0.3.2.Boron-SR2 | Statistics collection for node
> >     >>         openflow:2913975747405 still in
> >     >>         >     > progress even after 50 secs
> >     >>         >     >
> >     >>         >     > 2017-03-06 23:28:25,577 | WARN  |
> pool-38-thread-1 | StatisticsManagerImpl            | 312 -
> >     >>         >     > org.opendaylight.openflowplugin.impl -
> 0.3.2.Boron-SR2 | Statistics gathering for single node
> >     >>         openflow:2913975747405
> >     >>         >     was not
> >     >>         >     > successful: Task was cancelled.
> >     >>         >     >
> >     >>         >     > Thanks
> >     >>         >     >
> >     >>         >     >
> >     >>         >     >
> >     >>         >     > _______________________________________________
> >     >>         >     > openflowplugin-dev mailing list
> >     >>         >     >  [email protected]
> <mailto:[email protected]>
> >     <mailto:[email protected] <mailto:
> [email protected]>> <javascript:;>
> >     >>         >     >  https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >     >>         <https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >>
> >     >>         >     <https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >     >>         <https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >>>
> >     >>         >     >
> >     >>         >
> >     >>
> >     >
> >     >         _______________________________________________
> openflowplugin-dev mailing list
> >     >         [email protected] <mailto:
> [email protected]>
> >     <mailto:[email protected] <mailto:
> [email protected]>>
> >     >         https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >     >         <https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >>
> >     >
> >     >
> >     >
> >     >     _______________________________________________
> >     >     openflowplugin-dev mailing list
> >     >     [email protected] <mailto:
> [email protected]>
> >     <mailto:[email protected] <mailto:
> [email protected]>>
> >
> >
> >     >     https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >     >     <https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >>
> >     >
> >     >
> >     >
> >     >
> >     > _______________________________________________
> >     > openflowplugin-dev mailing list
> >     > [email protected] <mailto:
> [email protected]>
> >     >  https://lists.opendaylight.org/mailman/listinfo/
> openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >     >
> >
> >
> >     _______________________________________________
> >     openflowplugin-dev mailing list
> >     [email protected] <mailto:
> [email protected]>
> >     https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >     <https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev>
> >
> >
> >
> >
> >
> >      --
> >
> >
> >     Thanks
> >     Anil
>
> >
> >
> >
> >
> > _______________________________________________
> > openflowplugin-dev mailing list
> > [email protected]
> > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >
>
>
>
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to