Only install nfs-utils bundle. This package was previously broken and
relied on a dependency in storage-utils, but this has since been fixed.
Add no_root_squash option for exporting a NFS mount to increase the read
performance.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
Koji will not work well if network and time
are not configured properly. All basic
configurations need performed on the host
first prior to attempting to install and
configure koji.
Do not bother using DNF to get the NVR of packages. Call out to RPM
directly instead.
More completely parameterize script to allow for sourcing of variables
from parameters.sh sometime in the future.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
When koji builder and koji master are hosted on different machines, NFS
mounting is needed to connect the services. Make this process more
smooth to minimize manual editing of files. Namely, change the top
directory that koji looks at. If on the master, this is on the local
file system. If on the builder not on the master, this is also on the
local file system, but is backed by a NFS mount in a different location.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
A deployment of a "koji" server consists of additional services that
support development beyond koji itself. These include
git/cgit/gitolite, a mash containing the current snapshot of the
packages in koji, and an upstreams package sources cache.
Because these are required for integration with a DevOps workflow, they
are not included by default in the ansible playbook.
OpenSSL complains if the RANDFILE does not exist when it is generating
certificates. Create an initial seed for this file from urandom.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
kojid will not be able to merge repos and mock will not be able to build
a chroot in an environment where proxy variables are used unless they
are defined in configuration files.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
Because the kojid capacity is difficult and error-prone to calculate
automatically, let the user define this. Default the kojid capacity to
what is listed in the pagure documentation.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
The capacity for kojid should scale according to the number of
processing units available because building packages is largely a
CPU-bound task. Defaulting to a safe capacity of one-fourth the number
of processing units.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
Making external repository usage optional based on how it's defined or
not defined in parameter.sh so users do not need to edit any script
besides this one.
Signed-off-by: George T Kramer <george.t.kramer@intel.com>
George T Kramer