The playbooks/roles/gitea-set-org-logos/files directory potentially
contains files which are not covered by any open source copyright
licenses, do add a document clarifying this.
Change-Id: I55cbc9c768d0c3c467a647aafbc82ece7cae989e
Over a few upgrades, we've managed to break some of the default avatar
logos you see when browsing code on opendev.org.
After investigating ways to fix this up, we established that there
isn't an exposed API for setting these, but we can do a simple query
to point to logo files on disk. This implements that.
One caveat is that the logos should be PNG files; particiularly we
note that SVG files don't work reliably because they don't get served
with the image/svg+xml mime-type.
Change-Id: Ie6799de2fb27e09f936c488258dc1bd1c638c370
Gitea 1.16 added partial clone support, but the clone filters pip
tries to apply (--filter=blob:none) don't work well when combined
with older cgit clients and lead to errors like "Server does not
allow request for unadvertised object" or "protocol error: bad pack
header".
Explicitly disable this feature server-side for now, so that clients
will fall back to making full clones.
Change-Id: Ia86394d5176c28567bf67b60578aadde6629c775
Depends-On: https://review.opendev.org/834196
openEuler yum mirror in Russia is down. This patch change the
rsync url to the official HongKong one.
This patch also fix the openEuler mirror url nit.
Change-Id: Ifb930e34fd7f16f77ba55bc489e5389c641139de
Switch the port 80 and 443 endpoints over to doing http checks instead
of tcp checks. This ensures that both apache and the zuul-web backend
are functional before balancing to them.
The fingergw remains a tcp check.
Change-Id: Iabe2d7822c9ef7e4514b9a0eb627f15b93ad48e2
We've been told these resources are going away. Trying to remove them
gracefully from nodepool. Once that is done we can remove our configs
here.
Depends-On: https://review.opendev.org/c/openstack/project-config/+/831398
Change-Id: I396ca49ab33c09622dd398012528fe7172c39fe8
These were added when we faced significant memory pressure on the old
server. That is no longer a problem and there is an issue with the
specification that breaks file compression due to destination files
already existing. It seems like the log specification is only able to
rotate once then it cannot keep moving files aside because they already
exist as eg jvm_gc.log.0.gz. This results in annoying errors in the
Gerrit error_log.
Note that it doesn't appear sufficient to remove this log specification
we also need to move the existing jvm_gc.log* files aside or delete
them. This was tested on a held zuul node and I stopped gerrit, updated
the docker-compose file, moved the files aside, then started gerrit and
that got rid of the startup errors in error_log. Merely updating
docker-compose resulted in the same errors on startup.
Change-Id: Ied1464c57b2e8331b9bdf7cbc9ad74f92dea2dfd
Once restarted onto the parent change, our Gerrit deployment will no
longer link to Gitiles representations of changes or the Git tree.
Explicitly deny access to the Gitiles URL base path in the Apache
vhost config, since we can't effectively remove the plugin itself.
This should help prevent search engines from finding its copies of
our projects rather than the ones we want people to use in Gitea.
Change-Id: I3c96221256662443f7a43344afd12194dce82b9d
This is a reimplementation of earlier change
I8efefe365f3b9ebe97c8c2ce322fa8c6f3b70b3a to link out to Gitea
instead of Gerrit's local Gitiles plugin. This should reduce the
complexity of what we're hosting on the Gerrit server, while at the
same time be less confusing for search engines and users. Configure
the Gitiles plugin to no longer take over Gerrit weblinks, and a
followup change will block access to its URL base path entirely.
Change-Id: I7e194fe5c907b39d53fd0663e06cbfd33a3ae410
Gerrit 3.4.0 stopped generating the is:mergeable predicated by default,
but it seems to be rather helpful for some reviewers. The computational
load caused by this is O(N^2) where N depends on the number of changes
open against a branch and their respective size. Since most of the
changes we process are rather small and also we didn't see a significant
reduction in load when we moved to 3.4, this isn't expected to be an
issue in our installation.
[0] https://www.gerritcodereview.com/3.4.html
[1] https://gerrit-documentation.storage.googleapis.com/Documentation/3.4.0/config-gerrit.html#change.mergeabilityComputationBehavior
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I9fce11b454255818e4a5817affed5b6e9c19f521
Without this our config changes are not applying to the running service
until something else reloads or restarts the service.
Change-Id: I4df229d1c42f06159a4b320d4b6a07c5239ca111
Previously we were only checking that Apache can open TCP connections to
determine if Gitea is up or down on a backend. This is insufficient
because Gitea itself may be down while Apache is up. In this situation
TCP connection to Apache will function, but if we make an HTTP request
we should get back an error.
To check if both Apache and Gitea are working properly we switch to
using http checks instead. Then if Gitea is down Apache can return a 500
and the Gitea backend will be removed from the pool. Similarly if Apache
is non functional the check will fail to connect via TCP.
Note we don't verify ssl certs for simplicity as checking these in
testing is not straightforward. We didn't have verification with the old
tcp checks so this isn't a regression, but does represent something we
could try and improve in the future.
Change-Id: Id47a1f9028c7575e8fbbd10fabfc9730095cb541
We have removed Fedora 34 from our CI system. Fedora has a short
lifetime for each release, and in this particular case Fedora 34 did not
boot reliably in all our clouds. Now that the images have been removed
we can remove the release from our mirrors too.
Change-Id: I07dfca0ef88dc9531e4cb2c67ebbca5e0503594e
Currently `gerrit show-queue -w -q` indicates we are only using 2
threads for service users and have 100 available for interactive users.
Unfortunately we really have three current classes of users: Humans,
Zuul, and everything else. We can't currently separate these into
different pools so instead we'll try using a single large pool and
sharing. To do that we set batchThreads to the special value of 0.
Change-Id: I08681a6b88683355ea5780ac452de903c8c8a7a3
In CS9 the layout of the repos has changed and the SIGs repos are in a
separatee directory under centos-stream [1] so we need to add a new
rsync command. These repos includes messaging for rabbitmq-server, nfv
for openvswitch and storage for ceph.
[1] http://mirror.stream.centos.org/
Change-Id: I90890aade7ad5f42e15c4c171ed2c2545f2310c4
As of pip 22.0, its HTML parser no longer accepts any page which
doesn't start with the string "<!DOCTYPE html>" and, unfortunately,
Apache's mod_autoindex declares a very specific HTML 3.2 doctype
instead, causing pip to break any time our wheel cache is added to
its indices. The main index we generate has been updated with
https://review.opendev.org/826969 but we need this change to address
Apache's dynamically generated file lists for that site.
Configure Apache to supply a custom header file for file indices
within the /wheel/ subtree of our mirror vhosts, and alias it from
outside the docroot in order to reduce clutter of the top-level
directory index. Also instruct mod_autoindex to omit its own
document preamble which would otherwise include the original doctype
declaration. Note that this omits the header title and H1 level
headings from the resulting pages, but as these are only meant for
machine parsing anyway and not humans, it's a compromise to keep the
solution as simple and straightforward as possible.
Change-Id: Id71174954b13b80483256d37f773b781f4956c21
Pip 22.0 doesn't support Python versions prior to 3.7, so the
unversioned get-pip.py script refuses to run under Ubuntu Bionic's
default python3 interpreter. Add a 3.6-specific URL instead to work
around this.
Change-Id: Icab5f4dd45d8f290a2f52db083cdc564e5a08776
The sql connection is no longer supported, we need to use "database"
instead. The corresponding hostvars change has already been made
on bridge.
Change-Id: Ibcac56568f263bd50b2be43baa26c8c514c5272b
The gerrit.config template is a gitconfig-like file, so is expected
to use tab characters for indentation. Half the indented lines used
tabs already, so make the rest consistent.
Change-Id: I6e77f0278a25d688b9517c275614485518923bc9
These two apt.conf.d config files are installed by different packages
but have overlap in the configuration they set. Unfortunately if the
wrong one sets the flag to disable periodic updates it wins based on apt
conf's priority rules.
To ensure that we continue to auto update and handle different packages
supplying different config files we manage the entirety of the periodic
config in both of these files at the same time using a common source
file.
Change-Id: I5e408fd7c343adb1de9ec564fe430a6f31ecc360
