LXD is no longer part of the Linux Containers project
103 views
Skip to first unread message
Stéphane Graber
Jul 4, 2023, 9:41:59 PM7/4/23
to LXC users mailing-list, LXC development mailing-list
Original: https://linuxcontainers.org/lxd/
Hello,
Canonical, the creator and main contributor of the LXD project has
decided that after over 8 years as part of the Linux Containers
community, the project would now be better served directly under
Canonical’s own set of projects.
While the team behind Linux Containers regrets that decision and will
be missing LXD as one of its projects, it does respect Canonical’s
decision and is now in the process of moving the project over.
Concretely, the expected changes are:
- https://github.com/lxc/lxd will now become https://github.com/canonical/lxd
- https://linuxcontainers.org/lxd will disappear and be replaced with
a mention directing users to https://ubuntu.com/lxd
- The LXD YouTube channel will be handed over to the Canonical team
- The LXD section on the LinuxContainers community forum will slowly
be sunset in favor of the Ubuntu Discourse forum run by Canonical
- The LXD CI infrastructure will be moved under Canonical’s care
- Image building for Linux Containers will no longer be relying on
systems provided by Canonical, limiting image building to x86_64 and
aarch64.
What will not be changing:
- The rest of the Linux Containers projects remain unaffected
- The image server, currently used by both LXC and LXD will keep
operating as normal, though with less architectures available as
mentioned above
Those changes will likely all happen pretty rapidly as everything is
relatively tightly integrated together. As a result, you may notice a
bit of bumpiness while Canonical sets up the replacement
infrastructure.
Sincerely,
The Linux Containers team
Christian Brauner
Serge Hallyn
Stéphane Graber
Hello,
Canonical, the creator and main contributor of the LXD project has
decided that after over 8 years as part of the Linux Containers
community, the project would now be better served directly under
Canonical’s own set of projects.
While the team behind Linux Containers regrets that decision and will
be missing LXD as one of its projects, it does respect Canonical’s
decision and is now in the process of moving the project over.
Concretely, the expected changes are:
- https://github.com/lxc/lxd will now become https://github.com/canonical/lxd
- https://linuxcontainers.org/lxd will disappear and be replaced with
a mention directing users to https://ubuntu.com/lxd
- The LXD YouTube channel will be handed over to the Canonical team
- The LXD section on the LinuxContainers community forum will slowly
be sunset in favor of the Ubuntu Discourse forum run by Canonical
- The LXD CI infrastructure will be moved under Canonical’s care
- Image building for Linux Containers will no longer be relying on
systems provided by Canonical, limiting image building to x86_64 and
aarch64.
What will not be changing:
- The rest of the Linux Containers projects remain unaffected
- The image server, currently used by both LXC and LXD will keep
operating as normal, though with less architectures available as
mentioned above
Those changes will likely all happen pretty rapidly as everything is
relatively tightly integrated together. As a result, you may notice a
bit of bumpiness while Canonical sets up the replacement
infrastructure.
Sincerely,
The Linux Containers team
Christian Brauner
Serge Hallyn
Stéphane Graber
Stéphane Graber
Jul 11, 2023, 9:00:27 PM7/11/23
to Linus Lüssing, LXC users mailing-list, LXC development mailing-list
On Wed, Jul 5, 2023 at 1:02 AM Linus Lüssing <linus.l...@c0d3.blue> wrote:
>
> Hi,
>
> Thanks for forwarding the news. Not ment judgingly but to better understand
> how things like this can happen. Can I also read this as follows?
>
> 1) Many/most of the LXD contributors/developers
> (by code contributed) personally would have liked the LXD project
> to stay more independent, under the non-profit linuxcontainers.org
> umbrella, as it used to be so far.
Yes
> 2) Canonical('s management?) wants more control over LXD? (or what is Canonical's
> motivation?) Which contradicts 1).
Yes, Canonical upper management wanted more control.
> 3) However the Linux Containers team can't decline
> because otherwise they'd risk their own ties with / job at Canonical?
> (Or what would be at risk if things were just kept as is?
> Trademark enforcement from Canonical, which would then require a rename of LXD?
> And/or Canonical cutting its funding for development on it?
> (which would seem contradictory to 2) then though) )
Canonical owns the trademark on LXD so refusing the request could
indeed have been a bit tricky.
> Sorry, if a casual, very uninformed bystander like me is completely
> misreading this. But this announcement at least had me raise an
> eyebrow and gave me a bit of mild OpenOffice/Oracle tingles.
>
> Regards, Linus
>
> PS: I love using LXD and really appreciate all the work and effort
> you guys have put into it. And was glad that I could contribute a
> little once by debugging and narrowing down one small issue with
> LXD + systemd-networkd in the past. But maybe that's also why this
> news made me a little bit concerned.
> > --
> > You received this message because you are subscribed to the Google Groups "lxc-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
> > To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CA%2Benf%3DuCcTkSb0PcbV%3D-sW7F06exS0rUeQjuzF%2BU7anG1ye7-g%40mail.gmail.com.
>
> Hi,
>
> Thanks for forwarding the news. Not ment judgingly but to better understand
> how things like this can happen. Can I also read this as follows?
>
> 1) Many/most of the LXD contributors/developers
> (by code contributed) personally would have liked the LXD project
> to stay more independent, under the non-profit linuxcontainers.org
> umbrella, as it used to be so far.
Yes
> 2) Canonical('s management?) wants more control over LXD? (or what is Canonical's
> motivation?) Which contradicts 1).
Yes, Canonical upper management wanted more control.
> 3) However the Linux Containers team can't decline
> because otherwise they'd risk their own ties with / job at Canonical?
> (Or what would be at risk if things were just kept as is?
> Trademark enforcement from Canonical, which would then require a rename of LXD?
> And/or Canonical cutting its funding for development on it?
> (which would seem contradictory to 2) then though) )
Canonical owns the trademark on LXD so refusing the request could
indeed have been a bit tricky.
> Sorry, if a casual, very uninformed bystander like me is completely
> misreading this. But this announcement at least had me raise an
> eyebrow and gave me a bit of mild OpenOffice/Oracle tingles.
>
> Regards, Linus
>
> PS: I love using LXD and really appreciate all the work and effort
> you guys have put into it. And was glad that I could contribute a
> little once by debugging and narrowing down one small issue with
> LXD + systemd-networkd in the past. But maybe that's also why this
> news made me a little bit concerned.
> > You received this message because you are subscribed to the Google Groups "lxc-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
> > To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CA%2Benf%3DuCcTkSb0PcbV%3D-sW7F06exS0rUeQjuzF%2BU7anG1ye7-g%40mail.gmail.com.
Stéphane Graber
Jul 11, 2023, 9:14:42 PM7/11/23
to Tamas Papp, LXC users mailing-list, LXC development mailing-list
On Wed, Jul 5, 2023 at 5:22 AM Tamas Papp <tamas...@rtfm.co.hu> wrote:
>
> hi Stephane,
>
> It is unclear to me, what will change for the users practically.
>
> You mentioned two things:
> - The project will be hosted by Canonical (changes of URLs).
> - Fewer architectures of LXD images will be available.
>
> Who is going to remain the developers (contributors) of the project? Concretely, are you going to keep working on it? Is the development going to remain open?
The Canonical LXD team will keep working on it. These days it's a set
of around 10 people with more positions opened to be filled.
As you may have seen since, I have left Canonical:
https://stgraber.org/2023/07/10/time-to-move-on/
I may still contribute to LXD here and there, but I'm no longer the
project leader.
LXD will keep on as an Open Source project (Apache-2), there's no
planned change on that front at all.
How open the development community will be, that may or may not
change, it's up to Canonical from now on.
> What advantages does Canonical expect from this change?
Control
> If the information can be published, what particular problem triggered the change?
My resignation from the company
> How does this change influence the future of the roadmap and plans?
It shouldn't affect it. Everything I presented as planned for the next
6 months remains on the company roadmap.
I had relatively little LXD work assigned directly to me so my
departure shouldn't cause items to be skipped.
> Thanks in advance,
> tamas
>
> hi Stephane,
>
> It is unclear to me, what will change for the users practically.
>
> You mentioned two things:
> - The project will be hosted by Canonical (changes of URLs).
> - Fewer architectures of LXD images will be available.
>
> Who is going to remain the developers (contributors) of the project? Concretely, are you going to keep working on it? Is the development going to remain open?
The Canonical LXD team will keep working on it. These days it's a set
of around 10 people with more positions opened to be filled.
As you may have seen since, I have left Canonical:
https://stgraber.org/2023/07/10/time-to-move-on/
I may still contribute to LXD here and there, but I'm no longer the
project leader.
LXD will keep on as an Open Source project (Apache-2), there's no
planned change on that front at all.
How open the development community will be, that may or may not
change, it's up to Canonical from now on.
> What advantages does Canonical expect from this change?
Control
> If the information can be published, what particular problem triggered the change?
My resignation from the company
> How does this change influence the future of the roadmap and plans?
It shouldn't affect it. Everything I presented as planned for the next
6 months remains on the company roadmap.
I had relatively little LXD work assigned directly to me so my
departure shouldn't cause items to be skipped.
> Thanks in advance,
> tamas
>> --
>> You received this message because you are subscribed to the Google Groups "lxc-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
>> To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CA%2Benf%3DuCcTkSb0PcbV%3D-sW7F06exS0rUeQjuzF%2BU7anG1ye7-g%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "lxc-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
> To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CAJgZx%3D%2BAxogU7jm8pkm-YLq6dk%2BLHa2W2fLxgZxGHBf%3DpsDqPQ%40mail.gmail.com.
>> You received this message because you are subscribed to the Google Groups "lxc-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
>> To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/CA%2Benf%3DuCcTkSb0PcbV%3D-sW7F06exS0rUeQjuzF%2BU7anG1ye7-g%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "lxc-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
Reply all
Reply to author
Forward
0 new messages