With zuulv3 there is only a single configuration file now for
projects, no more external python files. Remove zuul_file_layout with
zuul_file_main_yaml.
Change-Id: I63d592999684b1437bb240405a62af0cc362e977
Depends-On: https://review.openstack.org/561475
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This was really to work around the need not to template our service
files. Mostly because I was scared how large and unmanageable they
would become. Let ansible do its job and remove the hacks we had in
our systemd unit file.
Change-Id: I5ae753d7c2a2d068750bd29400e7b736cc33df39
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We do this for ansible-role-nodepool, we might as well do it here.
Change-Id: I1976f05ec1ec6fdb69e255297dfa64ab00330e7c
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Currently all but zuul-web support the commandsocket, so use that over
kill which systemd does by default.
Change-Id: Ic4eacbf6c74c8b722189780b1845ece0ff485b99
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Currently all the other services in zuul do not support it, so we can
remove this logic as it is not needed.
Change-Id: I013c4331070491197a119ff2b2317efa2bce4bc4
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
In zuulv3 we added the fingergw process, update our role to support
that.
Change-Id: I2978bb3c53c2f0ed56a6536be110cb471f157ab2
Depends-On: https://review.openstack.org/551015
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Zuulv3 creates zuul-web which is needed for log streaming, secrets and
various other things.
Change-Id: Ib3378e6f726d0781750a48f80fe276d63c5c68f5
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Add an example tenant to layout.yaml to allow zuul-scheduler to start
properly.
Collect additional logs to add in debugging gate failures.
Change-Id: Ic8db52d90716fe8a73afba231ac3a063db2710db
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This are no longer used since we moved to systemd service config
files.
Change-Id: I69587b0088294a7c86ddd2d2b4091d125f17df62
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The recommended way to setup service config files is with using:
systemctl edit foo.service
This updates our systemd configuration files to support this.
Change-Id: I405d6063ad3d5fd529139d7ce17c3238924f2e45
Depends-On: I92801be5fadc91c72e562b4b8dfb2ed1af24a320
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
No need to support 2 LTS releases of ubuntu. Focus on ubuntu xenial.
Change-Id: Ib5d33346cb09bb58a2bca66905f1037345ec7364
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Now that we are running zuulv3-dev.o.o, we are in a good place to
switch to the feature/zuulv3 branch for our ansible role.
Switch out zuul-server with zuul-scheduler.
Add python2-dnf to bindep.txt for fedora-25 job.
Change-Id: Ib61063c9b542e04f2f14a165f23bc82062714bf8
Depends-On: Id54a479e2e1b406cd5fd526ec6d2ee118b28b8d7
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Because of a bug in ansible 2.2, it is easier for us to move to
systemd for ubuntu-xenial.
Change-Id: I0c4709f413b7beb131846b815a9e5c474b3221bb
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This migrates installation of config files from using 'copy' to 'template',
allowing downstream users of the role the ability to carry a template in their
playbooks and have it easily rendered out simply by overriding the
zuul_file_*_dest variables.
Note, this omits layout.yaml for the time being
Depends-on: I32cc11901bddd03125e1c4ce6f246d811f414cba
Change-Id: I9f5890a54ded2b0169aa76501828e7856e0d6583
This change tries to mitigate the "Too many open files" error happening
on busy deployment. This is using the same limit as in puppet-zuul
module.
Change-Id: I277865b06b98665e7c577703faf9369b90eec183
Add a helpful message that the zuul binaries are missing from init.d
scripts.
Change-Id: I703b2c5cce3a09d0330063cb65097dc7041648bc
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Currently we hardcode the user we use to start services. Allow the
user to decided who to use.
Sadly, we cannot support systemd services at this time. We likely need
to switch to the systemd task or write out own logic. We'll have to
revisting this in the future.
Change-Id: I338d167863509667b935ccc7490d796315bc6153
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Since it is possible for zuul to be installed into a virtualenv, we
need to expose the ability for a user to update the prefix for
services.
Change-Id: Ifb7e174a5ed338ed3d299e7e8a5deabd01b2f429
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
It is now possible to make configuration changes per service.
Change-Id: Ia59daa9859c22e4ff5e601528a63331d2eef93cf
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Simplify things by only passing the zuul.conf file, not a template.
If users need more dynamic options, they are free to template the file
first then use us to copy the file in place.
Change-Id: Ibd599b3ece707682eff9650a2244c0fb092f601c
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This removes the wonky relative paths used in ansible.
Change-Id: I37cf70c919d3e0a9022b1c63352565c46be07c57
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The most I started thinking about this, the more it should be in an
external project. We've exposed everything the user needs to override
the default settings and reload zuul.
Change-Id: I3b7c08f1511100ccbf50ba1eb8fd7dd220c9eab4
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Both server and merger should properly load on first-boot now. Also
drop logging to syslog, since we have logging setup.
Change-Id: I59cc2ade3ce81736f70d4dd7f0bf49d1d2a4f933
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This will allow a user to override our settings, additional we now
have unit tests for code coverage.
Change-Id: I5a10bc09dc1de941af89c11314c32c31a7890434
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Paul Belanger