Use scenario004 as third party CI for ceph-ansible

Bug #1834189 reported by Giulio Fidente
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Unassigned

Bug Description

As discussed during Train PTG [1], it would be great to use scenario004 as third party CI for ceph-ansible upstream.

Some work has been done already to trigger jobs in RDO infra via Zuul, see [2] and [3]

1. https://etherpad.openstack.org/p/tripleo-ptg-train
2. https://review.rdoproject.org/r/#/c/18734/
3. https://github.com/ceph/ceph-ansible/pull/3576

Tags: alert ci
Changed in tripleo:
milestone: train-3 → train-2
wes hayutin (weshayutin)
tags: added: alert
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
Revision history for this message
wes hayutin (weshayutin) wrote :

work is in progress and visible here, have periodic jobs running into ceph issues atm.

http://dashboard-ci.tripleo.org/d/jiglzyLWk/third-party-dependency-check?orgId=1

Changed in tripleo:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.