[openstack-dev] [tripleo] TripleO CI end of sprint status

Emilien Macchi emilien at redhat.com
Fri Dec 15 16:26:56 UTC 2017

On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz <arxcruz at redhat.com> wrote:
> The goal on this sprint was to enable into quickstart a way to reproduce
> upstream jobs, in your personal RDO cloud tenant, making easy to developers
> to debug and reproduce their code.

This phrase confused some non-Red-Hat OpenStack contributors on #openstack-tc:

2 questions came up:

1) Do we need RDO Cloud access to reproduce TripleO CI jobs?

I think the answer is no. What you need though is an OpenStack cloud,
with the work that is being done here:

I'll let the TripleO CI team to confirm that, no, you don't need RDO
Cloud access.

2) Can anyone have access to RDO Cloud resources?

One of the reasons of creating RDO Cloud was for developers so they
can get resources to build OpenStack.
RDO community organizes something called "test days", where anyone is
welcome to join and test OpenStack on centos7 with RDO packages.
See: https://dmsimard.com/2017/11/29/come-try-a-real-openstack-queens-deployment/
The event is announced on RDO users mailing list:
Other than that, I'm not sure about the process if someone needs
full-time access. FWIW, I never saw any rejection in the past. We
welcome contributors and we want to help how we can.

Any feedback is welcome to improve our transparency and inclusiveness.


Emilien Macchi

More information about the OpenStack-dev mailing list