Please run "snappy install ubuntu-core" as part of the build

[Michael Vogt]

One goal of 16.04 is to ship the snappy package by default so that you can "snappy install $stuff". For this to work the "ubuntu-core" snap must be installed. To make this a better user experience we should install it by default.

[Scott Moser (smoser)]

Michael,
  I'm confused by 'livecd-rootfs' as the target here.
If we want this installed, we should just seed it in 'server' and 'cloud-image' seed.

[Scott Moser (smoser)]

hm.. now i see. so in addition to having the 'snappy-ubuntu' package installed, you're wanting the cloud image and server installed image to have 'snappy install ubuntu-core' already run inside them.

Just for reference, from a cloud image today
apt-get install snappy-ubuntu: adds about 25M of usage to /

snappy install ubuntu-core: adds about 75M

a 'df -h /' on a fresh instance before versus after
/dev/vda1 20G 870M 19G 5% /
to
/dev/vda1 20G 976M 19G 5% /

[Scott Moser (smoser)]

I've removed myself as the asignee for the livecd-rootfs task.
We probably also need another task for the cloud image build process . not sure where that would go.

Then, I suggest that we do seed those packages.

[Robert C Jennings (rcj)]

I have added this to the 'cloud-images' project to get this added to our cloud image build process.

[Scott Moser (smoser)]

Robert, I've added the ubuntu-snappy package to the cloud-image and server seeds so new images should get the package.
Whether or not we actually then run the 'snappy install ubuntu-core' would need to be done by the imag builder still.

[Oliver Grawert (ogra)]

i think what you actually want to seed is ubuntu-snappy-cli, that has less dependencies ... though given you need to install the 70-80MB big ubuntu-core snap additionally a few extra MB do perhaps not matter ...

[Oliver Grawert (ogra)]

for the image build process you most likely want to add a script snippet under live-build/ubuntu-cpc/hooks/ in the livecd-rootfs package/tree ...

[Scott Moser (smoser)]

Oliver,
Thanks for the suggestion of ubuntu-snappy-cli. We are definitely interested.
That said:
  apt-get install ubuntu-snappy
and
  apt-get install ubuntu-snappy-cli
on a cloud image seem to differ only by the 'ubuntu-snappy' package (which has an installed size of 42k). Ie, it seems like ubuntu-snappy is nothing more than a convenient meta-package over ubuntu-snappy-cli.

I believe that everyone is in agreement that we do not want the ubuntu core snap already installed by default. Thus, I've marked the 2 tasks that would do that with 'wont fix' and added the task for the Ubuntu Seeds to indicate that the seed is still to be done.

Please feel free to comment and change the state of those if I'm misunderstanding something.

[Oliver Grawert (ogra)]

sounds sane ... but you likely want some first-boot setup to pull it in or some such

[Dustin Kirkland  (kirkland)]

+1, right, Scott. The desire is to have /usr/bin/snappy in the server/cloud images. We do not want to embed all of the snappy image in the server/cloud image, but rather snappy should download it when it's used the first time, if necessary.

[Scott Moser (smoser)]

OK. ubuntu-snappy is now in the seeds. I have no intention of changing that to 'ubuntu-snappy-cli'.
Any new cloud image or server iso with serial > 20160310 will have ubuntu-snappy and its dependencies installed.