Seems we missed these in our previous commit.
Change-Id: I630d02e45f0a17cd6f5886fcf9a971a8264ebf10
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
To avoid confusion with nodepool-launcher, we've decided to rename
zuul-launcher to zuul-executor.
Change-Id: I7d03cf0f0093400f4ba2e4beb1c92694224a3e8c
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The zuul v3 architecture does not require that this be supported
as an internal special case. Remove it for now in the expectation
that we will implement similar functionality using the auth system
and Ansible roles.
Change-Id: I9c1e05a716ce8cfb5f66c4688db110c320d33b4b
We need a way to configure zuul to connect to zookeeper. Add a new
setting into the zuul section of zuul.conf. Multiple zookeeper hosts
would be configured as:
[zuul]
zookeeper_hosts=nodepool.openstack.org:2181,foo.openstack.org:1337
Change-Id: I4640c4af5ba925e099978b64c59ed29d723b1230
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Now that we are calling this daemon 'zuul-scheduler' we should default
its pid path to /var/run/zuul-scheduler/zuul-scheduler.pid.
Change-Id: I4dd263dc34def5b41a926cf5248f7cc35b3c5d9f
The layout option no longer makes much sense since config repos are
where layouts come from now. The -t option is still useful for testing
the static config, and may one day be expanded to fully load all config
repos and test them.
There were also chunks left in the scheduler from the old way.
Change-Id: I0a0b521b3ed20762e1cd60a042daa1f8c4f57a65
Paul Belanger