Hi Karthik,
There is a Ryu talk on Youtube that mentions the use of Zookeeper for
HA/redundancy purposes.
I haven't tried it as I'm at the start of my Ryu journey, but maybe it
helps you as an advanced user.
http://youtu.be/gGJRTo78Osg
Benny
Am Samstag, 10. Mai 2014 schrieb Karthik Sharma :
> Hi,
>
> I would like to deploy RYU in a scalable and fault tolerant architecture.
>
> What I want to do is as follows.
>
> 1) There are two instances of RYU (RYU1 and RYU2) running on two separate
> machines (SYS1 and SYS2 ) but are connected so as to form a logically
> unified CONTROL plane.
>
> 2) The mininet and my topology runs on SYS1,but the switches in my
> topology initiate connection to both RYU1 and RYU2.
>
> 3) I should be able to assign one of the controllers (RYU1 or RYU2) as the
> master controller.(The master controller assignment will be on a per-switch
> basis)
>
> 4) To demonstrate scalability I do the following.
>
> - Assume there are 6
> switches in the topology (s1 - s6)
> - A rough sketch of the
> topology is given below
>
> h1 ---- s1 ----- s4
> ----- h4
>
> h2 ---- s2 ----- s5
> ----- h5
>
> h3 ---- s3 ----- s6
> ----- h6
>
> - I let switches 1,2,3
> be controlled by RYU1
> switches 4,5,6
> be controlled by RYU2
>
> I should be able to communicate between the switches as expected.
>
> i.e h1 should be
> able to ping h4
> h2 should be
> able to ping h5
> h3 should be
> able to ping h6
>
>
> 5) To demonstrate fault tolerance with the above topology I start will all
> the switches having RYU2 as the master.
> Then I shut RYU2 down and I should be able to switch all the switches to
> RYU1.
>
> Something like below.(where the ip of the RYU1 is 192.168.241.129"
>
>
>
> sudo ovs-vsctl set-controller s1 "tcp:192.168.241.129:6633"
>
> sudo ovs-vsctl set-controller s2 "tcp:192.168.241.129:6633"
>
> sudo ovs-vsctl set-controller s3 "tcp:192.168.241.129:6633"
>
> sudo ovs-vsctl set-controller s4 "tcp:192.168.241.129:6633"
>
> sudo ovs-vsctl set-controller s5 "tcp:192.168.241.129:6633"
>
> sudo ovs-vsctl set-controller s6 "tcp:192.168.241.129:6633"
>
>
> Have anyone thought of this or something similar.Do you have any comments
> or suggestions regarding the same?
>
> Thanks & Regards,
> Karthik.
>
>
>
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel
