[rdo-list] Updated mitaka stable images for tripleo

[Wesley Hayutin]

We would need to setup yet another pipeline.  I can go after that if there
is a need and it sounds like there is.  I'll reduce the cadence on some of
the other jobs to compensate.

We are already chewing up quite a bit of the ci.centos.org infra,  KB we
may need to sync up regarding storage and network bandwidth.

I'll wait for KB's ack before proceeding.

Thanks

Sent from my mobile

On Aug 18, 2016 05:05, "Graeme Gillies" <ggillies at redhat.com> wrote:

On 18/08/16 18:45, Haïkel wrote:
> 2016-08-18 9:42 GMT+02:00 Graeme Gillies <ggillies at redhat.com>:
>> On 18/08/16 17:14, Haïkel wrote:
>>> 2016-08-18 6:06 GMT+02:00 Hugh Brock <hbrock at redhat.com>:
>>>> On Aug 18, 2016 5:48 AM, "Graeme Gillies" <ggillies at redhat.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> In a follow up to my previous post about image building in
tripleo/RDO,
>>>>> do we currently have a timeline, process, or anything else regarding
>>>>> when rebuilt tripleo images are rebuilt and uploaded to
>>>>> buildlogs.centos.org? E.g. if you look at the mitaka images
>>>>>
>>>>>
>>>>> http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_
images/mitaka/cbs/
>>>>>
>>>>> They were built back in April. Can we get something in place to have
>>>>> them updated more frequently?
>>>>>
>>>
>>> https://ci.centos.org/artifacts/rdo/images/
>>
>> If you look under the mitaka directory at this link, you will notice the
>> only directory there is delorean.
>>
>> I'm not talking about delorean, I'm not interested in that. I'm
>> interested in images built using the package manifests from
>> centos-release-openstack-mitaka and its dependencies (Ceph, qemu-ev,
etc).
>>
>> The images at the link I gave originally are images that were built with
>> those CBS, non-delorean, repos
>>
>> Regards,
>>
>> Graeme
>>
>
> The thing is there's no automation to periodically rebuild and test
> those images.
>
> Regards,
> H.

Ok no problem, now we have identified that, how can we go about getting
some automation to do this? It would ideally happen everytime we ship a
new package in those official channels, but failing, that, could we do
this periodically?

Regards,

Graeme

>
>>>
>>>>> Regards,
>>>>>
>>>>> Graeme
>>>>>
>>>>> --
>>>>> Graeme Gillies
>>>>> Principal Systems Administrator
>>>>> Openstack Infrastructure
>>>>> Red Hat Australia
>>>>>
>>>>> _______________________________________________
>>>>> rdo-list mailing list
>>>>> rdo-list at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/rdo-list
>>>>>
>>>>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>>>
>>>> Graeme thanks for raising this.
>>>>
>>>> RDO folks, should we not be building images every time we promote? If
we are
>>>> doing that, should we not be linking them more obviously?
>>>>
>>>> -Hugh
>>>>
>>>
>>> Seems like sync is broken.
>>>
>>> @KB; maybe, I'm missing some context but since John is in PTO, can you
>>> look at it?
>>> https://bugs.centos.org/view.php?id=10697
>>>
>>> Regards,
>>> H.
>>>
>>>>
>>>> _______________________________________________
>>>> rdo-list mailing list
>>>> rdo-list at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/rdo-list
>>>>
>>>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>
>>
>> --
>> Graeme Gillies
>> Principal Systems Administrator
>> Openstack Infrastructure
>> Red Hat Australia


--
Graeme Gillies
Principal Systems Administrator
Openstack Infrastructure
Red Hat Australia

_______________________________________________
rdo-list mailing list
rdo-list at redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list

To unsubscribe: rdo-list-unsubscribe at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160819/c3dff551/attachment.html>