On Wed, Aug 26, 2020 at 1:40 AM Yi Li <[email protected]> wrote: > > Signed-off-by: Yi Li <[email protected]> > --- > AUTHORS.rst | 1 + > northd/ovn-northd.c | 2 +- > ovn-architecture.7.xml | 8 ++++---- > ovn-nb.xml | 2 +- > 4 files changed, 7 insertions(+), 6 deletions(-) > > diff --git a/AUTHORS.rst b/AUTHORS.rst > index 2a642be2..a0ca9bb2 100644 > --- a/AUTHORS.rst > +++ b/AUTHORS.rst > @@ -389,6 +389,7 @@ Xiao Liang [email protected] > xu rong [email protected] > YAMAMOTO Takashi [email protected] > Yasuhito Takamiya [email protected] > +Yi Li [email protected] > Yi-Hung Wei [email protected] > Yifeng Sun [email protected] > Yin Lin [email protected] > diff --git a/northd/ovn-northd.c b/northd/ovn-northd.c > index 23312540..f2e3104b 100644 > --- a/northd/ovn-northd.c > +++ b/northd/ovn-northd.c > @@ -11275,7 +11275,7 @@ sync_meters(struct northd_context *ctx) > struct dns_info { > struct hmap_node hmap_node; > const struct nbrec_dns *nb_dns; /* DNS record in the Northbound db. */ > - const struct sbrec_dns *sb_dns; /* DNS record in the Soutbound db. */ > + const struct sbrec_dns *sb_dns; /* DNS record in the Southbound db. */ > > /* Datapaths to which the DNS entry is associated with it. */ > const struct sbrec_datapath_binding **sbs; > diff --git a/ovn-architecture.7.xml b/ovn-architecture.7.xml > index b1a46293..b81844f8 100644 > --- a/ovn-architecture.7.xml > +++ b/ovn-architecture.7.xml > @@ -815,7 +815,7 @@ > <p> > The <code>redirect-type</code> option requires the administrator or the > CMS to configure each participating chassis with a unique Ethernet address > - for the locgical router by setting <code>ovn-chassis-mac-mappings</code> in > + for the logical router by setting <code>ovn-chassis-mac-mappings</code> in > the Open vSwitch database, for use by <code>ovn-controller</code>. This > makes it more difficult to configure than > <code>reside-on-redirect-chassis</code>. > @@ -1816,7 +1816,7 @@ > owned IP addresses (i.e., IP addresses configured on the router ports, > VIPs, NAT IPs) in a specific way and only forwards them to the logical > router that owns the target IP address. This behavior is different than > - that of traditional swithces and implies that other routers/hosts > + that of traditional switches and implies that other routers/hosts > connected to the logical switch will not learn the MAC/IP binding from > the request packet. > </p> > @@ -2462,7 +2462,7 @@ > > <h1>Security</h1> > > - <h2>Role-Based Access Controls for the Soutbound DB</h2> > + <h2>Role-Based Access Controls for the Southbound DB</h2> > <p> > In order to provide additional security against the possibility of an OVN > chassis becoming compromised in such a way as to allow rogue software to > @@ -2521,7 +2521,7 @@ > RBAC configuration for the OVN southbound database is maintained by > ovn-northd. With RBAC enabled, modifications are only permitted for the > <code>Chassis</code>, <code>Encap</code>, <code>Port_Binding</code>, and > - <code>MAC_Binding</code> tables, and are resstricted as follows: > + <code>MAC_Binding</code> tables, and are restricted as follows: > </p> > <dl> > <dt><code>Chassis</code></dt> > diff --git a/ovn-nb.xml b/ovn-nb.xml > index 9f3621dc..1f2dbb9a 100644 > --- a/ovn-nb.xml > +++ b/ovn-nb.xml > @@ -2243,7 +2243,7 @@ > <p> > This feature requires the administrator or the CMS to configure > each participating chassis with a unique Ethernet address for the > - locgical router by setting <code>ovn-chassis-mac-mappings</code> in > + logical router by setting <code>ovn-chassis-mac-mappings</code> in > the Open vSwitch database, for use by <code>ovn-controller</code>. > </p> > > -- > 2.25.3 > > > > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Thanks for the fix. I applied it to master. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
