starlingx/metal
Code Issues Proposed changes

Update kickstarts to generate DNF repo config files

Browse Source 
As the patching framework is updated to use DNF instead of the smart
package manager, the kickstarts are updated to generate the initial
DNF repo config files, rather than configure the smartpm channels.

Depends-On: https://review.opendev.org/700961
Change-Id: Ic625aa4646b45719c9527159aa46f157a4d2cff0
Story: 2006227
Task: 37935
Signed-off-by: Don Penney <don.penney@windriver.com>
This commit is contained in:
Don Penney 2020-01-02 17:40:09 -05:00
parent 8959d8258d
commit 09b95bf651
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
bsp-files/kickstarts/post_common.cfg
View File

@ -31,25 +31,25 @@ else
fi
. /etc/platform/platform.conf
# Configure smart package manager channels
rm -rf /var/lib/smart
mkdir /var/lib/smart
/usr/bin/smart channel -y \
--add rpmdb type=rpm-sys name="RPM Database"
/usr/bin/smart channel -y \
--add base type=rpm-md name="Base" baseurl=http://controller:${http_port:-8080}/feed/rel-xxxPLATFORM_RELEASExxx
/usr/bin/smart channel -y \
--add updates type=rpm-md name="Patches" baseurl=http://controller:${http_port:-8080}/updates/rel-xxxPLATFORM_RELEASExxx
# Configure smart to use rpm --nolinktos option
/usr/bin/smart config --set rpm-nolinktos=true
# Configure smart to use rpm --nosignature option
/usr/bin/smart config --set rpm-check-signatures=false
# Delete the CentOS yum repo files
rm -f /etc/yum.repos.d/CentOS-*
# Create platform yum repo file
cat >/etc/yum.repos.d/platform.repo <<EOF
[platform-base]
name=platform-base
baseurl=http://controller:${http_port:-8080}/feed/rel-xxxPLATFORM_RELEASExxx
gpgcheck=0
enabled=1
[platform-updates]
name=platform-updates
baseurl=http://controller:${http_port:-8080}/updates/rel-xxxPLATFORM_RELEASExxx
gpgcheck=0
enabled=1
EOF
# Persist the boot device naming as UDEV rules so that if the network device
# order changes post-install that we will still be able to DHCP from the
# correct interface to reach the active controller. For most nodes only the