8:37 p.m.
Hi,
As discussed during the RDO meeting today, we want to migrate the DLRN builder instance to
the RDO Cloud next week. This migration will give us higher performance for builds, and
also tighter integration of the different components inside the RDO Cloud.
The plan is outlined in [1], and it will involve a one-by-one migration of each of the
workers.
We are planning to start the migration on August 16. About the impact:
- No new builds will happen while the worker repos are rsynced to the new server (that can
be a few hours). Repos will always remain available via trunk.rdoproject.org.
- The DNS entry for trunk-primary.rdoproject.org will be moved, we need to make sure jobs
using it do not use the old IP address, and work fine after the migration.
If you have any question, please do not hesitate to contact me.
Regards,
Javier
[1] - https://review.rdoproject.org/etherpad/p/DLRN-builder-migration
9:36 a.m.
rdo-list-bounces(a)redhat.com wrote on 08/09/2017 08:37:45 PM:
As discussed during the RDO meeting today, we want to migrate the
DLRN builder instance to the RDO Cloud next week. This migration
will give us higher performance for builds, and also tighter
integration of the different components inside the RDO Cloud.
The plan is outlined in [1], and it will involve a one-by-one
migration of each of the workers.
Are there any plans for ppc64le builders? I can help with tech support
or grunt work...
2:16 a.m.
2017-08-10 16:36 GMT+02:00 Mark Hamzy <hamzy(a)us.ibm.com>:
rdo-list-bounces(a)redhat.com wrote on 08/09/2017 08:37:45 PM:
> As discussed during the RDO meeting today, we want to migrate the
> DLRN builder instance to the RDO Cloud next week. This migration
> will give us higher performance for builds, and also tighter
> integration of the different components inside the RDO Cloud.
>
> The plan is outlined in [1], and it will involve a one-by-one
> migration of each of the workers.
Are there any plans for ppc64le builders? I can help with tech support
or grunt work...
Nope, DLRN instances only builds OpenStack components which are
mostly noarch (there are few exceptions), since we didn't have the
hardware anyway, it was considered not to be a priority.
IMHO, having CI running on ppc64le would bring more immediate benefis.
We can always revisit that, though.
Regards,
H.
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
8:56 a.m.
On Fri, Aug 11, 2017 at 3:16 AM, Haïkel <hguemar(a)fedoraproject.org> wrote:
2017-08-10 16:36 GMT+02:00 Mark Hamzy <hamzy(a)us.ibm.com>:
> rdo-list-bounces(a)redhat.com wrote on 08/09/2017 08:37:45 PM:
>
>> As discussed during the RDO meeting today, we want to migrate the
>> DLRN builder instance to the RDO Cloud next week. This migration
>> will give us higher performance for builds, and also tighter
>> integration of the different components inside the RDO Cloud.
>>
>> The plan is outlined in [1], and it will involve a one-by-one
>> migration of each of the workers.
>
> Are there any plans for ppc64le builders? I can help with tech support
> or grunt work...
>
Nope, DLRN instances only builds OpenStack components which are
mostly noarch (there are few exceptions), since we didn't have the
hardware anyway, it was considered not to be a priority.
IMHO, having CI running on ppc64le would bring more immediate benefis.
We have machines in CentOS CI now, so that should be possible. Though
I thought DLRN was the repository that CI used, so that seems like we
have a chicken/egg scenario if there is no DLRN repo that includes
ppc64le?
This is likely a dumb question because my understandings of the RDO
bits and pieces and workflow are really limited. If there are docs
that outline this, feel free to point me (and probably Mark and other
newbies) to them. If not, could you explain briefly?
josh
2656
days inactive
2657
days old
3 comments
4 participants
participants (4)
-
Haïkel -
Javier Pena -
Josh Boyer -
Mark Hamzy