A new page describes the ipxe and xnba netboot methods: the files of the
upstream loader, UEFI Secure Boot through the shim and its limits, the
client test, the loader of nodes without a definition, the move of
nodes to the ipxe method and back, and the known limits of the upstream
loader.
The node guide, the noderes, node, group and nodeset pages list the ipxe
method, and the value lists mark xnba deprecated. The examples that
define an x86 node use netboot=ipxe. The mixed cluster and uninstall
guides name ipxe-xcat, and the DHCP validation matrix gets the iPXE
loader rows, Secure Boot included.
A ppc64el or riscv64 management node installs the amd64 Genesis. xCAT and
xCATsn declare Architecture: amd64 ppc64el riscv64 and one unrestricted
Depends: xcat-genesis-scripts-amd64, so every architecture gets it. That
package is Architecture: all, so apt reports no error. It lays down
/opt/xcat/share/xcat/netboot/genesis/x86_64 and pulls the 128 MB
xcat-genesis-base-amd64, and the node receives no Genesis for its own
architecture. xcat-genesis-scripts-ppc64, the package that would carry it, is
uninstallable: it depends on xcat-genesis-base-ppc64, and builddeb-genesis-base
names the ppc64el base deb xcat-genesis-base-ppc64el.
xCAT/debian/control and xCATsn/debian/control now restrict the dependency by
architecture, the way xCAT.spec does with
%{?genesistarch:Requires: xCAT-genesis-scripts-%{genesistarch}}. amd64 gets
xcat-genesis-scripts-amd64, ppc64el gets xcat-genesis-scripts-ppc64el, and
riscv64 gets neither, because its Genesis is the OpenEmbedded image.
xCAT-genesis-scripts/debian/control-ppc64el builds xcat-genesis-scripts-ppc64el
and depends on xcat-genesis-base-ppc64el. It conflicts with and replaces the
old name, which shares the same files.
debian_control_arch_coverage.t asserts the genesis scripts an architecture
receives are that architecture's own, and that control-<arch> builds
xcat-genesis-scripts-<arch> against xcat-genesis-base-<arch>. Eight of its
assertions fail without this change.
Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
Add the riscv64 page to the cluster management guide (UEFI + grub2 boot
path, discovery through mknb's grub2 network configurations, stateful and
stateless provisioning, the dependency picture for a management node on
riscv64, limitations), list riscv64 in the node object attributes and in
the support matrices, add the architecture to the cross-build page for
stateless images, extend the grub2 install guide (and fix its swapped
x86_64/aarch64 file names), the uninstall package lists, the DHCP backend
validation matrix and the mknb/genimage man pages, and carry the riscv64
schema values into the generated nodetype, osimage, noderes, node and
group references.
* [go-xcat] Revise debug log, in order to make debugging go-xcat and bug reporting easier.
* [go-xcat] Revise the prompt messages
* [go-xcat] In yum/zypper repo file, use gpgcheck=1
* [go-xcat] Bump version number
* [go-xcat] Revise the help messages
* [go-xcat] xCAT uninstallation
* [go-xcat] Fix kill command error messages
* [go-xcat] Simplify command line argument processing
* [go-xcat] When do a `check', only run update_repo
* Update document of xCAT uninstallation - use `go-xcat uninstall`
* [go-xcat] Handle goconserver in trash_xcat()
* [go-xcat] Add goconserver to the uninstallation package list
* Add goconserver to the uninstallation package list
* [go-xcat] Fix debug_logger
* [go-xcat] xCAT can be completely uninstalled
* Use lowercase file name xcat-core.repo instead of xCAT-core.repo
* Rename xCAT-core.repo to xCAT-core.repo.nouse if it exists
* Change xCAT-dep.repo mentioned in document to xcat-dep.repo
Vinícius Ferrão
Daniel Hilst
Markus Hilger
Mark Gurevich
Gᴏɴɢ Jie
Victor Hu
junxiawang
immarvin
Patrick Lundgren
ertaozh