I think that this was a golden choice. There’ll likely be much less worry if existing features get to live alongside future plans (experimental) for a release or two before the plug is pulled (if it ever will be).
Gets both worlds of folks happy to upgrade & not lose anything and experiment & bug test, and you guys can toss any UI Experimental or End of Life warnings as you see relevant to set community expectations of what the future will hold & levels of support to be expected.
I suppose that iX will want to pull the plug at some point, to cut on the cost of maintaining two different interfaces to the same functionality, but when Instances are regarded as stable it might be possible to propose automatic migration.
Where we think we can we normally try to do.
In this case, it would have been a good plan, but we did not know ahead of time that both could run simultaneously
Docker and K8S don’t really run simultaneously.
There are user simplicity challeneges sometimes…
LXC is different functionality
VMs are duplicate with subtle differences.
If it was my product I would not put containers (LXC) and VMs (KVM) under the same umbrella (Instances).
I’d keep VMs with traditional KVM because people are used to and expect that and it’s what about every other product (Proxmox and friends) does.
Additionally provide LXC based containers with Incus under - whatever - “Containers”?
Kind regards,
Patrick
From what I see in Proxmox interface they also put VMs and Containers next to each other and only difference is small icon.
So Proxmox does it similarly to this new Instances method.
That, and they’re broken out separately in the list:
The LXCs are listed first (in numerical order), then the VMs. But, as you say, not a great distinction between them.
Both “traditional” and “instance” VMs use KVM. The former then goes through libvirt and the latter through Incus, as do system containers which run on LXC. And I think it is still possible to run system containers on systemd-nspawn, as was (is?) leveraged through jailmaker.
It is libvirt that could go to the chopping block if the plan succeeds, not KVM.
