> Above are equivalent configs. As far as I understand one of them is newer
> than the other, and one of them is prefered than the other, both are
> supported for legacy reasons.
They are equivalent. Storage config is newer than the grub namespace in
curtin config. Curtin will prefer storage config grub_device flags over
install_devices lists. Both are supported for legacy and because Curtin
does not require that a storage config be provided for installing.
Curtin includes a block-meta simple mode which will find a disk,
install the provided rootfs and make it bootable. In the case that MAAS
or the user desires to use a specific disk that is not the same device
that Curtin may automatically pick to be the boot disk the install_devices
value under the grub: namespace is used.
> As far as I understand, for newly written yaml only one of these
> should be prefered.
It depends on the deployment blockmeta mode and the needs of the
scenario.
> Can you please explain the difference between the two ways to
> specify bootloader devices via grub.install_devices list
> and storage.config.grub_device flag?
Using grub_device: True on devices in custom storage config is
the easiest and most reliable method. In particular, curtin
will lookup the correct device path.
When using grub.install_devices, the user has to guess the
device path and may reference a disk that is not the intended
target (or be quite familiar with how to express a stable linux
block device path).
> Why doesn't documention only use one of them?
Documentation species both as they apply to different scenarios.
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862848
Title:
curtin yaml has two ways to specify grub device, which one is the
right one?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1862848/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
