Hi, On Tue, 15 Sep 2015 18:23:54 +0900 (JST) FUJITA Tomonori <[email protected]> wrote:
> I would recommend you to use OVS plugin with the native interface > (Ryu) instead of ofagent: > > https://github.com/openstack/neutron/commit/3524e113165411c553be5cfe593d2462094a03e6 > > On Sun, 13 Sep 2015 19:38:46 -0700 (PDT) > "Ailing Zhang" <[email protected]> wrote: > > > 1. As I understand, there is one ofagent running on each compute > > node. Let「s say in a multi-nodes openstack environment, there > > should be separate ryu controller running on each compute node. ?Is > > the ryu controller on compute-node1 aware of switches on other > > compute nodes? > > No. The ryu controller on compute-node1 takes care of only OVS on > compute-node1. That's the key for scalability. > > The upper layer controller (say, Neutron) has the whole view (but > doesn't need to know the details of OVS like flows). > > > 2. Is there an API we can query to get the flow table of ryu > > controller inside ofagent? > > I suspect that there isn't but CC'ed to the expert. > ------------------------------------------------------ Currently there is no api to get the flow table. Please use some kind of commands such as 'ovs-vsctl'. ------------------------ > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel I also recommend you to use ovs ml2 driver rather than ofagent from now on. In Liberty the ovs driver gained openflow interface using ryu. And Liberty will be released soon. Thanks -- fumihiko kakuma <[email protected]> ------------------------------------------------------------------------------ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
