Zuul is publishing lovely container images, so we should
go ahead and start using them.
We can't use containers for zuul-executor because of the
docker->bubblewrap->AFS issue, so install from pip there.
Don't start any of the containers by default, which should
let us safely roll this out and then do a rolling restart.
For things (like web or mergers) where it's safe to do so,
a followup change will swap the flag.
Change-Id: I37dcce3a67477ad3b2c36f2fd3657af18bc25c40
We need to wrap the hostnames/ips with []s and supply the port numbers
for the files to be effective with paramiko.
Change-Id: Iab12951a828b7c27ef2255137a6bc0b69ca3a770
This adds a connection to the opendaylight Gerrit server to zuul
so that we can perform cross-community testing.
Change-Id: I846983e873072c2235a4c49e36f602a47d06cfce
Apply the review.o.o ssh rsa host key to all of our active zuul servers.
Update the ip addresses in that host key entry to reflect the current
server's IP addrs too.
Change-Id: I147ff0b9547f2cee36d7c56c8f5352ece8a4ec82
This reverts commit c7bb14bba6.
SSH connectivity isn't quite working yet. Revert until we can get that
sorted out.
Change-Id: If2a88a61ed592f927980c71486ed0b7e3cb848d0
This adds a connection to the opendaylight Gerrit server to zuul
so that we can perform cross-community testing.
Change-Id: I840b24ebe52c50840180f2dda40a3f8669baa347
This is needed for our zuulv3 effort durning the atlanta PTG event. We
don't expect this server to be moved into production at this time.
Currently, we are missing zuul-launcher and zuul-scheduler support, which
will be added in a follow up patch.
Change-Id: I97a3ffd168679562edd2f89c572c185d94b44255
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This should be setup in site.pp, like all our other nodes.
Change-Id: I790f59d870ac70340bc43b9ebf53f6ce93fd5f46
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This patch takes part of the smooth shift of log
configuration files from system-config to puppet-zuul.
Here we remove the usage of manage_log_conf to true as
the patch this one depends on set the feature flag
as true by default. This removes useless redundancy.
This patch should be marged after Iae1e8329373463b332bf1452ec05187d8fda20e3
has been validated and merged.
Change-Id: I6693244d54d44b3f1044ff6a9016184e5b8af4ec
Depends-on: Iae1e8329373463b332bf1452ec05187d8fda20e3
gearman-logging.conf, logging.conf and merger-logging.conf
has been moved in puppet-zuul modules in:
I76851c8672968a7581622cac8ff0062c1f50e0ef
The patch this one depends on adds a feature flag (by default set
to false) that can activate the installation of these configuration
files.
This patch removes the configuration files and set the
feature flag to true in order to let puppet-zuul manage
the configuration files by itself.
Two follow up patches will then be created (once this one is merged)
in order to set the feature flag (in puppet-zuul) at true by default
and another one on system-config to remove "manage_log_conf => true".
Change-Id: Ic5ceb7fb23a8403a31f9db2774ddd900fd838930
Depends-On: I76851c8672968a7581622cac8ff0062c1f50e0ef
The following items were missing from an automated zuul install:
* A pre-populated known hosts file
* The git user/email for creating commits (.gitconfig existed
on zuul.o.o, but switch to using zuul's config file instead).
Also, make sure that the mergers specify the zuul server as the
gearman server address rather than localhost.
Change-Id: I47a473f60c4b5b2daaa910aa61cdf6e0c6fe1528
Remove obsolete config options from zuul module.
The server and merger classes are constructed so that they
may coexist on a single server. Also, the init section is
constructed so that it will install everything needed for
both services but without activating them (leaving maximum
flexibility for the operator).
Change-Id: I7b86fbbe4611c5edfb463a0a6944e0717f664188
Monty Taylor