Re: [openstack-dev] [tripleo] Migrating TripleO CI in-tree tomorrow - please README

2017-11-19 Thread Emilien Macchi 
Quick update - our plan worked quite well.

https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3

Here's what has been done:
- Migrate most of TripleO projects to zuul layout in-tree + backports
to stable branches.
- Some projects have broken gate and I plan to take a look on Monday -
any help is welcome.
- I pushed patches in OpenStack projects where TripleO jobs were
running, waiting for review.
- Alex and I made scenario001 and 003 non voting due to instabilities.
We really need help on these ones (see alerts on #tripleo).

Next steps:
- Fix gate issue to merge the rest of zuulv3 migration patches
- Start planning work to convert legacy playbooks into proper Ansible
tasks, and re-using quickstart modules.

If you notice any issue or strange thing please let us know.
Thanks,

On Fri, Nov 17, 2017 at 7:18 AM, Alex Schultz  wrote:
> On Thu, Nov 16, 2017 at 11:20 AM, Emilien Macchi  wrote:
>> TL;DR: don't approve or recheck any tripleo patch from now, until
>> further notice on this thread.
>>
>> Some good progress has been made on migrating legacy tripleo CI jobs
>> to be in-tree:
>> https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3
>>
>> The next steps:
>> - Let the current gate to finish their jobs running.
>> - Stop approving patches from now, and wait the gate to be done and cleared
>> - Alex and I will approve the migration patches tomorrow and we hope
>> to have them in the gate by Friday afternoon (US time) when gate isn't
>> busy anymore. We'll also have to backport them all.
>
> They have been pushed to the gate. There are a few patches in front of
> them before they will hit. please do not approve anything until the v3
> cut over lands as you'll end up with double the amount of jobs running
> on your gate patches until the project-config change lands.
>
> Thanks,
> -Alex
>
>
>> - When these patches will be merged (it might take the weekend to
>> land, depending how the gate will be), we'll run duplicated jobs until
>> https://review.openstack.org/514778 is merged. I'll try to ping
>> someone from Infra over the week-end if we can land it, that would be
>> great.
>> - Once https://review.openstack.org/514778 is merged, people are free
>> to do recheck or approve any patches. We hope it should happen over
>> the weekend.
>> - I'll continue to migrate all other tripleo projects to have in-tree
>> layout. On the list: t-p-e, t-i-e, paunch, os-*-config,
>> tripleo-validations.
>>
>> Thanks for your help,
>> --
>> Emilien Macchi
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Migrating TripleO CI in-tree tomorrow - please README

2017-11-17 Thread Alex Schultz 
On Thu, Nov 16, 2017 at 11:20 AM, Emilien Macchi  wrote:
> TL;DR: don't approve or recheck any tripleo patch from now, until
> further notice on this thread.
>
> Some good progress has been made on migrating legacy tripleo CI jobs
> to be in-tree:
> https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3
>
> The next steps:
> - Let the current gate to finish their jobs running.
> - Stop approving patches from now, and wait the gate to be done and cleared
> - Alex and I will approve the migration patches tomorrow and we hope
> to have them in the gate by Friday afternoon (US time) when gate isn't
> busy anymore. We'll also have to backport them all.

They have been pushed to the gate. There are a few patches in front of
them before they will hit. please do not approve anything until the v3
cut over lands as you'll end up with double the amount of jobs running
on your gate patches until the project-config change lands.

Thanks,
-Alex


> - When these patches will be merged (it might take the weekend to
> land, depending how the gate will be), we'll run duplicated jobs until
> https://review.openstack.org/514778 is merged. I'll try to ping
> someone from Infra over the week-end if we can land it, that would be
> great.
> - Once https://review.openstack.org/514778 is merged, people are free
> to do recheck or approve any patches. We hope it should happen over
> the weekend.
> - I'll continue to migrate all other tripleo projects to have in-tree
> layout. On the list: t-p-e, t-i-e, paunch, os-*-config,
> tripleo-validations.
>
> Thanks for your help,
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] Migrating TripleO CI in-tree tomorrow - please README

2017-11-17 Thread Bogdan Dobrelya 

On 11/16/17 7:20 PM, Emilien Macchi wrote:

TL;DR: don't approve or recheck any tripleo patch from now, until
further notice on this thread.

Some good progress has been made on migrating legacy tripleo CI jobs
to be in-tree:
https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3

The next steps:
- Let the current gate to finish their jobs running.
- Stop approving patches from now, and wait the gate to be done and cleared
- Alex and I will approve the migration patches tomorrow and we hope
to have them in the gate by Friday afternoon (US time) when gate isn't
busy anymore. We'll also have to backport them all.
- When these patches will be merged (it might take the weekend to
land, depending how the gate will be), we'll run duplicated jobs until
https://review.openstack.org/514778 is merged. I'll try to ping
someone from Infra over the week-end if we can land it, that would be
great.
- Once https://review.openstack.org/514778 is merged, people are free
to do recheck or approve any patches. We hope it should happen over
the weekend.
- I'll continue to migrate all other tripleo projects to have in-tree
layout. On the list: t-p-e, t-i-e, paunch, os-*-config,
tripleo-validations.

Thanks for your help,



Thank you for working on this Emilien! That's well done, and provides a 
good example for future use in other projects as well.


--
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Migrating TripleO CI in-tree tomorrow - please README

2017-11-16 Thread Emilien Macchi 
TL;DR: don't approve or recheck any tripleo patch from now, until
further notice on this thread.

Some good progress has been made on migrating legacy tripleo CI jobs
to be in-tree:
https://review.openstack.org/#/q/topic:tripleo/migrate-to-zuulv3

The next steps:
- Let the current gate to finish their jobs running.
- Stop approving patches from now, and wait the gate to be done and cleared
- Alex and I will approve the migration patches tomorrow and we hope
to have them in the gate by Friday afternoon (US time) when gate isn't
busy anymore. We'll also have to backport them all.
- When these patches will be merged (it might take the weekend to
land, depending how the gate will be), we'll run duplicated jobs until
https://review.openstack.org/514778 is merged. I'll try to ping
someone from Infra over the week-end if we can land it, that would be
great.
- Once https://review.openstack.org/514778 is merged, people are free
to do recheck or approve any patches. We hope it should happen over
the weekend.
- I'll continue to migrate all other tripleo projects to have in-tree
layout. On the list: t-p-e, t-i-e, paunch, os-*-config,
tripleo-validations.

Thanks for your help,
-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev