Comment 29 for bug 1872941

On Mon, 27 Apr 2020 at 09:05, bugproxy <email address hidden> wrote:
>
> ------- Comment From <email address hidden> 2020-04-27 03:47 EDT-------
> Independent from KVM and virt-install, reading again
> https://ubuntu-on-big-iron.blogspot.com/2020/03/glimpse-at-subiquity.html
> I think this is actually a big step backwards for LPAR.
> Do you really have no network configuration script in the installer itself and now you HAVE to specify this via the parmfile?
> Until now Ubuntu was the only distribution that could be installed via a public ftpserver via the HMC. If I read the doc right, I now NEED an FTP server myself.
> Looks like you just got rid of your big installation advantage over SLES and RHEL.
>

I hope dream and wish, for HMC to offer a selection of .iso, download
them, DD them onto the zfcp drive, and boot the HMC using el-torito
boot record from it, with the correct zfcp zdev-auto-activated. That
way, without doing a thing, the LPAR comes up, initrd automatically
activates the right drive and boots into the installer on the ascii
terminal, with installation happening at blazing fast speeds.
Potentially disconnected from the internet / ubuntu mirrors. Because
.iso is self-contained.

I have asked for HMC to allow storing / launching .iso or cloud-image
.img, but that's not supported at the moment.

Booting over the public internet FTP server, terrifies me. Because
there is no secureboot verification of either kernel or the initrd.
Meaning it's trivial to man-in-the-middle attack, and inject things
into the installer. Can HMC support HTTPS load?

--
Regards,

Dimitri.