[ovs-dev] [PATCH 00/10] Expose vlog and vconn in public headers

[Thomas Graf]

On 12/10/14 at 02:05pm, YAMAMOTO Takashi wrote:
> > On 12/10/14 at 01:29pm, YAMAMOTO Takashi wrote:
> >> can you explain your motivation briefly?
> > 
> > The motivation is to end up with a set of header files that have
> > clean namespaces so they can be installed on the system and be
> > used in combination with the shared libraries.
> 
> is there a particular user of the libraries in your mind?

Yes. The API is primarily targeted at architectures like CoreOS,
Docker, kubernetes, Neutron agent, ... which already have an agent
running on the host and would like to control the OVS instance
running on that particular host. So this is serving as an API to
OVS for them.

I do not expect this to replace existing controller development
frameworks such as RYU.