On Thu, May 06, 2021 at 12:34:00AM +0200, Ilya Maximets wrote: > On 5/5/21 11:40 PM, Ben Pfaff wrote: > > I think that this series has the details that one needs to understand it > > at a high level, but I didn't see a high-level overview of its intended > > use. I think the idea is that, for a use case like OVN, one would > > deploy a clustered OVS database, and then the second tier would be a > > collection of replicas on top of that cluster. If that's the case, I > > think that adding a paragraph to an appropriate high-level documentation > > file for OVSDB explaining it would be helpful, and possibly a (ASCII > > art?) diagram. > > > > Yes. That is the intended use case. And I agree that current series > has only bare minimum of documentation. I'll include the patch that > adds a new paragraph to Documentation/topics/ovsdb-replication.rst to > describe how to scale out read access (existing functionality that is > documented with a single sentence in ovsdb(7) "A set of replicas that do > serve clients could be used to scale out read access to the primary > database.") and how to use the same schema for an OVN deployment with > transaction forwarding enabled (new features). This could be done in > v2 or as a separate patch. > > I have a following ASCII art for the deployment schema: > [...]
OK, great! OVS and OVN are usually good at documenting details, but not the high level. It's a syndrome of starting out as a project that implemented a standard (OpenFlow): we didn't document the high level because we assumed everyone was already familiar with OpenFlow and what it was good for at a high level. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
