On Mon, Apr 10, 2017 at 2:06 PM, Lance Richardson <lrich...@redhat.com> wrote: > > > ----- Original Message ----- >> From: "Lance Richardson" <lrich...@redhat.com> >> To: "Terry Wilson" <twil...@redhat.com> >> Cc: "ovs dev" <d...@openvswitch.org>, "Lucas Alvares Gomes" >> <lucasago...@gmail.com> >> Sent: Monday, 10 April, 2017 2:01:39 PM >> Subject: Re: [ovs-dev] [PATCH v2] python: Allow tuning the session >> probe_interval from IDL >> >> > From: "Terry Wilson" <twil...@redhat.com> >> > To: "Lucas Alvares Gomes" <lucasago...@gmail.com> >> > Cc: "ovs dev" <d...@openvswitch.org> >> > Sent: Monday, 10 April, 2017 1:01:31 PM >> > Subject: Re: [ovs-dev] [PATCH v2] python: Allow tuning the session >> > probe_interval from IDL >> > >> > ovsdb-server has the ability to create additional servers based on a >> > DB contents. For the Open_vSwitch schema, that's the Manager table and >> > the Open_vSwitch table's manager_options column. >> > >> > The ovsdb-server code refers to these as "remotes". If these remotes >> > have a max_backoff/inactivity_probe column, those values will be set. >> > inactivity_probe is the column that will determine the probe_interval >> > for the RPC server that is launched. >> > >> > According to documentation (and the implementation in the "olden >> > days"), these remotes are set from the DB by passing >> > >> > --remote=db:DATABASE_NAME,TABLE_NAME,COLUMN >> > >> > to ovsdb-server. For the Open_vSwitch case, that's >> > >> > --remote=db:Open_vSwitch,Open_vSwitch,manager_options. >> > >> > In real life, this actually takes place by ovs-ctl calling >> > >> > # ovs-appctl -t ovsdb-server ovsdb-server/add-remote \ >> > db:Open_vSwitch,Open_vSwitch,manager_options >> > >> > after ovs-vswitchd has started. >> > >> > OVN, on the other hand, does not appear to have a Manager-like table >> > to set up remotes and configure them with inactivity_probes, etc. The >> > ovn-ctl script just hard codes the ptcp:$DB_NB_PORT:$DB_NB_ADDR remote >> > when launching ovsdb-server for north/southbound db access. >> > >> >> Hi Terry, >> >> Actually in OVS 2.7 we have "Connection" and "SSL" tables in ovn-sb and >> ovn-nb. >> >> See commits: >> >> 1047182 ovn-sb: remote connection management in sb db > > and, more relevant: > > 7fff4eb ovn-southbound: Implement read-only connection support. > >> 821302c ovn-nb: remote connection management in nb db >> >> Regards, >> >> Lance
but in any case, this only affects the ovsdb-server side probe interval. This patch is analogous to the ovn-controller configuration option you spotted (ovn-remote-probe-interval). We have to configure it separately for both ends of the connection. >> >> > If we want to be consistent with how OVS does things, we would need to >> > create something like the Manager table and make it possible for >> > ovn-ctl to call ovs-appctl to add the remotes and configure them. >> > >> > Related, I see ovn-controller has code to set the probe interval via >> > the local Open_vSwitch db's >> > Open_vSwitch.external_ids:ovn-remote-probe-interval. The patch that >> > added that also added ovsdb-idl.h's ovsdb_idl_set_probe_interval() >> > which is a similar solution the the one above for the Python code. >> > >> > I don't have enough "big picture" OVN knowledge yet to know whether >> > this (and the ovn-remote-probe-interval) patch is the way to go or >> > whether independently configuring the connections via the db like >> > Open_vSwitch db is the way. But since I'd had some run-ins with >> > probe_interval via Neutron code, I thought I'd at least put what I >> > knew out there. >> > >> > Terry >> > _______________________________________________ >> > dev mailing list >> > d...@openvswitch.org >> > https://mail.openvswitch.org/mailman/listinfo/ovs-dev >> > >> _______________________________________________ >> dev mailing list >> d...@openvswitch.org >> https://mail.openvswitch.org/mailman/listinfo/ovs-dev >> > _______________________________________________ > dev mailing list > d...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev -- Russell Bryant _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
