Reorganizing docs as recommended in:
https://www.divio.com/blog/documentation/
This is simply a reorganization of the existing documents and changes
no content EXCEPT to correct the location of sphinx doc references.
Expect followup changes to change document names (to reflect the new
structure) and to move content from existing guides (e.g., to move the
pipeline/project/job structure definitions out of the "Project Configuration"
reference guide into their own reference documents for easier locatability).
All documents are now located in either the "overview", "tutorials",
"discussions", or "references" subdirectories to reflect the new structure
presented to the user. Code examples and images are moved to "examples" and
"images" root-level directories.
Developer specific documents are located in the "references/developer"
directory.
Change-Id: I538ffd7409941c53bf42fe64b7acbc146023c1e3
As this is the lastest stable version of ansible.
Change-Id: I02a0e9703a61b3976cec559a1069b51616c3d447
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We have noticed that some quickstart jobs fail due to timeouts waiting
to connect to mariadb. On further investigation I've found that this
slowness is related to bootstrapping of TZINFO tables on initial startup
[0][1].
The workaround for this problem that I've chosen is to disable this
TZINFO generation on startup. Other options include using mariadb 10.4.7
(10.4.8 introduced the issue upstream), switching to mysql or percona,
or increasing out timeout to cover the longer startup time (probably
want to set the timeout around 5 minutes).
[0] https://github.com/docker-library/mariadb/issues/261
[1] https://github.com/docker-library/mariadb/issues/262
Change-Id: Ib27681c1e5ac25a0a5f75a6b1bfb24029d0be3c8
Updates the environment variable processing to only affect variables
prefixed with ZUUL_.
Adds a test showing the os.environ with % in it.
This reverts commit b3929b5633.
Change-Id: Ic6c3dd0327ef70dc1375486827e4503a4cea9bfc
In prod for OpenDev we're seeing things like this:
http://paste.openstack.org/show/785704/
which lead us to believe this is somehow connected.
This reverts commit f2229705f3.
Change-Id: I0b73b71f72483e6c6e511411c3c59729761cec9b
This will allow users to set environment variables with sensitive
strings like passwords, but keep a single config file. This comes
in handy when using Kubernetes in particular, as it wants to
handle sensitive data and templated config files in a very different
manner.
Change-Id: I38f6c4da82e1647ad197908f19ea6df23e04fc32
To increase the chances that job_dir and git_dir are on the
same filesystem in the default configuration, set the default
job_dir to /var/lib/zuul/builds.
Also, all zuul container images specify a volume at /var/lib/zuul,
therefore the docker-compose file does not need to specify the
same for the scheduler container.
Due to this, we were inadvertently running the executor with the
git_dir and job_dir on different filesystems in the quick-start.
That should no longer be the case.
Change-Id: I2fe5eea588006da7181c3ea8ad2637598764e8f1
With the removal[*] of refs/publish in Gerrit 3.0.0, git-review
1.27.1 or later is needed to avoid attempting a push there and
ultimately failing. The git-review package in Ubuntu 18.04 LTS is
too old (1.26.0), so use latest from PyPI instead.
Adjust the quick-start document to install git-review with pip, and
on Debian/Ubuntu suggest including the python3-pip distro package
since it's split out separate from the interpreter packages.
[*] https://gerrit-review.googlesource.com/c/gerrit/+/192494
Change-Id: I247fb761667a99cf9f25478b49c5a1fe5d11a6cf
This file may be required by recent containers tool when doing unshare
actions.
Also make the image build jobs non-voting temporarily since they are
broken by the issue this change fixes.
Also, pin docker image to 2.16.8 for quick-start (squashed in here
to be able to merge again):
The new version 3.0.0 needs some configuration adjustment, git-review is
failing with:
remote: error: branch refs/publish/master:
remote: You need 'Create' rights to create new references.
remote: User: user
remote: Contact an administrator to fix the permissions
Change-Id: Iab45bf2322edf8a10d2d41a1fc9a098e17a39ea7
Ensure that any container making use of no_proxy has the full list of
services it needs to talk to listed, and also allow for pass-through of
http and https proxy settings.
There is no need to use `*_proxy=...` unless modifying the value as
docker-compose will simply ignore unset environment variables.
Ensure the node built to run jobs is injecting any proxy env variables
added at build time in a manner that can be transparently picked up by
ansible jobs.
Change-Id: Ibc91cb40f92c2e7708640819e4ed36c70445d859
As a first step towards supporting multiple ansible versions we need
tooling to manage ansible installations. This moves the installation
of ansible from the requirements.txt into zuul. This is called as a
setup hook to install the ansible versions into
<prefix>/lib/zuul/ansible. Further this tooling abstracts knowledge
that the executor must know in order to actually run the correct
version of ansible.
The actual usage of multiple ansible versions will be done in
follow-ups.
For better maintainability the ansible plugins live in
zuul/ansible/base where plugins can be kept in different versions if
necessary. For each supported ansible version there is a specific
folder that symlinks the according plugins.
Change-Id: I5ce1385245c76818777aa34230786a9dbaf723e5
Depends-On: https://review.openstack.org/623927
To improve the experience for new users, have the mergers automatically
add new ssh hosts to their known hosts files. They will still validate
existing entries, so a paranoid sysadmin can still pre-populate the file
to avoid trojan attacks on the initial connection. New users in the
typical case of a secure internal network will not need to manually add
host keys to start Zuul.
This matches the behavior of the scheduler with its stream-events
connection to Gerrit.
Change-Id: Ib416bbb2ffcfedd5d114709af3931e154a1a92ac
We actually have a specific container for nodepool-launcher, lets use
that over the base nodepool container. We do this incase in the future
pbrx add new things for the nodepool-launcher entry point.
Change-Id: I636c1d9129765287d3a22b9edcf39f3645e44b77
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This allows us to show build history in the web ui.
Also add a local test playbook for the quickstart which basically
does what the zuul-quick-start job does, but expects to run locally
on a workstation (ie, does not install the docker registry and
docker).
Change-Id: Id62dcf69f48399dab3d1259679bf2fc2ce50460e
It takes a long time to install ansible, but we have it installed
already in the zuul image (for the executor). Just use that instead.
Change-Id: I2dc2d6f5e5e83bb0654c45b27b8d37dc161f7841
Use docker-compose to get a zuul+nodepool+gerrit up and configured
so that we can write walkthrough documentation which starts with
a running system.
Change-Id: I5819aee1fb9c3af72eb31818da476df074424225
Co-Authored-By: Tobias Henkel <tobias.henkel@bmw.de>
David Shrewsbury