Re: [ovs-dev] [PATCH v2 03/17] ovsdb: Track jsonrpc options per remote.

2024-01-12 Thread Dumitru Ceara
On 1/12/24 14:48, Ilya Maximets wrote: > On 1/12/24 12:22, Dumitru Ceara wrote: >> On 1/9/24 23:49, Ilya Maximets wrote: >>> Store JSON-RPC options for each remote separately, so it will be >>> possible to have different configurations per remote in the future. >>> >>> These are also stored to and

Re: [ovs-dev] [PATCH v2 03/17] ovsdb: Track jsonrpc options per remote.

2024-01-12 Thread Ilya Maximets
On 1/12/24 12:22, Dumitru Ceara wrote: > On 1/9/24 23:49, Ilya Maximets wrote: >> Store JSON-RPC options for each remote separately, so it will be >> possible to have different configurations per remote in the future. >> >> These are also stored to and loaded from the temporary file that >> OVSDB i

Re: [ovs-dev] [PATCH v2 03/17] ovsdb: Track jsonrpc options per remote.

2024-01-12 Thread Dumitru Ceara
On 1/9/24 23:49, Ilya Maximets wrote: > Store JSON-RPC options for each remote separately, so it will be > possible to have different configurations per remote in the future. > > These are also stored to and loaded from the temporary file that > OVSDB is using to restore runtime configuration of t

[ovs-dev] [PATCH v2 03/17] ovsdb: Track jsonrpc options per remote.

2024-01-09 Thread Ilya Maximets
Store JSON-RPC options for each remote separately, so it will be possible to have different configurations per remote in the future. These are also stored to and loaded from the temporary file that OVSDB is using to restore runtime configuration of the server restarted by the monitor process after