Thanks for sharing this link.

On Sun, Mar 25, 2018 at 9:49 PM, Iwase Yusuke <iwase.yusu...@gmail.com>
wrote:

> Hi Taha,
>
> Hmmm... I haven't tried yet though, the following parameters seems to be
> configured. But sorry I don't know those parameters meanings further...
> https://github.com/osrg/ryu/blob/master/ryu/topology/switches.py#L509-L513
>
> Thanks,
> Iwase
>
> On 2018年03月26日 10:45, Taha Khan wrote:
>
>> Well, What I observed is - Number of Nodes: 13, Number of Edges:21.
>> Is there a way this could be increased in terms of number of edges and
>> nodes?
>>
>>
>> Thanks!
>> Taha
>>
>>
>> On Sun, Mar 25, 2018 at 7:33 PM, Iwase Yusuke <iwase.yusu...@gmail.com
>> <mailto:iwase.yusu...@gmail.com>> wrote:
>>
>>     Hi Taha,
>>
>>     > But do you have any rough idea, how many links should a topology
>> have to not
>>     > hit performance limit?
>>
>>     Sorry, I don't have any idea...
>>
>>     Thanks,
>>     Iwase
>>
>>
>>     On 2018年03月24日 11:07, Taha Khan wrote:
>>
>>         Thanks for the reply.
>>         But do you have any rough idea, how many links should a topology
>> have to
>>         not hit performance limit?
>>         This is my systems specs.
>>         I need EventLinkAdd and EventLinkDelete to work properly as I am
>>         planning to introduce multiple link failures from mininet.
>>
>>         I started with 62 nodes, 107 links and trimmed my topology to 30
>> Nodes
>>         and 43 Links(86 bi-directional) and found, I was able to discover
>> the
>>         full topology but EventLinkDelete wasn't triggering when I tried
>>         with mininet (link down command).
>>         Now I have 30 Nodes, 32 Links and still EventLinkDelte is not
>> getting
>>         triggered though I see the full topology information in my
>> structures
>>         storing their information in RYU controller.
>>
>>
>>
>>
>>
>>
>>
>>
>>         Thanks!
>>         Taha
>>
>>
>>         On Fri, Mar 23, 2018 at 3:45 AM, Iwase Yusuke <
>> iwase.yusu...@gmail.com
>>         <mailto:iwase.yusu...@gmail.com> <mailto:iwase.yusu...@gmail.com
>>
>>         <mailto:iwase.yusu...@gmail.com>>> wrote:
>>
>>              Hi Taha,
>>
>>              IIRC, the similar problems had reported before on this
>> mailing list.
>>              I think you hit the performance limit of "single" controller
>> in
>>         order to use
>>              topology discovery feature against such many switches.
>>
>>              For handling such large topology, how about splitting your
>> topology
>>         into some
>>              sub-topology and having multiple controllers?
>>
>>              Thanks,
>>              Iwase
>>
>>
>>
>>              On 2018年03月23日 16:07, Taha Khan wrote:
>>
>>                  Hi
>>
>>                  I am using RYU-4.23 and Mininet OVS.
>>                  I have a 62 Node topology. When I run my RYU application
>> I
>>         noticed that
>>                  RYU is not able to discover all the datapaths and links
>>         everytime I run
>>                  my code. And also when I run (link down command ) in
>> mininet CLI,
>>                  EventLinkDelete is not getting triggered everytime I did
>> it.
>>         Few times I
>>                  was actually able to discover the full topology and
>>         EventLinkDelete was
>>                  also getting triggered.
>>                  Can you please suggest why is this so. I have attached
>> codes below.
>>
>>
>>                  Thanks!
>>                  Taha
>>
>>
>>                         ------------------------------
>> ------------------------------------------------
>>                  Check out the vibrant tech community on one of the
>> world's most
>>                  engaging tech sites, Slashdot.org!
>> http://sdm.link/slashdot
>>
>>
>>
>>                  _______________________________________________
>>                  Ryu-devel mailing list
>>         Ryu-devel@lists.sourceforge.net <mailto:Ryu-devel@lists.source
>> forge.net>
>>         <mailto:Ryu-devel@lists.sourceforge.net
>>         <mailto:Ryu-devel@lists.sourceforge.net>>
>>         https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>         <https://lists.sourceforge.net/lists/listinfo/ryu-devel>
>>                  <https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>         <https://lists.sourceforge.net/lists/listinfo/ryu-devel>>
>>
>>
>>
>>
>>         ------------------------------------------------------------
>> ------------------
>>         Check out the vibrant tech community on one of the world's most
>>         engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>>         _______________________________________________
>>         Ryu-devel mailing list
>>         Ryu-devel@lists.sourceforge.net <mailto:Ryu-devel@lists.source
>> forge.net>
>>         https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>         <https://lists.sourceforge.net/lists/listinfo/ryu-devel>
>>
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>
>>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to