starlingx/integ
Code Issues Proposed changes
583e744578
integ/centos_iso_image.inc

224 lines
2.5 KiB
PHP
Raw Normal View History

Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# List of packages to be included/installed in ISO
# If these have dependencies, they will be pulled in automatically
#
# qemu-kvm-ev
qemu-kvm-ev
qemu-img-ev
qemu-kvm-tools-ev
# libvirt
libvirt
libvirt-docs
libvirt-daemon
libvirt-daemon-config-network
libvirt-daemon-config-nwfilter
libvirt-daemon-driver-network
libvirt-daemon-driver-nwfilter
libvirt-daemon-driver-nodedev
libvirt-daemon-driver-secret
libvirt-daemon-driver-storage
libvirt-daemon-driver-qemu
libvirt-daemon-driver-lxc
libvirt-client
# lldpd
lldpd
# tss2
tss2
# libtpms
libtpms
# python-3parclient
python-3parclient
# python-lefthandclient
python-lefthandclient
# docker-distribution
docker-distribution
# helm
helm
Add support for Helm v3, chartmuseum, and armada chart This adds support for Helm v3: - 'helm init' and 'helm serv' were removed in v3, and helm initialization was simplified so that is not required in build. - chart validation and version checking is enforced with 'helm lint', so all Charts require the tag: apiVersion: v1 (or v2). - 'chartmuseum' is a drop-in replacement for 'helm serv', and is currently used for building charts only. It is not part of ISO image. - armada chart is built and installed to /opt/extracharts. This provides a Kubernetes pod with armada-api and tiller containers. This provides a Helm v2 client (i.e., helmv2-cli) that gives access to containerized armada/tiller managed charts. This can be used as an interactive shell, or as a wrapper for single helm v2 commands. Change-Id: Iff2b219ea765cf9278c6e80c6aeb5b98cc9a0626 Depends-On: https://review.opendev.org/732731 Story: 2007000 Task: 38893 Signed-off-by: Jim Gauld <james.gauld@windriver.com>
2020-04-07 14:13:34 -04:00
# armada
armada
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# rpm
rpm-plugin-systemd-inhibit
# dpkg
dpkg
# ldapscripts
ldapscripts
# drbd
drbd
drbd-utils
drbd-udev
drbd-pacemaker
drbd-heartbeat
drbd-bash-completion
# initscripts
initscripts
# setup
setup
# nss-pam-ldapd
nss-pam-ldapd
refactor nfs-utils Story: 2004404 Task: 28046 since there is no src patch, move the meta patch setting to config package. And replace srpm with rpm. The 4 service files(rpc-statd/rpc-statd-notify) from nfs-utils are kept to avoid rpm audit complain. Just disable them by default. The service/conf files in files folder are not used, so just remove them. Test: Pass build and multi node deploy test. Confirmed The 4 services are disabled. Other services are the same as before. Change-Id: I42d2ef3d61c1f62fe8aaea5467c810fc6e39dc13 Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
2018-11-30 20:09:22 +08:00
# nfs-utils series package
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# dhcp
dhcp
dhclient
# openssh
openssh
openssh-clients
openssh-server
# facter
facter
# vim
vim-enhanced
# python
python
# libvirt-python
Upgrade libvirt to version 4.7.0 Includes the libvirt-python package upgrade as well. Note that the generated package is now called python2-libvirt. Story: 2003339 Task: 24377 Story: 2003396 Task: 24522 Depends-On: https://review.openstack.org/#/c/605230/ Change-Id: Iad2c521c2f2fc871589f793c5902555d3c3c41f4 Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
2018-09-24 18:28:03 -04:00
python2-libvirt
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# lighttpd
lighttpd
lighttpd-fastcgi
lighttpd-mod_geoip
lighttpd-mod_mysql_vhost
Add collection of linuxptp patches This commit applies several patches to the linuxptp srpm in order to address an issue syncing multiple interfaces on a ptp node. The srpm used is linuxptp-2.0-2.el7.src.rpm. Patch descriptions: base/linuxptp/centos/meta_patches: 0001 updates the srpm spec file to apply the patches during build 0002 updates the package versioning to comply with the STX format base/linuxptp/centos/patches: Patches 0001-0005 combine to correct a fault present when a ptp node is configured with multiple clocks in jbod mode which results in the client port getting stuck in the UNCALIBRATED state and unable to lock to the Grandmaster clock. The root of the issue lies in the sanity check where checking timestamps recieved on multiple ports will result in the sanity_freq_limit threshold constantly being reached and the servo for that port is repeatedly reset, preventing it from ever syncing. The changes in patches 0001-0005 have been written by Miroslav Lichvar on the linuxptp-devel mailing list. They are currently under review and testing by the upstream linuxptp maintainers prior to merging. I was able to apply them as-is to linuxptp v2.0. I have chosen to keep them as individual patches, as that is how they will appear upstream. Patch 0006 is my work and serves to address an issue in phc2sys where the local ptp clocks are not synced together properly if the local time is far behind the reference time. This issue ocurrs when phc2sys starts and there is no client port currently synced to a grandmaster. In the original behaviour, phc2sys selects the first configured port and proceeds to sync all of the other clocks to it by performing the first_step operation. Then ptp4l will evenually lock to the Grandmaster clock, and that single port will have its time updated to the correct value, but phc2sys has already performed the first_step operation and will not step the other clocks again. My solution is to provide an option to disable the selection of a default port by phc2sys. When no default port is selected, phc2sys waits for ptp4l to sync to the Grandmaster before bringing the other clocks into sync with the first_step operation. This option is configured via the default_sync parameter or the -D flag. The default_sync parameter is set to on by default to in order to keep the behaviour the same as upstream linuxptp but can be configured by users via system service-parameter-add ptp global default_sync=0 Closes-Bug: 1930607 Signed-off-by: Cole Walker <cole.walker@windriver.com> Change-Id: I2f660787c6753dcd4fc4c51da7b08ab9e6f197f4
2021-06-24 14:49:51 -04:00
# linuxptp
linuxptp
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# logrotate
logrotate
# novnc
novnc
# sudo
sudo
remove lshell There is security related issue with lshell, and it is not maintained now. So remove it from our system to avoid security issue. To remove lshell: 1. Package sudo-config is created for wrs.sudo configure file following the refactor process. 2. ldapusersetup in ldapscripts is modified to use bash only. lshell support is removed. ldapusersetup related patches are merged into 1 for easy maintenance. Test has been done: Build and deploy test is done, also unit tests for ldap are executed with pass, except lshell related test. Closes-Bug: 1795451 Change-Id: Ia5de1bc94d22eb6c9bea6d9a96e92564ad848b19 Signed-off-by: slin14 <shuicheng.lin@intel.com>
2018-10-16 19:43:58 +08:00
# config files
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# openldap
openldap
openldap-servers
openldap-clients
# openvswitch
openvswitch
# libevent
libevent
# tpm2-tools
tpm2-tools
# audit
# puppet
puppet
# systemd
systemd
# tboot
tboot
# memcached
memcached
# kubernetes
Split kubernetes into versioned stages and unversioned package This packages kubernetes in versioned subdirectories to be able to support upgrading multiple versions of kubernetes without collisions. Common configuration/environment files are moved to the new kubernetes-unversioned package. This creates directories: /usr/local/kubernetes/<version>/stage1 /usr/local/kubernetes/<version>/stage2 The binaries and configuration or kubernetes-node, kubernetes-kubeadm, and kube-client are placed in new locations, e.g., /usr/local/kubernetes/1.18/stage1/usr/bin/kubeadm /usr/local/kubernetes/1.18/stage2/usr/bin/{kubelet,kubectl} A new package kubernetes-unversioned contains directories: /usr/local/kubernetes/current/stage1 /usr/local/kubernetes/current/stage2 This package contains symlinks of all the expected binaries and configuration needed to run kubernetes. For example, /usr/bin/kubelet is a symlink to /usr/local/kubernetes/current/stage2/user/bin/kubelet. At ansible install time and during subsequent boots, there is code in place to bind-mount /usr/local/kubernetes/<version>/stageX onto /usr/local/kubernetes/current/stageX . This removes redundant doc and man pages from the production rpms. Story: 2008972 Task: 43002 Depends-On: https://review.opendev.org/c/starlingx/ansible-playbooks/+/802898 Signed-off-by: Jim Gauld <james.gauld@windriver.com> Change-Id: I74dc867faea6759906a687cef0b0ebf9555829ee
2021-08-11 09:49:49 -04:00
kubernetes-unversioned
Replace K8s 1.21.3 with 1.21.8 In testing K8s 1.21.8 used less CPU than 1.21.3, so we are moving to the newer version. This has been booted in vbox and a basic pod has been started. A full regression will be performed. Depends-On: https://review.opendev.org/c/starlingx/compile/+/824802 Partial-Bug: 1957994 Signed-off-by: Chris Friesen <chris.friesen@windriver.com> Change-Id: I64e4a64c90ef7591aeee52742dfcba9fdd8e5063
2022-01-07 20:49:31 -05:00
kubernetes-1.21.8-node
kubernetes-1.21.8-kubeadm
kubernetes-1.21.8-client
Add kubernetes 1.22.5 pkg Here are the changes needed for adding k8s v1.22.5 in StarlingX alongside with the changes needed for the build environment to find and build the package. The package builds successfully. Deployed an iso with k8s 1.22.5 on AIO-SX and AIO-DX. The deployment phase works and the pods are up and running after the upgrade completes. Story: 2009789 Task: 44305 Signed-off-by: Daniel Safta <daniel.safta@windriver.com> Change-Id: Ibb9be075fa0b1491b9ab1854ebb1fddf4df53461
2022-01-19 09:35:50 +00:00
kubernetes-1.22.5-node
kubernetes-1.22.5-kubeadm
kubernetes-1.22.5-client
Add Kubernetes 1.23.1 pkg Changes for adding Kubernetes 1.23.1 in StarlingX, including build environment updates. The package builds successfully. Built and installed an iso with K8s 1.23.1 on AIO-SX. Depends-On: https://review.opendev.org/c/starlingx/compile/+/825651 Story: 2009830 Task: 44424 Change-Id: I3e2b793d7b88057fc597b2445bddd137bb2b4fcf Signed-off-by: Gleb Aronsky <gleb.aronsky@windriver.com>
2022-01-05 13:06:05 -05:00
kubernetes-1.23.1-node
kubernetes-1.23.1-kubeadm
kubernetes-1.23.1-client
Revert "Revert "add containerd package for kata container support"" This reverts commit ff7b8ffd6a91d4fe3b59f939d59bf1512e524c60. Depends-On: https://review.opendev.org/703263 Change-Id: I9ed3cc54bb61d6e49219c9c98571740f0e066c3f Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
2020-01-19 01:59:42 +00:00
containerd
Introduce k8s pod recovery service Add a recovery service, started by systemd on a host boot, that waits for pod transitions to stabilize and then takes corrective action for the following set of conditions: - Delete to restart pods stuck in an Unknown or Init:Unknown state for the 'openstack' and 'monitor' namespaces. - Delete to restart Failed pods stuck in a NodeAffinity state that occur in any namespace. - Delete to restart the libvirt pod in the 'openstack' namespace when any of its conditions (Initialized, Ready, ContainersReady, PodScheduled) are not True. This will only recover pods specific to the host where the service is installed. This service is installed on all controller types. There is currently no evidence that we need this on dedicated worker nodes. Each of these conditions should to be evaluated after the next k8s component rebase to determine if any of these recovery action can be removed. Change-Id: I0e304d1a2b0425624881f3b2d9c77f6568844196 Closes-Bug: #1893977 Signed-off-by: Robert Church <robert.church@windriver.com>
2020-09-02 00:59:44 -04:00
k8s-pod-recovery
Implement CNI cache file cleanup for stale files It has been observed in systems running for months -> years that the CNI cache files (representing attributes of network attachment definitions of pods) can accumulate in large numbers in the /var/lib/cni/results/ and /var/lib/cni/multus/ directories. The cache files in /var/lib/cni/results/ have a naming signature of: <type>-<pod id>-<interface name> While the cache files in /var/lib/cni/multus have a naming signature of: <pod id> Normally these files are cleaned up automatically (I believe this is the responsibility of containerd). It has been seen that this happens reliably when one manually deletes a pod. The issue has been reproduced in the case of a host being manually rebooted. In this case, the pods are re-created when the host comes back up, but with a different pod-id than was used before In this case, _most_ of the time the cache files from the previous instantiation of the pod are deleted, but occasionally a few are missed by the internal garbage collection mechanism. Once a cache file from the previous instantiation of a pod escapes garbage collection, it seems to be left as a stale file for all subsequent reboots. Over time, this can cause these stale files to accumulate and take up disk space unnecessarily. The script will be called once by the k8s-pod-recovery service on system startup, and then periodically via a cron job installed by puppet. The cleanup mechanism analyzes the cache files by name and compares them with the id(s) of the currently running pods. Any stale files detected are deleted. Test Plan: PASS: Verify existing pods do not have their cache files removed PASS: Verify files younger than the specified 'olderthan' time are not removed PASS: Verify stale cache files for pods that do not exist anymore are removed. PASS: Verify the script does not run if kubelet is not up yet. Failure Path: PASS: Verify files not matching the naming signature (pod id embedded in file name) are not processed Regression: PASS: Verify system install PASS: Verify feature logging Partial-Bug: 1947386 Signed-off-by: Steven Webster <steven.webster@windriver.com> Change-Id: I0ce06646001e52d1cc6d204b924f41d049264b4c
2021-10-15 10:00:20 -04:00
k8s-cni-cache-cleanup
uprev the containernetwork-plugins This commit upgrades the containernetwork plugins to version 0.9.1 As there is no existing upstream package for this version for StarlingX, it is being built based on the downloaded source and centos7 spec file. Note: previous commit 303ed35 was reverted because of an issue with the centos_tarball-dl.lst and the autosetup command of the spec file. The second parameter of the centos_tarball-dl.lst specifies the top level directory name of the package. If the dl_tarball script detects that this TLD differs from that of the downloaded tarball, the TLD is changed to that of the 2nd parameter. In this case, the TLD of the downloaded package was 'plugins-0.9.1', while the centos_tarball-dl.lst had specified 'containernetworking-plugins-v0.9.1'. The two options to fix this incompatibility are to either change the TLD in the centos_tarball-dl.lst to match the downloaded version, or to modify the .spec file to run the autosetup command against the re-named TLD. This commit chooses the 2nd option, which allows for the package to built against any mirror dl that already has the containernetworking-plugins download present in it. Plugins tested: bridge vlan host-device dhcp host-local static tuning portmap bandwidth Story: 2008972 Task: 42977 Signed-off-by: Steven Webster <steven.webster@windriver.com> Change-Id: Ice12cbeacaeadc8beaa22152ca2a6104d31eec8b
2021-08-13 11:16:31 -04:00
containernetworking-plugins
Add bond-cni container network plugin This commit adds the bonding CNI plugin to StarlingX. The bonding CNI plugin allows a container to bond multiple interfaces together to be used in a fail-over or load balancing configuration. https://github.com/k8snetworkplumbingwg/bond-cni Note that this plugin (for now) resides outside of the main containernetwork project, and is still part of the k8s network plumbing working group project. As such, it is required to build this plugin separately. v1.0 of the bond-cni was released in 2018. Since then, 14 commits containing such things as doc clean-ups and bug fixes have been committed. We pick up these additional fixes by clamping down on the latest commit SHA. Testing: - Configure bond interface name (ifName) - Configure miimon value (miimon) - Configure and verify traffic path for modes (mode): - balance-rr (0) - active-backup (1) - balance-xor (2) - broadcast (3) - 802.3ad (4) - balance-tlb (5) - balance-alb (6) - Configure and verify behaviour for fail-over-mac modes (failOverMac): - none (0) - active (1) - follow (2) - Configure linksInContainer: - take lower interfaces existing on host - take lower interfaces existing on container - Links tested: - virtual interfaces - SR-IOV VF interfaces Story: 2009800 Task: 44344 Change-Id: I7bffaa272ffe9eba85c3aa0a26b9c4f61428b640 Signed-off-by: Steven Webster <steven.webster@windriver.com>
2022-01-26 17:20:41 -05:00
bond-cni
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# resource-agents
resource-agents
add isolcpus device plugin for kubernetes In order to minimize latency as much as possible, we want to allow kubernetes containers to make use of CPUs which have been specified as "isolated" via the kernel boot args. This commit creates an isolcpus device plugin, which detects the isolated CPUs and exports them to kubelet via the device plugin API. See kubernetes/plugins/isolcpus-device-plugin/files/README.md for more information on the behaviour and design choices for this commit. When we move to a newer version of the Intel device plugin manager we may be able to simplify some of this. See the above README.md file for details. Change-Id: I3bfe04ab6e7fbafefa63f6dc43cb2ed79a52579f Story: 2008760 Task: 42165 Signed-off-by: Chris Friesen <chris.friesen@windriver.com>
2020-04-14 20:16:48 -04:00
# isolcpus device plugin for K8s
isolcpus-device-plugin
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
Add Kubectl Cert Manager This commit adds the kubernetes plugin kubectl cert manager to the iso. This is used to convert old v1alpha2 and v1alpha3 cert manager resources to v1 during a system upgrade. The plugin is not required for debian because there are no old cert manager resources to convert. Test Cases: PASS: Convert our default DC certificates and issuers using kubectl cert manager Change-Id: I59f1b0e4d5d6ece1ccef43fee1acacd7b7e44efd Story: 2009837 Task: 45372 Signed-off-by: Jerry Sun <jerry.sun@windriver.com>
2022-05-13 19:04:14 -04:00
# kubectl-cert-manager
kubectl-cert-manager
Split image.inc across git repos Currently compiling a new package and adding it to the iso still requires a multi-git update because image.inc is a single centralized file in the root git. It would be better to allow a single git update to add a package. Too allow this, image.inc must be split across the git repos and the build tools must be changed to read/merge those files to arrive at the final package list. Current scheme is to name the image.inc files using this schema. ${distro}_${build_target}_image_${build_type}.inc distro = centos, ... build_target = iso, guest ... build_type = std, rt ... Traditionally build_type=std is omitted from config files, so we instread use ${distro}_${build_target}_image.inc. Change-Id: Ic0d076b4537f6edbd0c058c0dab667fea68de647 Story: 2003447 Task: 24649 Depends-On: Ib39b8063e7759842ba15330c68503bfe2dea6e20 Signed-off-by: Scott Little <scott.little@windriver.com>
2018-08-15 14:11:12 -04:00
# haproxy
haproxy
# iptables
# python-psycopg2
python-psycopg2
# dnsmasq
dnsmasq
dnsmasq-utils
# parted
parted
# python-keyring
python-keyring
# grub2
grub2-tools
grub2-efi-x64-modules
Add python2-ruamel-yaml to controllers This change adds the package to the list of files included on the ISO and installed on nodes be default. Depends-On: https://review.openstack.org/615923 Change-Id: Ie42771672d867140728905bce7b011f7f375cfd3 Signed-off-by: Jason McKenna <jason.mckenna@windriver.com> Story: 2004240 Task: 27763
2018-11-06 11:10:47 -05:00
# python2-ruamel-yaml
python2-ruamel-yaml
Refactor patches for util-linux package Use util-linux-config package to package config files for util-linux. Remove util-linux package folder and use RPM instead of SRPM for util-linux. Deployment test and ping test between VMs pass Config file check pass. Story: 2003768 Task: 27595 Depends-on: https://review.openstack.org/#/c/618943/ Change-Id: If90ed6df4a875a576c7ac709589ac221bb0fa2e3 Signed-off-by: zhipengl <zhipengs.liu@intel.com>
2018-11-20 18:15:13 +08:00
Add redfishtool package Add redfishtool package to controller nodes It will be used by maintenance processes(mtcAgent and hwmon). Two patches are required. 1. python2 support patch 2. config file support patch Deploy test pass redfishtool can run normally in controller node. Story: 2005861 Task: 34187 Depends-On: https://review.opendev.org/665993/ Change-Id: I69e08cffd8587cb4287394f2b7a2f46fd3d054d9 Signed-off-by: zhipengl <zhipengs.liu@intel.com>
2019-06-20 23:14:09 +08:00
# redfish tool
Redfishtool
Add back kvm_timer_advance_setup.service The kvm_timer_advance_setup service was packaged and installed as part of nova-compute package prior to containerizing nova. The service file has been updated to start before kubelet. The service becomes enabled by puppet which writes a config file containing the vcpu_pin_set information. The utility script has been updated. The .sh extension has been added, and it passes bashate. Updated the license to GPLv2 since the tuned package where the script was dervied from is GPLv2. Change-Id: Iff90c46826a88283e42a980e7823593599f03206 Closes-Bug: 1823751 Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
2019-07-22 12:28:50 -05:00
# kvm-timer-advance (AIO and worker nodes only)
kvm-timer-advance
Add boto3 to build boto3 is a python package for interacting with AWS. we need this for interacting with an Amazon Docker registry. This commit adds boto3 and its dependencies to the build Story: 2006274 Task: 36704 Depends-On: https://review.opendev.org/683179 Change-Id: I5a5c7ea7b20c012b51ee20057a1ebd0f0c635386 Signed-off-by: Jerry Sun <jerry.sun@windriver.com>
2019-09-19 11:20:02 -04:00
# aws packages for interacting with amazon aws registry
# botocore is an unspecified requirement of boto3
python2-botocore
python-boto3
Add: PF Baseband Device config application for ACC100 This introduces PF BBDEV (baseband device) Configuration Application "pf_bb_config" and inih. PF BBDEV program accesses the configuration space and sets the various parameters through memory-mapped IO read/writes. This is needed for Intel ACC100 (Mt Bryce) configuration and QMGR related settings. PF BBDEV requires inih for parsing .INI configuration file. This commit adds the inih for static linkage with PF BBDEV. Story: 2008440 Task: 41472 Signed-off-by: Babak Sarashki <zbsarashki@gmail.com> Change-Id: Idaebcac5d0021d5c11c7ab27e13176139ba66c3b
2021-02-04 23:21:48 +00:00
# Pf bbdev configuration tool for ACC100 (Mt. Bryce)
pf-bb-config
Update kexec-tools/makedumpfile to support v5.10 kernel This patch updates kexec-tools from 2.0.15 to 2.0.21 (and its supporting software package makedumpfile from 1.6.2 to 1.6.9) for compatibility with the newer v5.10 kernel. This commit clones the kexec-tools package's supporting files from commit 26a7a543427eac59ed39728466f3d95d320f735a in the CentOS RPM packaging git repository. Links for reference: - https://git.centos.org/rpms/kexec-tools/c/26a7a543427eac59ed39728466f3d95d320f735a?branch=c7 - https://git.centos.org/rpms/kexec-tools/tree/26a7a543427eac59ed39728466f3d95d320f735a Please note that this patch causes the build system to pull in and extract an SRPM file to acquire: kdump-anaconda-addon-003-29-g4c517c5.tar.gz This is done for security, because the only public reference to commit 4c517c5 is on a Red Hat developer's personal Github account: https://github.com/ryncsn/kdump-anaconda-addon/commits/rhel-7 kexec-tools package's supporting files cloned by this commit trigger a large number of shell script linting errors. Given that the shell scripts in question are inherited from upstream (i.e., CentOS 7), the "files" directory of this package is excluded from automated linting via the changes in tox.ini. Verification: A kexec-tools RPM package built with this commit was installed onto an existing StarlingX system. A vmcore file was succesfully collected from a kernel crash triggered with /proc/sysrq-trigger. A recent version of the crash utility was found to succesfully parse the collected vmcore file. Credits: Thanks to Jiping Ma for helping with cleaning up and publishing an earlier version of this patch. Story: 2008921 Task: 43040 Depends-On: https://review.opendev.org/c/starlingx/tools/+/805127 Signed-off-by: Jiping Ma <jiping.ma2@windriver.com> Signed-off-by: M. Vefa Bicakci <vefa.bicakci@windriver.com> Change-Id: Idc4e523610e4c09259300c8b67ea5e0fbe59c611
2021-10-18 11:29:50 -04:00
# kexec-tools
kexec-tools
Add iproute-tc to the ISO image iproute was updated from 4.11 to 5.12 with commit a7760b40a266 ("iproute: Update from 4.11.0-14 to 5.9.0-4") and commit 36673774ee3c ("iproute-5.12, iptables-1.8.4, and libnftnl-1.1.5"). In CentOS 7, the iproute-4.11 RPM package included the 'tc' utility, but with CentOS 8, tc was moved to a separate RPM package, "iproute-tc". The original version of the second aforementioned commit added the iproute-tc RPM package in the ISO, but iproute-tc was later removed from the ISO during the code review, as it was not known at the time that tc had been split into a separate package (iproute-tc) between CentOS 7's iproute 4.11 and CentOS 8's 5.9/5.12, and that tc used to be included in the StarlingX ISO before the iproute updates. This commit explicitly adds the iproute-tc package into the ISO image to make tc available in StarlingX installations again. To prevent another similar issue, the iproute spec file was scanned for %package declarations to see if any other new sub-packages had been introduced since CentOS 7, and only the iproute-tc package was seen. Verification: - ISO build was successful. - Resulting bootimage.iso file was confirmed to contain the iproute-tc RPM package via "iso-info -f -i bootimage.iso | grep iproute-tc". - Note that run-time testing of the tc utility had been carried out in the past for eBPF testing by manually installing the iproute-tc RPM package to a running StarlingX installation. Closes-Bug: #1951989 Signed-off-by: M. Vefa Bicakci <vefa.bicakci@windriver.com> Change-Id: I8422f0aa872101e85502f1f3f0d3dc62ec19b8bb
2021-11-23 11:02:49 -05:00
iproute-tc
Copy Permalink