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

John Trowbridge trown at redhat.com
Fri Dec 15 19:33:04 UTC 2017

On Fri, Dec 15, 2017 at 1:15 PM, Ben Nemec <openstack at nemebean.com> wrote:

> On 12/15/2017 10:26 AM, Emilien Macchi wrote:
>> 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:
>> http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23op
>> enstack-tc.2017-12-15.log.html#t2017-12-15T15:37:59
>> 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:
>> https://review.openstack.org/#/c/525743
>> I'll let the TripleO CI team to confirm that, no, you don't need RDO
>> Cloud access.
> /me makes yet another note to try OVB against a public cloud
> At the moment, at least for the OVB jobs, you pretty much do need access
> to either RDO cloud or rh1/2.  It _may_ work against some public clouds,
> but I don't know of anyone trying it yet so I can't really recommend it.

Ah right, didnt think about the OVB part. That has nothing to do with the
reproducer script though... It is just not possible to reproduce OVB jobs
against a non-OVB cloud. The multinode jobs will work against any cloud

>> 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-qu
>> eens-deployment/
>> The event is announced on RDO users mailing list:
>> https://lists.rdoproject.org/pipermail/users/2017-December/000079.html
>> 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.
> I am aware of a few people who have been rejected for RDO cloud access,
> and given the capacity constraints it is currently under I suspect there
> would need to be strong justification for new users.  I'm _not_ an RDO
> cloud admin though, so that's not an official statement of any kind.
> Also note that the test day is not happening on RDO cloud, but on a
> separate single node cloud (per https://etherpad.openstack.org
> /p/rdo-queens-m2-cloud).  It would not be particularly well suited to
> reproducing CI and presumably won't be around for long.
> So the story's not great right now unless you already have access to cloud
> resources.  The developer hardware requirements problem is not quite solved
> yet. :-/
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171215/c5fa7402/attachment.html>

More information about the OpenStack-dev mailing list