Ubuntu

Bug #1407714
Comment #9

Comment 9 for bug 1407714

Revision history for this message

bugproxy (bugproxy) wrote on 2015-01-26: Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-01-26 23:14 EDT-------
(In reply to comment #16)
> Err, the above comment makes no sense, FWIW. ISO build and debian-installer
> builds are not the same thing. In fact, the d-i on a new CD would still be
> the old one from days ago, even though the ISO would be new.
>
Then this is an issue, when testing daily build ISOs, if the netboot files are not in sync with the ISO.

> netbooting, by its very nature, pulls files directly from the archive, so
> the ISO is effectively worthless, and I'm not sure why you'd want to
> download something that's CD-sized when you only intend to use a few MB from
> it.
>
The use case is netbooting to installing from a local (http or ftp) repository created from the ISO, not netbooting to installing from the internet repository..

> Anyhow, the reason to keep the powerpc ISO slim is fairly obvious, it
> contains several kernel flavours (which add up fast), so we try not to bloat
> it out too much.
>
So.. this would add three new initrd files, at about 20 mb each? assuming the old ones could not be replaced? If that's too much bloat, Ok.
>
> The ppc64el ISO, however, having only one flavour, could probably have the
> netboot initrd added to it in the same fashion as we do for amd64. I'll
> look into that at some point.
>
Cool.

> Unless someone can give me a solid reason otherwise, however, I'm going to
> make this a wishlist priority, as the netboot kernel/initrd are published
> elsewhere (and those are exactly the same files that would be on the CD,
> feel free to validate that claim on amd64), so it's merely a convenience(?)
> to also let you download a whole CD to get them.
>
Not sure why the request is so unreasonable. The benefit seem obvious, when you consider the use case of netbooting for installation against a local repository, which is a very common installation method in the enterprise. The pitfalls of not having them in the same place, and in sync, equally obvious. The netboot files are on the amd64 ISO so I'm not sure why the ppc64 and ppc64el cases are so different. Other leading distros put the netboot files on their server ISO as well, and many network mgmt systems (e.g. xCAT) are used to finding them there. In fact, the Ubuntu ppc ISOs are the first place I've hit this issue.

------- Comment From hellerda@us.ibm.com 2015-01-26 23:14 EDT-------
(In reply to comment #16)
> Err, the above comment makes no sense, FWIW.  ISO build and debian-installer
> builds are not the same thing.  In fact, the d-i on a new CD would still be
> the old one from days ago, even though the ISO would be new.
>
Then this is an issue, when testing daily build ISOs, if the netboot files are not in sync with the ISO.

> Anyhow, the reason to keep the powerpc ISO slim is fairly obvious, it
> contains several kernel flavours (which add up fast), so we try not to bloat
> it out too much.
>
So.. this would add three new initrd files, at about 20 mb each?  assuming the old ones could not be replaced?  If that's too much bloat, Ok.
>
> The ppc64el ISO, however, having only one flavour, could probably have the
> netboot initrd added to it in the same fashion as we do for amd64.  I'll
> look into that at some point.
>
Cool.

> Unless someone can give me a solid reason otherwise, however, I'm going to
> make this a wishlist priority, as the netboot kernel/initrd are published
> elsewhere (and those are exactly the same files that would be on the CD,
> feel free to validate that claim on amd64), so it's merely a convenience(?)
> to also let you download a whole CD to get them.
>
Not sure why the request is so unreasonable.  The benefit seem obvious, when you consider the use case of netbooting for installation against a local repository, which is a very common installation method in the enterprise.  The pitfalls of not having them in the same place, and in sync, equally obvious.  The netboot files are on the amd64 ISO so I'm not sure why the ppc64 and ppc64el cases are so different.  Other leading distros put the netboot files on their server ISO as well, and many network mgmt systems (e.g. xCAT) are used to finding them there.  In fact, the Ubuntu ppc ISOs are the first place I've hit this issue.