On Tue, Jul 31, 2018 at 10:10 AM Free Ekanayaka <fr...@debian.org> wrote: > > Hey, > > I would think that Stéphane will want to backport these changes to the > 3.0.x series, as they improve performance considereably. It wouldn't be > a big change for the LXD code itself, since this is mostly "backend" > code.
Yes, we will be backporting the switch to the new dqlite implementation in the 3.0.x branch, should be in 3.0.2. > I'll Stéphane say the last workd tho. > > Thanks for the initiative, looking forward to see LXD in Debian! > > Free > > Clément Hermann <nod...@nodens.org> writes: > > > Hi, > > > > On 31/07/2018 17:28, Free Ekanayaka wrote: > >> Hello Clement, > >> > >> dqlite upstream and LXD team member here. > >> > >> Please note that dqlite is going through a bit of change, which I > >> started to merge yesterday. So a few of the ITPs you have filed will no > >> longer make sense. > > > > Thanks a lot for the heads up! > > > >> In a nutshell: > >> > >> 1) https://github.com/CanonicalLtd/dqlite is now a C project > >> 2) https://github.com/CanonicalLtd/go-dqlite has Go bindings > >> 3) golang-github-canonicalltd-go-sqlite3 won't be necessary anymore > >> 4) golang-github-canonicalltd-go-grpc-sql won't be necessary anymore > >> > >> This will all be effective starting with LXD 3.4, to be released in 3 > >> weeks. > >> > >> In LXD master, this will be effective once we land: > >> > >> https://github.com/lxc/lxd/pull/4854 > >> > >> which should happen today or tomorrow at latest. > > > > Good to know! I guess this won't change anything for 3.0.x series ? > > That's what we're aiming for, since we want to package the LTS version: > > the users needing cutting-edge version should use the snap IMO. > > > > Cheers,
