For deploying Debian/bookworm (see MT#55524), we'd like to have an
updated Grml ISO. With such a Debian/bookworm based live system, we can
still deploy older target systems (like Debian/bullseye).
Relevant changes:
1) Ad jo as new build-dependency, to generate build information in
conf/buildinfo.json (new dependency of grml-live)
2) Always include ca-certificates, as this is required with more recent
mmdebstrap versions (>=0.8.0), when using apt repositories with
https, otherwise bootstrapping Debian fails.
3) Update to latest stable grml-live version v0.42.0, which:
a) added support for "bookworm" as suite name
cff66073a7
b) provides corresponding templates for memtest support:
c01a86b3fc
c) and a workaround for a kmod/initramfs-tools issue with PXE/NFS boot:
ea1e5ea330
4) Update memtest86+ to v6.00-1 as present in Debian/bookworm and
add corresponding UEFI support (based on grml-live's upstream change,
though as we don't support i386, dropped the 32bit related bits)
Change-Id: I327c0e25c28f46e097212ef4329d75fc8d34767c
When running in EFI mode, it's as simple as executing "fwsetup".
This is taken over from upstream change
8c0c9d9228
Change-Id: I0fffee2aa814597ade9772bd93ab6d69b1ea4f9c
This pretty much never works for me, while exiting GRUB switches to the
next device in the boot order, so let's just "exit" GRUB and name the
menu entries accordingly.
This is taken over from upstream change
89c43982fb
Change-Id: I23106b202bfc57f3173cb1ee0326c5b7eddd0474
* Addon fixes:
* Provide custom addon template according to our needs, instead of
relying on the default one being present in grml-live.git/templates
* Install memtest86+ as addon for BIOS usage
* Install netboot.xyz.lkrn for BIOS usage and netboot.xyz.efi for EFI usage
* Install ipxe.lkrn for BIOS usage and ipxe.efi for EFI usage
* Stick grml-live version to v0.34.3, instead of relying on some random
git master version
* Stick grml2usb version to v0.17.0, instead of relying on the grml2usb
version available on the host system (being 0.14.14 on Debian/stretch as
present on our current build hosts). For arbitrary addon file names we
need grml2iso (which uses grml2usb underneath) from grml2usb >=0.17.0.
FTR, grml2iso and grml2usb can be executed from within the git repository,
assuming all relevant tools are present
* No longer invoke isohybrid on the resulting ISO, instead rely on
grml2iso behaviour (which also checks for EFI support and enables
according switches as needed)
* Fix usage instructions in t/Dockerfile:
* it's "deployment-iso-buster" and not "lua-ngcp-kamailio-buster"
* refer to working directory instead of "deployment-iso.git",
which very probably isn't named as such on any of our systems,
while the $(pwd) approach works for c/p
* Fix docker build usage in grml_build/Dockerfile (for building we need
to provide a PATH (being current working directory for us)
* Provide testing tools in grml-build-buster docker environment
* Provide new testing script t/iso-tester to compare generated ISO
against pre-defined screenshot (only testing memtest feature using
./t/screenshots/01-memtest.jpg for now)
Change-Id: I67e3f85bbe86bd1b3ee709161504b5250ca5d7fe
Use a single (prev CE like) approach
GRML -> main.sh -> deployment.sh -> ngcp-installer
All SP versions can be installed from a single image
Remove network configuration points from GRML installer
Change-Id: I9a56c12ca3f42d055303e5a0b08691de3560fe2c
This is Sipwise NGCP install CD. NGCP install options must be on top
(right after 'Rescue system boot').
Change-Id: Ie33e06e17f86bcb5633bed7c59bcd9a266201645
It is often outdated, see MT#19427 and confuses support,
as you never really know which version you will get.
We have a special sections with list of releases below.
Lets force users to choose what to install.
Change-Id: I2770521d92da4410c066fcf9ed23fef8b62db1b0
1) Starting with Grml 2017.05 we need net.ifnames=0 as default
boot option, otherwise we end up with network device names like
enp0s3 instead of eth0
2) Now that we're getting closer to the Debian/stretch release let's
add support for it through the boot menues
3) Noticed that the GRUB menu order is wrong for the Debian installation
options, make it consistent what we have in isolinux/syslinux.
Change-Id: Ia32c16707b158c8afb3a7babf7b51fe96ab05753
We shouldn't install wheezy systems with "Install sip:providerCE"
amd "Install sip:providerPRO" entries.
Change-Id: Ia78787c2bb997be55c86d7206c1c2723d4f36b63
DHCP somehow affects PRO installation by getting IP on eth1
which affects glusterfs. We should not use DHCP if user
explicitly choose static network configuration.
Change-Id: I6db8118916c2ca6bb1cec212f908b14dafc1e7fe
Using 2+ DNS servers is a good practice, also
ngcp-status reports error if he notice 1 DNS server only.
GRML support 2+ DNS servers in dns boot option, lets use it.
Change-Id: I236f7e5d854fef59f72323cf471fe4d949731c38
System boot freezes during udev startup on some systems (e.g. on
Supermicro boards and recent IBM server models). Workaround
required for Grml 2014.11: use boot option mgag200.modeset=0.
This should be made a default boot option in our ISOs.
Change-Id: I316d30f89fac6ced43256801f599e8b6366e9757
1) boot option 'ngcpnoupload' is depricated in trunk since f9192367
We have a Jenkins job for uploading and it uses option 'ngcpupload'.
2) Previously we used 'ngcpnoupload' to skip dumps upload to Git.
Uploading has been considered for CE-trunk only (skipped for other systems),
so there were no need to specify the option everywhere.
Anyway, 'ngcpnoupload' R.I.P
Change-Id: I13dd43be43be37152877cc3f183ec39863ea7e80
dns=92.42.136.30 doesn't work for the public so switch to
dns=8.8.8.8 instead, at least in the configs we use for
building the public Grml-Sipwise deployment ISO.
Some of them got lost in recent changes related to MT#6253 + MT#7365,
we want the trailing white space char because otherwise when typing
to add a new boot option it gets appended to the previous one (which
is unwanted and unexpected behaviour, as we had this behaviour ("space
char after last pre-configured boot option is present" since the
very first days).
So finally we can boot our deployment ISO in UEFI mode.
Documentation for the operation guys will follow in the ticket,
once everything is sorted out the according documentation can
be integrated in our documentation/handbook.
Closes: https://bugtracker.sipwise.com/view.php?id=1843
From: Michael Prokop <mprokop@sipwise.com>
Works on my machine™ now. Let's see whether we get this working
Hint: for testing efi boot inside kvm check out
http://dummdida.blogspot.co.at/2011/09/efi-kvm.html
From: Michael Prokop <mprokop@sipwise.com>
Jose Su
Michael Prokop
Mykola Malkov
Alexander Lutay
Victor Seva
Andrew Pogrebennyk
Andreas Granig