On Thu, Jul 7, 2016 at 3:15 PM, Andy Zhou <az...@ovn.org> wrote: > Another consideration is that we'd be able to make use of ovsdb features, >> but at the expense of not be able to use etcd features directly. An >> example is authorization. This is a v2 API doc, but: >> >> https://coreos.com/etcd/docs/latest/auth_api.html >> >> I was thinking we might be able to build a solution for the "Limiting the >> impact of a compromised chassis" item in ovn/TODO using etcd capabilities. >> If we put ovsdb in front of it, we still have to solve this in ovsdb. >> >> This is a very good point. May be it is another +1 for #2? Or you have > some other approach in mind? >
Yes, +1 for #2. -- Russell Bryant
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
