I digged into the remaining and will investigate whether we can retire them:
openstack-infra/zuul-packaging
Paul, should we abandon this one as well?
openstack-infra/featuretracker (together with puppet-featuretracker)
these work together with openstack/development-proposals from the
pro
On 2018-08-28 23:50, Clark Boylan wrote:
> [...]
I think these repos can definitely be retired:
# Was part of bitergia work with openstack which is no longer done
openstack-infra/activity-board
# These may have been attempts at having puppet beaker testing play nice with
our CI but we hacked a
All of the patches to import the zuul settings into these repositories
are approved and we are ready to proceed with
https://review.openstack.org/#/c/592970/
On Fri, Aug 17, 2018 at 9:20 PM Nguyễn Trí Hải
wrote:
> The Zuul project settings for the congress repositories
> has begun. Please do not
On 2018-08-28 14:50:40 -0700 (-0700), Clark Boylan wrote:
[...]
> # Project to provide alternate Gerrit UI that never got commits
> openstack-infra/puppet-vinz
> openstack-infra/vinz
> openstack-infra/vinz-webclient
[...]
As an aside, if we ever decide to rename nodepool, recycling this
name gets
On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote:
> A quick search with codesearch suggests that these can be retired since
> I couldn't find a user:
>
> openstack-infra/activity-board
> openstack-infra/beaker-localhost
> openstack-infra/beaker-nodepool
> openstack-infra/err2d2
> openstack
The migration of Zuul project settings for the
heat repositories has begun.
Please do not approve any changes to
openstack-infra/project-config/zuul.d/projects.yaml
for the following repositories:
- openstack-dev/heat-cfnclient
- openstack/heat
- openstack/heat-agents
- openstack/heat-cfntools
- o
Excerpts from Doug Hellmann's message of 2018-08-06 11:54:35 -0400:
> The Zuul project settings for the Oslo repositories
> has begun. Please do not approve any changes to
> openstack-infra/project-config/zuul.d/projects.yaml for
> the following repositories:
>
> - openstack-dev/cookiecutter
> - o
Ian Wienand writes:
> On 08/28/2018 09:48 AM, Clark Boylan wrote:
>> On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote:
>> One quick new observation. launch-node.py does not install puppet at
>> all so the subsequent ansible runs on the newly launched instances
>> will fail when attempting to
On 08/28/2018 09:48 AM, Clark Boylan wrote:
On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote:
One quick new observation. launch-node.py does not install puppet at
all so the subsequent ansible runs on the newly launched instances
will fail when attempting to stop the puppet service (and will
