Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Thanks all. Marking as "Won't Fix" and marked MP as Rejected.
** Changed in: ubuntu-meta (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.
I was already leaning that way and thank you for adding the data.
I agree to not to
Based on the data, I'm in the "No" camp as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
Always preseed core and snapd snap in server seed
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.
That is my position. Thanks for bringing data to this!
--
You received this bug
With only snapd snap preseeded I get boot times very similar to
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.757s (kernel) + 12.458s (userspace) = 16.216s
graphical.target reached after 12.061s in userspace.
```
Which shows we are still taking a boot time hit of ~1.5 seconds...
> * boot times w/ and w/o preseeded snaps
Without preseeded snaps:
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.609s (kernel) + 11.026s (userspace) = 14.636s
graphical.target reached after 10.642s in userspace.
```
With preseeded snapd and core22 snaps:
```
ubuntu@cloudimg:~$
@vorlon
> Also, statically seeding a particular base snap is bad form, as soon
as lxd upgrades its base you lose your performance benefit and have to
play catch-up in a stable release.
yes I don't like this either. Even if we do change it later to core24
then the expectations people have for
It was nice to have LXD around and ready for many test/dev workloads,
and I feel it was worth it back then.
But we already replaced it with lxd-installer in minimal environments and it
was fine there too.
I never heard someone complaining that LXD takes a bit there, but every second
of boot time
Thank you for the detail sdeziel
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
Always preseed core and snapd snap in server seed
Status in
> "other cloud cases that have preseeded snaps" (thinking like ec2 or
oracle that have snapped cloud agent
This isn't something we need to worry about as there will be no change
in this case. If any agent snaps are preseeded then so too will a core
snap and snapd snap.
--
You received this bug
FYI, snapd is a "base-less" snap:
$ lxc launch ubuntu-minimal-daily:22.04 c1
$ lxc shell c1
root@c1:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
root@c1:~# snap install snapd
2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart...
snapd 2.61.1 from Canonical✓
I agree with vorlon in general. It is a bit odd to not be seeding snapd
by default, since snaps are a recognized package format. preseeding
snapd will bring in its base, but there's no guarantee that base will
match any other snaps.
Flip side is that somewhere back in history, it was decided that
> 15 seconds vs 30 seconds, on a thing that won't affect most cloud
customers
I'll see if I can find the data to back this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
If we don't preseed a core snap and snapd it feels like we're failing to
prioritise the performance of snaps on server/cloud.
But if we acknowledge that knowing that we are prioritising boot speed
then that's fine and we can add it to the noble release notes.
--
You received this bug
Good points
I'll measure boot speed with and without core snap preseeded and add it
here.
time to initialize any snap was my goal but with lxd as an example as it
is such a popular snap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
> This is a significant difference and for a workload we intend to remain as a
> core tested
> and tracked workload. As such I propose we re-introduce core22 and snapd
> snaps to our seed.
I disagree that the image should be optimized by default to prioritize
the one-time startup performance of
** Description changed:
In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
core22 snap.
This means that are subsequent snap
** Merge proposal linked:
https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459599
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
19 matches
Mail list logo
