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
We need the js tools to be present so that zuul from scratch install
docs produce a working javascript build. Add a step to that process to
run our helper script for js toolchain install.
Note this adds support for opensuse to that script as opensuse is a
valid from scratch install target.
Change-Id: I4c3584957f7a4afaeb0315a57d56f93e915eace1
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
The parameters passed to chown were incorrectly specifying the
user/group delimiter as '.' instead of ':'.
Change-Id: Ic2a258771328df32f8e4ca274413d0dcaadbff43
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
Use useradd rather than adduser[0] as some distros do not come with adduser
installed.
Additionally some distros do not use a group per user, instead ensure the
zuul and nodepool groups are created and assigned to their respective
users.
[0] https://askubuntu.com/questions/345974/what-is-the-difference-between-adduser-and-useradd
Change-Id: Id44a7dbc03896705aed576a05a2fe8db62d76272
This change adds the additional steps to follow while installing Zuul on
CentOS 7. The included steps are
- creation of zuul-scheduler.service.d, zuul-executor.service.d, and
zuul-web.service.d folders in /etc/systemd/system to place provided
drop-in files
- copying provided drop-in files to appropriate locations so ExecStart
and ExecStop commands can be overriden by systemd
Apart from the additional steps, the package installation command on Fedora27
is switched to yum to keep the differences between Fedora27 and CentOS 7 at
minimum.
Depends-On: https://review.openstack.org/#/c/565074/
Change-Id: I830be38cbb52c7b8aa95f1ad080341de40250d17
Also modify the Zuul From Scratch doc to reference these new files
in the service installation documents.
Depends-On: https://review.openstack.org/560993
Change-Id: Ifa0d1cd48ec5e1ef3358ada55b1b2769f392dfe9
In preparation for adding instructions for Gerrit and other
Linux derivatives, reorganize the "Zuul From Scratch" doc to
more easily incorporate those changes.
Also, just use the default Zookeeper config. That bit is
moved to be with the Zookeeper installation portion.
Change-Id: I206a2acf09eb8a2871ec61a00226654c798bb3eb
David Shrewsbury