Currently elasticsearch fuel ccp plugin is
placed in fuel-ccp-stacklight repository, but
needed not only by stacklight repo, but also for
fuel-ccp-searchlight deployment repo. So, for safer
usage elasticsearch.
Change-Id: I0f5209d08bdafde4829d958dc02b8c43fecf6dde
Since the nodepool builders are trusty, we have this as a target
platform. Unfortunately we were not testing trusty on feature/v2. I
went to merge that branch back into master thinking it was ready, and
guess what doesn't work :)
Change-Id: Ic32990c7e4d9191b4551874e79be7e92b8148d0e
The suffix was added to most jobs, but some trends were still using job
names without it, which made the trends vanish from dashboards due to no
events to track.
Change-Id: I409189807d66ee5a886f3f1b6bf247a22bcc2ab1
Optimize the zuul layout to run tirpleo upgrade jobs only when touching
the right files, like other scenarios.
Change-Id: I7e49a3926e95ce0250083400e10c7a48b58864ef
The job was broken twice in the course of last two weeks (once by
local.conf loading strategy changed in d-g; now by incorrectly calling
testr slowest in the job).
And it's not surprising, since the job uses neutron gate_hook that is
very complex and relies on DEVSTACK_LOCALCONF, dsconf, and other gate
configuration features that may be not utilized in current list of
gating jobs.
The job is very stable, so there should have been no concerns about
destabilizing the d-g gate. But there are still concerns about tangling
d-g gate with external consuming projects too much. We will start with a
non-voting job, and see if it is enough to make neutron gate a safer
place.
Change-Id: I54d8023e11afec858cdceeb83cd2a57febc54971
The previous patch [1] added python-manilaclient, but forgot to
do the same for py35.
[1] https://review.openstack.org/#/c/438733/
Change-Id: I8e3fcb8d4719a5539898253801af15a2aa5b068a
This patch moves the undercloud-containers job from the
experimental "undercloud" jobs into experimental tripleo
jobs.
Moving this job into the tripleo-jobs again since the
architecture more closely align's with TripleO than
instack.
Change-Id: I1dcac878f30af5f3581ae6ca974d7d66b191b528
The project last developed branch has been mitaka. It is time
to retire it.
http://lists.openstack.org/pipermail/openstack-dev/2017-March/113325.html
Needed-by: I86862c9896e516cf5ae94d3bd7e05610a8bc51a1
Needed-by: I2291725c93088584ce4e75e383a4f5884f5635f8
Change-Id: Ie5e889812ec0df391340bb49baa2dec2496dc9e2
This was a place holder for testing at the PTG. We can remove this
now since we have landed a zuulv3 job in openstack-infra/zuul.
Change-Id: I639e416f98ffd515469832db157efa174a15caac
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Fix the case when someone submit a patch in README file for
puppet-openstack-integration project. Right now, no job is run. With
this patch, puppet-lint will be run which is something that we want.
Change-Id: I9cf38a769943e71795f3633a6fa13e3322ad0026
OSIC appears to not be able to create nodes right now, pull it from
the pool to let patch merges flow again.
Change-Id: Ia14b53b9e0ccd3b2e0ba97b0b6d156f4dea96fe4
The ec2 profile is deploying in scenario002, so we should run it when
there's changes to its relevant files.
Change-Id: If5295da7cc955a47709939d00a0dc0cc89ded11a