If lxd is always adding a reasonable value, we can just remove it from our
configuration. We only need it when Juju interacts with LXD. We added it to
Juju a long time ago because LXD was by-default-installed on all machines,
and they didn't want to tweak the value unless people were actually using
LXD.
If their policy has finally changed, then I'm more than happy to remove our
override.
John
=:->
On Thu, Feb 28, 2019 at 9:25 AM Richard Harding <email address hidden>
wrote:
> Thanks, the fact that the client is installed makes sense now. I
> appreciate the analysis that helped me look and note that lxd added that
> sysctl file in Apr 2017 and we had added this to the snap setup in Feb
> 2017. I think it's just that we originally needed that config and set
> some default and lxd later set a larger default that we missed was added
> and would negate the need for Juju to set this when using the client.
>
> https://github.com/lxc/lxd-pkg-
> ubuntu/commits/8dc4a41e780000c323e119ba14f4463b4c222c8e/debian/lxd.sysctl
>
>
> https://github.com/juju/juju/commit/609dbb29a77e01f54d602be8ca373a9a171f8653
> #diff-8f4e953fdcce135fef1df9e88717ab5d
> <https://github.com/juju/juju/commit/609dbb29a77e01f54d602be8ca373a9a171f8653#diff-8f4e953fdcce135fef1df9e88717ab5d>
>
> We'll look at updating the snap definition and see if we can
> test/validate that we no longer need the lxd tweaks and update it.
>
> For the immediate aid for your case I'd suggest testing removing the
> file 'usr/lib/sysctl.d/juju-2.conf' and kicking the system.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1817774
>
> Title:
> Juju has to allow tuning lxd-related kernel parameters
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1817774/+subscriptions
>
If lxd is always adding a reasonable value, we can just remove it from our installed on all machines,
configuration. We only need it when Juju interacts with LXD. We added it to
Juju a long time ago because LXD was by-default-
and they didn't want to tweak the value unless people were actually using
LXD.
If their policy has finally changed, then I'm more than happy to remove our
override.
John
=:->
On Thu, Feb 28, 2019 at 9:25 AM Richard Harding <email address hidden>
wrote:
> Thanks, the fact that the client is installed makes sense now. I /github. com/lxc/ lxd-pkg- commits/ 8dc4a41e780000c 323e119ba14f446 3b4c222c8e/ debian/ lxd.sysctl /github. com/juju/ juju/commit/ 609dbb29a77e01f 54d602be8ca373a 9a171f8653 cce135fef1df9e8 8717ab5d /github. com/juju/ juju/commit/ 609dbb29a77e01f 54d602be8ca373a 9a171f8653# diff-8f4e953fdc ce135fef1df9e88 717ab5d> sysctl. d/juju- 2.conf' and kicking the system. /bugs.launchpad .net/bugs/ 1817774 /bugs.launchpad .net/juju/ +bug/1817774/ +subscriptions
> appreciate the analysis that helped me look and note that lxd added that
> sysctl file in Apr 2017 and we had added this to the snap setup in Feb
> 2017. I think it's just that we originally needed that config and set
> some default and lxd later set a larger default that we missed was added
> and would negate the need for Juju to set this when using the client.
>
> https:/
> ubuntu/
>
>
> https:/
> #diff-8f4e953fd
> <https:/
>
> We'll look at updating the snap definition and see if we can
> test/validate that we no longer need the lxd tweaks and update it.
>
> For the immediate aid for your case I'd suggest testing removing the
> file 'usr/lib/
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Juju has to allow tuning lxd-related kernel parameters
>
> To manage notifications about this bug go to:
> https:/
>