I'd like to raise the following issues for discussion: 1. That the client side is abstracted from the specific choice of server-side database by using a db-abstraction layer on the client side. We already have some kind of an abstraction layer in the code: ovsdb-idl. Maybe we can start from there. 2. I think if clients receive all updates this will pose a scalability concern. I'd like to propose adding a pub/sub-like subsystem to be used for keeping clients up-to-date about updates in the DB. This can serve as a mechanism for table tracking and could also enable clients to receive updates only on a small subset of changes instead of all changes. This would greatly improve scalability in number of clients. 3. Do we really need an on-disk DB for the southbound DB? I think an in-memory DB for the Southbound is worth discussing.
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
