Remove pxelinux ipappend from pxelinux.cfg templates

[Robie Basak]

Following a discussion this morning, it would make things simpler if we don't use ipappend. The dynamic TFTP server can emulate it as required by supplying a bootif= kernel cmdline parameter directly. The exception is the pre-enlistment boot which for architecture detection needs to wait for the "default-<arch>-..." fallback, but at this stage we don't think bootif is required anyway. Am I wrong?

[Robie Basak (racb)]

Subscribing Scott for comments.

[Scott Moser (smoser)]

bootif is probably requird in the enlistment.
I'm fairly sure that stuff is actually correclty hooked up all the way through to get 'bootif=' value assigned to eth0. Or, if not, it could be. The reason that the images need to know the boot interface is that there is a entry for 'eth0' in /etc/network/interfaces of the images, and that *needs* to be the right interface, or cloud-init will at least potentially have race conditions reesulting in timeouts or failures.

If the guarantee of 'bootif' translating into 'eth0' is not present currently, we can make that happen, but if there are multiple interfaces and only one of them is going to have a route to the maas metadata server (used in enlistment) you need to somehow relay that information to the images.

[Dave Walker (davewalker)]

Can the reasons for dropping ipappend be included please?

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]