In order to correctly sync each architecture's repos, we have to
override the basearch while running reposync. Otherwise we are just
syncing the the host architecture (x86_64) multiple times under
misleading directory names.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
Zstd repodata support was introduced in DNF quite some time ago, and
is quite a bit faster and less resource intensive.
Additionally, there is no point in producing sqlmd or DeltaRPMs when
support for both has been removed from RHEL for a fair bit of time.
Regardless, we should leave things mostly as-is for EPEL 9, and thus
we retain older xz compression settings for that.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
This should setup the rdu3 vlans with initial dns, which is just a copy
of our iad2 networks with 10.3 changing to 10.16.
Once rdu3 machines have network we should be able to use these to let
rdu3 hosts query the regular dns servers for things.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It turns out the ostree volumes are special in that they are NFS shares
mapped to the NetApp Volumes for OSTree repo storage. They have
specific names and require no storage class to be set. This reverts the
changes made yesterday.
These have to be in "s in order to do a string comparison, since
they were not, they were never matching anything. ;(
Fix them all up, and also block a few more repos on pagure that are
getting heavily crawled.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
In f42 in some cases mv will prompt here to overwrite the old file.
We always want to replace it, so add a -f here.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Since there is no PV fedora-ostree-content-volume-2 on stg
the volumeName: "fedora-ostree-content-volume-1" was added.
We use ocs-storagecluster-cephfs to keep the ReadWriteMany
functionality. If the RBD volume is required,
then use storageClassName: ocs-storagecluster-ceph-rbd.
ODF will provision a new volume automatically.
ReadWriteMany cannot be used in a Filesystem mode with RBD.
I broke the trigger when I switched from one container to multiple
containers in the pod. Syntax-wise, I found this multi-line variant in
the CoreOS Cincinnati deployment config, and it seems like there's not a
way to say "all container images in the spec". Or there might be, but I
couldn't find an example or documentation.
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
