switch from virt-builder to virt-install (T813)
Summary:
We've kinda been having too much trouble with virt-builder
lately, mainly SELinux related issues due to how it does image
customization. It also produces images that differ in notable
ways from what a 'typical' install would give. virt-install
solves both these problems, and also gives us more flexibility
for storage configuration and post-install customization should
we need them in future.
The change isn't really too drastic, and the design is similar:
instead of virt-builder commands files, each image type now has
a kickstart file where all its customizations can be done.
There's also a single extra image dict key, 'variant', which
specifies which install tree variant to use for running the
install. It defaults to 'Everything' (for F24+) and 'Server'
(for <F24, as Everything wasn't installable until F24) but we
set it to 'Server' for the server images and 'Workstation' for
the desktop images, so those installs will use the correct
variant install class.
We run the installs in VNC. You can do it with a serial console
and log the output, but then anaconda gets clever and changes
several things in the installed system based on the fact that
you did the install over a serial console: it twiddles with
the kernel args and doesn't set graphical.target as the default.
We don't want any of that mess, so we do a VNC install.
The 'size' value is just a number of gigabytes for virt-install
images (as that's how the virt-install 'size' argument works).
This also drops some unused 32-bit images (we don't do 32-bit
KDE or Server upgrade tests, so there's no need to build those
images).
Test Plan:
Re-generate all affected images and re-run all tests
that use them, make sure they work. I am doing this on staging
at present. Note: this would render D911 unnecessary.
Reviewers: garretraziel
Reviewed By: garretraziel
Subscribers: tflink
Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D917
2016-07-04 16:29:25 +00:00
|
|
|
install
|
|
|
|
|
bootloader --location=mbr
|
|
|
|
|
network --bootproto=dhcp
|
|
|
|
|
url --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
|
|
|
|
|
repo --name=updates --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch
|
2020-09-08 23:17:15 +00:00
|
|
|
# contains fix to get F33 backgrounds in KDE. Remove when
|
|
|
|
|
# https://bodhi.fedoraproject.org/updates/FEDORA-2020-527d393bd7 goes stable
|
2020-09-09 01:06:36 +00:00
|
|
|
repo --name=kdesettemp --baseurl=https://www.happyassassin.net/temp/kdeback33/$releasever/$basearch
|
switch from virt-builder to virt-install (T813)
Summary:
We've kinda been having too much trouble with virt-builder
lately, mainly SELinux related issues due to how it does image
customization. It also produces images that differ in notable
ways from what a 'typical' install would give. virt-install
solves both these problems, and also gives us more flexibility
for storage configuration and post-install customization should
we need them in future.
The change isn't really too drastic, and the design is similar:
instead of virt-builder commands files, each image type now has
a kickstart file where all its customizations can be done.
There's also a single extra image dict key, 'variant', which
specifies which install tree variant to use for running the
install. It defaults to 'Everything' (for F24+) and 'Server'
(for <F24, as Everything wasn't installable until F24) but we
set it to 'Server' for the server images and 'Workstation' for
the desktop images, so those installs will use the correct
variant install class.
We run the installs in VNC. You can do it with a serial console
and log the output, but then anaconda gets clever and changes
several things in the installed system based on the fact that
you did the install over a serial console: it twiddles with
the kernel args and doesn't set graphical.target as the default.
We don't want any of that mess, so we do a VNC install.
The 'size' value is just a number of gigabytes for virt-install
images (as that's how the virt-install 'size' argument works).
This also drops some unused 32-bit images (we don't do 32-bit
KDE or Server upgrade tests, so there's no need to build those
images).
Test Plan:
Re-generate all affected images and re-run all tests
that use them, make sure they work. I am doing this on staging
at present. Note: this would render D911 unnecessary.
Reviewers: garretraziel
Reviewed By: garretraziel
Subscribers: tflink
Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D917
2016-07-04 16:29:25 +00:00
|
|
|
lang en_US.UTF-8
|
|
|
|
|
keyboard us
|
|
|
|
|
timezone --utc America/New_York
|
|
|
|
|
clearpart --all
|
|
|
|
|
autopart
|
|
|
|
|
rootpw --plaintext weakpassword
|
|
|
|
|
user --name=test --password=weakpassword --plaintext
|
|
|
|
|
poweroff
|
|
|
|
|
|
|
|
|
|
%packages
|
|
|
|
|
@^kde-desktop-environment
|
2019-12-10 22:12:11 +00:00
|
|
|
# these are all in the KDE live image, we want to match that as it's
|
|
|
|
|
# the most common KDE deployment method
|
|
|
|
|
@firefox
|
|
|
|
|
@kde-apps
|
|
|
|
|
@kde-media
|
|
|
|
|
@kde-office
|
|
|
|
|
@networkmanager-submodules
|
|
|
|
|
fedora-release-kde
|
|
|
|
|
falkon
|
|
|
|
|
|
2020-05-25 19:56:33 +00:00
|
|
|
# FIXME: fedora-jam-kde-theme-2.0.0-1.fc31 provides kde-settings,
|
|
|
|
|
# and anaconda prefers it to the real kde-settings for some reason,
|
|
|
|
|
# so F31 images are getting fedora-jam-kde-theme instead of
|
|
|
|
|
# kde-settings and this means they have the wrong background and
|
|
|
|
|
# some other issues. This should be fixed by 3.0.0-1.fc31, so we
|
|
|
|
|
# can probably remove this when
|
|
|
|
|
# https://bodhi.fedoraproject.org/updates/FEDORA-2020-3753ee3716
|
|
|
|
|
# is pushed stable
|
|
|
|
|
-fedora-jam-kde-theme
|
|
|
|
|
|
switch from virt-builder to virt-install (T813)
Summary:
We've kinda been having too much trouble with virt-builder
lately, mainly SELinux related issues due to how it does image
customization. It also produces images that differ in notable
ways from what a 'typical' install would give. virt-install
solves both these problems, and also gives us more flexibility
for storage configuration and post-install customization should
we need them in future.
The change isn't really too drastic, and the design is similar:
instead of virt-builder commands files, each image type now has
a kickstart file where all its customizations can be done.
There's also a single extra image dict key, 'variant', which
specifies which install tree variant to use for running the
install. It defaults to 'Everything' (for F24+) and 'Server'
(for <F24, as Everything wasn't installable until F24) but we
set it to 'Server' for the server images and 'Workstation' for
the desktop images, so those installs will use the correct
variant install class.
We run the installs in VNC. You can do it with a serial console
and log the output, but then anaconda gets clever and changes
several things in the installed system based on the fact that
you did the install over a serial console: it twiddles with
the kernel args and doesn't set graphical.target as the default.
We don't want any of that mess, so we do a VNC install.
The 'size' value is just a number of gigabytes for virt-install
images (as that's how the virt-install 'size' argument works).
This also drops some unused 32-bit images (we don't do 32-bit
KDE or Server upgrade tests, so there's no need to build those
images).
Test Plan:
Re-generate all affected images and re-run all tests
that use them, make sure they work. I am doing this on staging
at present. Note: this would render D911 unnecessary.
Reviewers: garretraziel
Reviewed By: garretraziel
Subscribers: tflink
Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D917
2016-07-04 16:29:25 +00:00
|
|
|
imsettings-qt
|
|
|
|
|
-initial-setup
|
|
|
|
|
-initial-setup-gui
|
|
|
|
|
%end
|