While further researching OVN, I found following in on ovs-dev alias
(http://openvswitch.org/pipermail/dev/2015-January/050380.html)
====
* In corner cases, respond to packets arriving from virtual
interfaces (via OpenFlow). For example, ARP suppression may
require observing packets from VMs through OpenFlow "packet-in"
messages.
ovn-controller is not a centralized controller but what we refer to as
a "local controller", since an independent instance runs locally on
every hypervisor. ovn-controller is not a general purpose "SDN
controller"--it performs the specific tasks outlined above in support
of the virtual networking functionality of OVN.
======
Assuming nothing has changed drastically since then, I wanted to make sure
following is true. Please correct if my understanding is wrong.
OVN can't be used by CMS (Cloud Managements System) to send Packet_Out or
receive Pakcet_IN messages to and from OVS. CMS is simply interfacing with OVN
Northbound DB, which is just a simple database, not a messaging layer.
Thanks
Maurice
PS: Would still like to know the answer to my original question about OVN
Daemaons.
Thanks
Maurice
From: discuss [mailto:[email protected]] On Behalf Of Maurice
Qureshi
Sent: Tuesday, May 10, 2016 1:24 PM
To: [email protected]
Subject: [ovs-discuss] Starting OVN Daemons
I just installed OVS 2.5.0 from
http://openvswitch.org/releases/openvswitch-2.5.0.tar.gz. The reason I wanted
to use this release is because it has OVN support. Have already experimented
with OVN Sandbox and now want to move to real thing.
Followed the installation process in INSTALL.md. It brought up the OVS daemons,
but not the "OVN" daemons such as ovn-northd, ovn-controller, and
ovn-controller-vtep. What needs to be done to bring these up.
Thanks
Maurice
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
