8:03 a.m.
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories
on CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
TripleO CI, etc...) have been working to switch to CentOS8 during last few
weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
CentOS 8/Python 3. As OpenStack projects have been dropping support for P
ython 2, we've started pinning them to the last commit working with
Python 2[1],
we were expecting that transition will finish soon but it's still going on.
Over time, the number of pinned packages has been growing including
services and Oslo libraries where we can't follow upper-constraints anymore
[2]. Recently, Kolla has removed support for CentOS 7 so i doubt it makes
sense to keep pinning packages to keep RDO Trunk consistent artificially
and continue running promotion pipelines on a repo with so many outdated
packages. Also, pinning these projects makes that changes needed for CentOS
8 will not be in RDO and would need to be backported manually to each
package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in upper
-constraints (for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so no
more promotions based on it).
- We will keep running centos7-master DLRN builder, so that packages still
builing with Python 2 will be available in current repo [3] to be used by
teams needing them until migration to CentOS 8 is finished everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can
remove CentOS 7 ones.
We understand this can add some pressure on moving to CentOS8 to the teams
working on it, but I'd say it's already a priority and it's justified at
this stage.
What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to
CentOS 8?
Best regards,
Alfredo
[1] https://review.rdoproject.org/r/#/q/topic:pin-py2
[2] https://review.rdoproject.org/r/#/c/24796/
[3] http://trunk.rdoproject.org/centos7-master/current
12:51 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
So, if I understand this right...
* We're keeping the centos7 and centos8 versions of Ussuri consistent
* There is no actual build of the latest commits built on either centos7 or
centos8
* There is no possible way to have an Ussuri release on Centos7
Assuming the above is true, I would say to turn off all the centos7 stuff
and focus all effort on getting Ussuri latest built on centos8. There does
not appear to be any value in continuing work on centos7 if we can't
actually deliver it at the end of the day.
Mike
On Thu, Feb 20, 2020 at 9:05 AM Alfredo Moralejo Alonso <amoralej(a)redhat.com>
wrote:
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories
on CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
TripleO CI, etc...) have been working to switch to CentOS8 during last few
weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
CentOS 8/Python 3. As OpenStack projects have been dropping support for P
ython 2, we've started pinning them to the last commit working with Python
2[1], we were expecting that transition will finish soon but it's still
going on. Over time, the number of pinned packages has been growing
including services and Oslo libraries where we can't follow
upper-constraints anymore[2]. Recently, Kolla has removed support for
CentOS 7 so i doubt it makes sense to keep pinning packages to keep RDO
Trunk consistent artificially and continue running promotion pipelines on a
repo with so many outdated packages. Also, pinning these projects makes
that changes needed for CentOS 8 will not be in RDO and would need to be
backported manually to each package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in u
pper-constraints (for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
no more promotions based on it).
- We will keep running centos7-master DLRN builder, so that packages
still builing with Python 2 will be available in current repo [3] to be
used by teams needing them until migration to CentOS 8 is finished
everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can
remove CentOS 7 ones.
We understand this can add some pressure on moving to CentOS8 to the teams
working on it, but I'd say it's already a priority and it's justified at
this stage.
What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to
CentOS 8?
Best regards,
Alfredo
[1] https://review.rdoproject.org/r/#/q/topic:pin-py2
[2] https://review.rdoproject.org/r/#/c/24796/
[3] http://trunk.rdoproject.org/centos7-master/current
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
1:48 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Thu, Feb 20, 2020 at 11:56 AM Mike Burns <mburns(a)redhat.com> wrote:
So, if I understand this right...
* We're keeping the centos7 and centos8 versions of Ussuri consistent
* There is no actual build of the latest commits built on either centos7
or centos8
* There is no possible way to have an Ussuri release on Centos7
Assuming the above is true, I would say to turn off all the centos7 stuff
and focus all effort on getting Ussuri latest built on centos8. There does
not appear to be any value in continuing work on centos7 if we can't
actually deliver it at the end of the day.
Mike
Agreeing and building on what Mike said.. this certainly raises the
priority on CentOS-8. There are still tripleo patches incoming that will
not be pinned ( I think )
Having a better understanding here of what has been pinned and what is in
progress w/o consulting rdo-info all the time would be handy.
I think the check, gate and promotion jobs for centos-7 ussuri need to stay
in place, however they should just always pass which would lower the amount
of work w/ regards to centos-7 but not eliminate it. It could also be the
case that tripleo breaks itself from time to time, but I'm sure Emilien
would never let that happen as he's a robot and not human.
I digress
On Thu, Feb 20, 2020 at 9:05 AM Alfredo Moralejo Alonso <
amoralej(a)redhat.com> wrote:
>
> Hi,
>
> I'd like to open a discussion about the status of RDO Ussuri
> repositories on CentOS7.
>
> As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
> TripleO CI, etc...) have been working to switch to CentOS8 during last
> few weeks.
>
> In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
> still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
> CentOS 8/Python 3. As OpenStack projects have been dropping support for P
> ython 2, we've started pinning them to the last commit working with P
> ython 2[1], we were expecting that transition will finish soon but it's
> still going on. Over time, the number of pinned packages has been
> growing including services and Oslo libraries where we can't follow
> upper-constraints anymore[2]. Recently, Kolla has removed support for
> CentOS 7 so i doubt it makes sense to keep pinning packages to keep RDO
> Trunk consistent artificially and continue running promotion pipelines on a
> repo with so many outdated packages. Also, pinning these projects makes
> that changes needed for CentOS 8 will not be in RDO and would need to be
> backported manually to each package. My proposal is:
>
> - Unpin all packages in Ussuri to follow master trunk, or versions in u
> pper-constraints (for clients and libraries).
> - RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
> no more promotions based on it).
> - We will keep running centos7-master DLRN builder, so that packages
> still builing with Python 2 will be available in current repo [3] to be
> used by teams needing them until migration to CentOS 8 is finished
> everywhere.
> - Projects which already have CentOS 8 jobs gating in master branch can
> remove CentOS 7 ones.
>
> We understand this can add some pressure on moving to CentOS8 to the
> teams working on it, but I'd say it's already a priority and it's
justified
> at this stage.
>
> What do you think about this plan?, is there any reason to keep CentOS 7
> artificially consistent and promoting at this point of the transition to
> CentOS 8?
>
> Best regards,
>
> Alfredo
>
> [1] https://review.rdoproject.org/r/#/q/topic:pin-py2
> [2] https://review.rdoproject.org/r/#/c/24796/
> [3] http://trunk.rdoproject.org/centos7-master/current
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
3:21 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
> On Thu, Feb 20, 2020 at 9:05 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
>> What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to CentOS 8?
There's a TripleO patch [1] blocked as a result. The patch enables a
new Glance feature that merged in Ussuri but we're unable to get it
tested by the TripleO CI system because we're pinned to such an old
version of Glance in the CentOS 7 container. I'm personally OK with
the plan, provided that exceptions can be requested when needed for a
project.
So in this case I'm asking for the first instance of such an
exception. Could the cent7 Glance container be updated to have a newer
version of Glance containing this change [2].
Thanks,
John
[1] https://review.opendev.org/#/q/topic:glance-multistore
[2] https://review.opendev.org/#/c/705229/
On Thu, Feb 20, 2020 at 2:49 PM Wesley Hayutin <whayutin(a)redhat.com> wrote:
On Thu, Feb 20, 2020 at 11:56 AM Mike Burns <mburns(a)redhat.com> wrote:
>
> So, if I understand this right...
>
> * We're keeping the centos7 and centos8 versions of Ussuri consistent
> * There is no actual build of the latest commits built on either centos7 or centos8
> * There is no possible way to have an Ussuri release on Centos7
>
> Assuming the above is true, I would say to turn off all the centos7 stuff and focus
all effort on getting Ussuri latest built on centos8. There does not appear to be any
value in continuing work on centos7 if we can't actually deliver it at the end of the
day.
>
> Mike
Agreeing and building on what Mike said.. this certainly raises the priority on CentOS-8.
There are still tripleo patches incoming that will not be pinned ( I think )
Having a better understanding here of what has been pinned and what is in progress w/o
consulting rdo-info all the time would be handy.
I think the check, gate and promotion jobs for centos-7 ussuri need to stay in place,
however they should just always pass which would lower the amount of work w/ regards to
centos-7 but not eliminate it. It could also be the case that tripleo breaks itself from
time to time, but I'm sure Emilien would never let that happen as he's a robot and
not human.
I digress
>
>
> On Thu, Feb 20, 2020 at 9:05 AM Alfredo Moralejo Alonso <amoralej(a)redhat.com>
wrote:
>>
>>
>> Hi,
>>
>> I'd like to open a discussion about the status of RDO Ussuri repositories on
CentOS7.
>>
>> As you know RDO and upstream teams (kolla, puppet-openstack, TripleO, TripleO CI,
etc...) have been working to switch to CentOS8 during last few weeks.
>>
>> In order to make the transition easier from CentOS 7 to CentOS 8, RDO is still
maintaining Trunk repos consistent for both CentOS 7/Python 2 and CentOS 8/Python 3. As
OpenStack projects have been dropping support for Python 2, we've started pinning them
to the last commit working with Python 2[1], we were expecting that transition will finish
soon but it's still going on. Over time, the number of pinned packages has been
growing including services and Oslo libraries where we can't follow upper-constraints
anymore[2]. Recently, Kolla has removed support for CentOS 7 so i doubt it makes sense to
keep pinning packages to keep RDO Trunk consistent artificially and continue running
promotion pipelines on a repo with so many outdated packages. Also, pinning these projects
makes that changes needed for CentOS 8 will not be in RDO and would need to be backported
manually to each package. My proposal is:
>>
>> - Unpin all packages in Ussuri to follow master trunk, or versions in
upper-constraints (for clients and libraries).
>> - RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so no more
promotions based on it).
>> - We will keep running centos7-master DLRN builder, so that packages still
builing with Python 2 will be available in current repo [3] to be used by teams needing
them until migration to CentOS 8 is finished everywhere.
>> - Projects which already have CentOS 8 jobs gating in master branch can remove
CentOS 7 ones.
>>
>> We understand this can add some pressure on moving to CentOS8 to the teams
working on it, but I'd say it's already a priority and it's justified at this
stage.
>>
>> What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to CentOS 8?
>>
>> Best regards,
>>
>> Alfredo
>>
>> [1] https://review.rdoproject.org/r/#/q/topic:pin-py2
>> [2] https://review.rdoproject.org/r/#/c/24796/
>> [3] http://trunk.rdoproject.org/centos7-master/current
>> _______________________________________________
>> dev mailing list
>> dev(a)lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/dev
>>
>> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
_______________________________________________
users mailing list
users(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
4:26 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
So in this case I'm asking for the first instance of such an
exception. Could the cent7 Glance container be updated to have a newer
version of Glance containing this change [2].
[1] https://review.opendev.org/#/q/topic:glance-multistore
[2] https://review.opendev.org/#/c/705229/
In this specific case, it might work, please propose update of the
Glance pin in rdoinfo tags/ussuri-uc.yml
Glance was pinned in https://review.rdoproject.org/r/24257 with the
link to an upstream commit which maybe broke py2 at that time but
upstream py2 compatibility seems to have been fixed in the meantime,
latest centos7-master-head trunk build worked:
https://trunk.rdoproject.org/centos7-master-head/24/56/2456c7d0000e8e3900...
This will not work in general and is not sustainable, after upstream
drops py2 test coverage, py2 incompatibility can be introduced at any
time!
Cheers,
Alan
1:41 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
Glance was pinned in https://review.rdoproject.org/r/24257 with the
link to an upstream commit which maybe broke py2 at that time
looking closer, this was not py2 breakage, it was due to failing tests
in puppet-openstack-integration after native SSL support was
completely removed in Glance https://review.opendev.org/697969
Yatin, in https://review.opendev.org/625613 in the series
https://review.opendev.org/#/q/topic:py3-enable SSL was disabled for
py3 in RHEL > 7, should we just disable it for all cases now?
Cheers,
Alan
3:20 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Fri, Feb 21, 2020 at 8:42 AM Alan Pevec <apevec(a)redhat.com> wrote:
> Glance was pinned in https://review.rdoproject.org/r/24257 with
the
> link to an upstream commit which maybe broke py2 at that time
looking closer, this was not py2 breakage, it was due to failing tests
in puppet-openstack-integration after native SSL support was
completely removed in Glance https://review.opendev.org/697969
Yatin, in https://review.opendev.org/625613 in the series
https://review.opendev.org/#/q/topic:py3-enable SSL was disabled for
py3 in RHEL > 7, should we just disable it for all cases now?
For the particular glance case, i propose:
- Make centos7-master consistent again [1]
- unpin glance [2]
- Disable ssl in CentOS7 in p-o-i (although irrelevant for tripleo
promotions, i'd like to get it in puppet promotions jobs also for
consistency).
With this, next promotion jobs should get updated glance in containers and
hopefully promote them so they are available in chek jobs to gate tripleo
reviews.
I'd hope this to be the last consistent status and start unpinning the rest
of packages, after getting glance update in.
Will this work?
Alfredo
[1] https://review.rdoproject.org/r/#/c/25100/
[2] https://review.rdoproject.org/r/#/c/25135/
Cheers,
Alan
_______________________________________________
users mailing list
users(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
6:52 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Fri, Feb 21, 2020 at 4:21 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
On Fri, Feb 21, 2020 at 8:42 AM Alan Pevec <apevec(a)redhat.com> wrote:
>
> > Glance was pinned in https://review.rdoproject.org/r/24257 with the
> > link to an upstream commit which maybe broke py2 at that time
>
> looking closer, this was not py2 breakage, it was due to failing tests
> in puppet-openstack-integration after native SSL support was
> completely removed in Glance https://review.opendev.org/697969
>
> Yatin, in https://review.opendev.org/625613 in the series
> https://review.opendev.org/#/q/topic:py3-enable SSL was disabled for
> py3 in RHEL > 7, should we just disable it for all cases now?
>
For the particular glance case, i propose:
- Make centos7-master consistent again [1]
- unpin glance [2]
- Disable ssl in CentOS7 in p-o-i (although irrelevant for tripleo promotions, i'd
like to get it in puppet promotions jobs also for consistency).
With this, next promotion jobs should get updated glance in containers and hopefully
promote them so they are available in chek jobs to gate tripleo reviews.
I'd hope this to be the last consistent status and start unpinning the rest of
packages, after getting glance update in.
Will this work?
Sounds good to me. Thank you Alfredo. --John
Alfredo
[1] https://review.rdoproject.org/r/#/c/25100/
[2] https://review.rdoproject.org/r/#/c/25135/
>
> Cheers,
> Alan
>
> _______________________________________________
> users mailing list
> users(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/users
>
> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
>
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
7:09 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Fri, Feb 21, 2020 at 1:52 PM John Fulton <johfulto(a)redhat.com> wrote:
On Fri, Feb 21, 2020 at 4:21 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
>
>
>
> On Fri, Feb 21, 2020 at 8:42 AM Alan Pevec <apevec(a)redhat.com> wrote:
>>
>> > Glance was pinned in https://review.rdoproject.org/r/24257 with the
>> > link to an upstream commit which maybe broke py2 at that time
>>
>> looking closer, this was not py2 breakage, it was due to failing tests
>> in puppet-openstack-integration after native SSL support was
>> completely removed in Glance https://review.opendev.org/697969
>>
>> Yatin, in https://review.opendev.org/625613 in the series
>> https://review.opendev.org/#/q/topic:py3-enable SSL was disabled for
>> py3 in RHEL > 7, should we just disable it for all cases now?
>>
>
> For the particular glance case, i propose:
>
> - Make centos7-master consistent again [1]
> - unpin glance [2]
> - Disable ssl in CentOS7 in p-o-i (although irrelevant for tripleo
promotions, i'd like to get it in puppet promotions jobs also for
consistency).
>
> With this, next promotion jobs should get updated glance in containers
and hopefully promote them so they are available in chek jobs to gate
tripleo reviews.
>
> I'd hope this to be the last consistent status and start unpinning the
rest of packages, after getting glance update in.
>
> Will this work?
Sounds good to me. Thank you Alfredo. --John
glance is now upate to master trunk in cntos7-master, so it should be used
in next promotion attempt.
>
> Alfredo
>
> [1] https://review.rdoproject.org/r/#/c/25100/
> [2] https://review.rdoproject.org/r/#/c/25135/
>
>
>>
>> Cheers,
>> Alan
>>
>> _______________________________________________
>> users mailing list
>> users(a)lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/users
>>
>> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
>>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
3 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Fri, Feb 21, 2020 at 1:52 PM John Fulton <johfulto(a)redhat.com> wrote:
On Fri, Feb 21, 2020 at 4:21 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
>
>
>
> On Fri, Feb 21, 2020 at 8:42 AM Alan Pevec <apevec(a)redhat.com> wrote:
>>
>> > Glance was pinned in https://review.rdoproject.org/r/24257 with the
>> > link to an upstream commit which maybe broke py2 at that time
>>
>> looking closer, this was not py2 breakage, it was due to failing tests
>> in puppet-openstack-integration after native SSL support was
>> completely removed in Glance https://review.opendev.org/697969
>>
>> Yatin, in https://review.opendev.org/625613 in the series
>> https://review.opendev.org/#/q/topic:py3-enable SSL was disabled for
>> py3 in RHEL > 7, should we just disable it for all cases now?
>>
>
> For the particular glance case, i propose:
>
> - Make centos7-master consistent again [1]
> - unpin glance [2]
> - Disable ssl in CentOS7 in p-o-i (although irrelevant for tripleo
promotions, i'd like to get it in puppet promotions jobs also for
consistency).
>
> With this, next promotion jobs should get updated glance in containers
and hopefully promote them so they are available in chek jobs to gate
tripleo reviews.
>
> I'd hope this to be the last consistent status and start unpinning the
rest of packages, after getting glance update in.
>
> Will this work?
Sounds good to me. Thank you Alfredo. --John
There has been a new tripleo promotion in centos7-master builder wich
includes glance from commit 2456c7d0000e8e3900e5812a820bbc31bc4d1cf1.
That's now available in all check/gate jobs for tripleo projects.
Alfredo
>
> Alfredo
>
> [1] https://review.rdoproject.org/r/#/c/25100/
> [2] https://review.rdoproject.org/r/#/c/25135/
>
>
>>
>> Cheers,
>> Alan
>>
>> _______________________________________________
>> users mailing list
>> users(a)lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/users
>>
>> To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
>>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
2:46 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Thu, Feb 20, 2020 at 8:49 PM Wesley Hayutin <whayutin(a)redhat.com> wrote:
On Thu, Feb 20, 2020 at 11:56 AM Mike Burns <mburns(a)redhat.com> wrote:
> So, if I understand this right...
>
> * We're keeping the centos7 and centos8 versions of Ussuri consistent
> * There is no actual build of the latest commits built on either centos7
> or centos8
> * There is no possible way to have an Ussuri release on Centos7
>
> Assuming the above is true, I would say to turn off all the centos7 stuff
> and focus all effort on getting Ussuri latest built on centos8. There does
> not appear to be any value in continuing work on centos7 if we can't
> actually deliver it at the end of the day.
>
> Mike
>
Agreeing and building on what Mike said.. this certainly raises the
priority on CentOS-8. There are still tripleo patches incoming that will
not be pinned ( I think )
Having a better understanding here of what has been pinned and what is in
progress w/o consulting rdo-info all the time would be handy.
Yes, tripleo patches are not pinned and should keep bulding in current
repo..
Currently pinned packages because of py2 issues:
- nova
- keystone
- cinder
- glance
- neutron
- neutron-lib
- neutron-vpnaas
- networking-generic-switch
- horizon
- heat-dasboard
- murano-dashboard
- octavia
- mistral
- ironic
- ironic-staging-drivers
- ironic-python-agent
- hardware
- kolla
- senlin
- tobiko
- rally
- heat-tempest-plugin
- zaqar-tempest-plugin
- mistral-tempest-plugin
Also, update of oslo-libraries to latest releases is blocked so we are
still using previous ones.
I think the check, gate and promotion jobs for centos-7 ussuri need
to
stay in place, however they should just always pass which would lower the
amount of work w/ regards to centos-7 but not eliminate it. It could also
be the case that tripleo breaks itself from time to time, but I'm sure
Emilien would never let that happen as he's a robot and not human.
There should be no problem with check jobs for c7, that will keep using
latest promoted content + current tripleo and family. TripleO patches
requiring changes in pinned projects will fail in CentOS7.
WRT promotion based on consistent link, as we get consistent link stuck by
unpinning packages to get them updated in CentOS8, i'm not sure if periodic
pipeline will keep running or it detects the link is still pointing to the
same hash and will skip it.
I digress
>
> On Thu, Feb 20, 2020 at 9:05 AM Alfredo Moralejo Alonso <
> amoralej(a)redhat.com> wrote:
>
>>
>> Hi,
>>
>> I'd like to open a discussion about the status of RDO Ussuri
>> repositories on CentOS7.
>>
>> As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
>> TripleO CI, etc...) have been working to switch to CentOS8 during last
>> few weeks.
>>
>> In order to make the transition easier from CentOS 7 to CentOS 8, RDO
>> is still maintaining Trunk repos consistent for both CentOS 7/Python 2
>> and CentOS 8/Python 3. As OpenStack projects have been dropping support
>> for Python 2, we've started pinning them to the last commit working
>> with Python 2[1], we were expecting that transition will finish soon
>> but it's still going on. Over time, the number of pinned packages has
>> been growing including services and Oslo libraries where we can't
>> follow upper-constraints anymore[2]. Recently, Kolla has removed
>> support for CentOS 7 so i doubt it makes sense to keep pinning packages
>> to keep RDO Trunk consistent artificially and continue running promotion
>> pipelines on a repo with so many outdated packages. Also, pinning these
>> projects makes that changes needed for CentOS 8 will not be in RDO and
>> would need to be backported manually to each package. My proposal is:
>>
>> - Unpin all packages in Ussuri to follow master trunk, or versions in u
>> pper-constraints (for clients and libraries).
>> - RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
>> no more promotions based on it).
>> - We will keep running centos7-master DLRN builder, so that packages
>> still builing with Python 2 will be available in current repo [3] to be
>> used by teams needing them until migration to CentOS 8 is finished
>> everywhere.
>> - Projects which already have CentOS 8 jobs gating in master branch can
>> remove CentOS 7 ones.
>>
>> We understand this can add some pressure on moving to CentOS8 to the
>> teams working on it, but I'd say it's already a priority and it's
justified
>> at this stage.
>>
>> What do you think about this plan?, is there any reason to keep CentOS 7
>> artificially consistent and promoting at this point of the transition
>> to CentOS 8?
>>
>> Best regards,
>>
>> Alfredo
>>
>> [1] https://review.rdoproject.org/r/#/q/topic:pin-py2
>> [2] https://review.rdoproject.org/r/#/c/24796/
>> [3] http://trunk.rdoproject.org/centos7-master/current
>> _______________________________________________
>> dev mailing list
>> dev(a)lists.rdoproject.org
>> http://lists.rdoproject.org/mailman/listinfo/dev
>>
>> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>
7:39 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Thu, Feb 20, 2020 at 9:04 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories on
CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO, TripleO CI, etc...)
have been working to switch to CentOS8 during last few weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is still
maintaining Trunk repos consistent for both CentOS 7/Python 2 and CentOS 8/Python 3. As
OpenStack projects have been dropping support for Python 2, we've started pinning them
to the last commit working with Python 2[1], we were expecting that transition will finish
soon but it's still going on. Over time, the number of pinned packages has been
growing including services and Oslo libraries where we can't follow upper-constraints
anymore[2]. Recently, Kolla has removed support for CentOS 7 so i doubt it makes sense to
keep pinning packages to keep RDO Trunk consistent artificially and continue running
promotion pipelines on a repo with so many outdated packages. Also, pinning these projects
makes that changes needed for CentOS 8 will not be in RDO and would need to be backported
manually to each package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in upper-constraints
(for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so no more
promotions based on it).
- We will keep running centos7-master DLRN builder, so that packages still builing with
Python 2 will be available in current repo [3] to be used by teams needing them until
migration to CentOS 8 is finished everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can remove CentOS 7
ones.
We understand this can add some pressure on moving to CentOS8 to the teams working on it,
but I'd say it's already a priority and it's justified at this stage.
What do you think about this plan?, is there any reason to keep CentOS 7 artificially
consistent and promoting at this point of the transition to CentOS 8?
Has anyone considered just switching everything to Python 3 for both?
Python 3 is now included in CentOS 7 and there's already a large
number of pre-built Python 3 modules in EPEL7.
Failing that, I'd rather just see CentOS 7 support discontinued for
upcoming releases.
--
真実はいつも一つ！/ Always, there's only one truth!
10:16 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Fri, Feb 21, 2020 at 2:40 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Thu, Feb 20, 2020 at 9:04 AM Alfredo Moralejo Alonso
<amoralej(a)redhat.com> wrote:
>
>
> Hi,
>
> I'd like to open a discussion about the status of RDO Ussuri
repositories on CentOS7.
>
> As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
TripleO CI, etc...) have been working to switch to CentOS8 during last few
weeks.
>
> In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
CentOS 8/Python 3. As OpenStack projects have been dropping support for
Python 2, we've started pinning them to the last commit working with Python
2[1], we were expecting that transition will finish soon but it's still
going on. Over time, the number of pinned packages has been growing
including services and Oslo libraries where we can't follow
upper-constraints anymore[2]. Recently, Kolla has removed support for
CentOS 7 so i doubt it makes sense to keep pinning packages to keep RDO
Trunk consistent artificially and continue running promotion pipelines on a
repo with so many outdated packages. Also, pinning these projects makes
that changes needed for CentOS 8 will not be in RDO and would need to be
backported manually to each package. My proposal is:
>
> - Unpin all packages in Ussuri to follow master trunk, or versions in
upper-constraints (for clients and libraries).
> - RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
no more promotions based on it).
> - We will keep running centos7-master DLRN builder, so that packages
still builing with Python 2 will be available in current repo [3] to be
used by teams needing them until migration to CentOS 8 is finished
everywhere.
> - Projects which already have CentOS 8 jobs gating in master branch can
remove CentOS 7 ones.
>
> We understand this can add some pressure on moving to CentOS8 to the
teams working on it, but I'd say it's already a priority and it's justified
at this stage.
>
> What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to
CentOS 8?
>
Has anyone considered just switching everything to Python 3 for both?
Python 3 is now included in CentOS 7 and there's already a large
number of pre-built Python 3 modules in EPEL7.
Some context about the topic in in
https://blogs.rdoproject.org/2020/02/migration-paths-for-rdo-from-centos-...
Failing that, I'd rather just see CentOS 7 support discontinued
for
upcoming releases.
--
真実はいつも一つ！/ Always, there's only one truth!
2:18 p.m.
Hi,
Note that all pins related to python2 support removal have been removed
from RDO Trunk master (Ussuri) today [1].
What that means for RDO users?
- Some packages are now failing to build in
https://trunk.rdoproject.org/centos7-master/report.html, this
centos7-master RDO Trunk repo will not be consistent again and it's
recommended that anyone using RDO Trunk for master/Ussuri in CentOS 7 to
move to CentOS 8 equivalent.
- Now RDO Trunk repo for CentOS 8 in master
https://trunk.rdoproject.org/centos8-master/report.html is consistent and
following master branch or using versions defined in upper-constraints [2].
- Content in promoted repositories previously both for CentOS 7 and 8
should be unaffected by this change.
- There are still two projects still pinned (mistral and neutron) for other
unrelated issues, we'll keep working to get them unpinned as soon as
possible.
- This change has no impact in stable releases.
Please, let us know if you have any question or issue related to this.
Best regards,
Alfredo
[1]
https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+statu...
[2]
https://github.com/openstack/requirements/blob/master/upper-constraints.txt
On Thu, Feb 20, 2020 at 3:03 PM Alfredo Moralejo Alonso <amoralej(a)redhat.com>
wrote:
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories
on CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
TripleO CI, etc...) have been working to switch to CentOS8 during last few
weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
CentOS 8/Python 3. As OpenStack projects have been dropping support for P
ython 2, we've started pinning them to the last commit working with Python
2[1], we were expecting that transition will finish soon but it's still
going on. Over time, the number of pinned packages has been growing
including services and Oslo libraries where we can't follow
upper-constraints anymore[2]. Recently, Kolla has removed support for
CentOS 7 so i doubt it makes sense to keep pinning packages to keep RDO
Trunk consistent artificially and continue running promotion pipelines on a
repo with so many outdated packages. Also, pinning these projects makes
that changes needed for CentOS 8 will not be in RDO and would need to be
backported manually to each package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in u
pper-constraints (for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
no more promotions based on it).
- We will keep running centos7-master DLRN builder, so that packages
still builing with Python 2 will be available in current repo [3] to be
used by teams needing them until migration to CentOS 8 is finished
everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can
remove CentOS 7 ones.
We understand this can add some pressure on moving to CentOS8 to the teams
working on it, but I'd say it's already a priority and it's justified at
this stage.
What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to
CentOS 8?
Best regards,
Alfredo
[1] https://review.rdoproject.org/r/#/q/topic:pin-py2
[2] https://review.rdoproject.org/r/#/c/24796/
[3] http://trunk.rdoproject.org/centos7-master/current
3:54 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
The plan still is to support 7 and 8 in one version to facilitate migration?
Thanks,
Kevin
________________________________________
From: dev <dev-bounces(a)lists.rdoproject.org> on behalf of Alfredo Moralejo Alonso
<amoralej(a)redhat.com>
Sent: Thursday, March 12, 2020 12:18 PM
To: RDO Developmen List; users(a)lists.rdoproject.org
Subject: Re: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS
8
Hi,
Note that all pins related to python2 support removal have been removed from RDO Trunk
master (Ussuri) today [1].
What that means for RDO users?
- Some packages are now failing to build in
https://trunk.rdoproject.org/centos7-master/report.html<https://protec...;,
this centos7-master RDO Trunk repo will not be consistent again and it's recommended
that anyone using RDO Trunk for master/Ussuri in CentOS 7 to move to CentOS 8 equivalent.
- Now RDO Trunk repo for CentOS 8 in master
https://trunk.rdoproject.org/centos8-master/report.html<https://protec...
is consistent and following master branch or using versions defined in upper-constraints
[2].
- Content in promoted repositories previously both for CentOS 7 and 8 should be unaffected
by this change.
- There are still two projects still pinned (mistral and neutron) for other unrelated
issues, we'll keep working to get them unpinned as soon as possible.
- This change has no impact in stable releases.
Please, let us know if you have any question or issue related to this.
Best regards,
Alfredo
[1]
https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+statu...
[2]
https://github.com/openstack/requirements/blob/master/upper-constraints.t...
On Thu, Feb 20, 2020 at 3:03 PM Alfredo Moralejo Alonso
<amoralej@redhat.com<mailto:amoralej@redhat.com>> wrote:
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories on CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO, TripleO CI, etc...)
have been working to switch to CentOS8 during last few weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is still maintaining
Trunk repos consistent for both CentOS 7/Python 2 and CentOS 8/Python 3. As OpenStack
projects have been dropping support for Python 2, we've started pinning them to the
last commit working with Python 2[1], we were expecting that transition will finish soon
but it's still going on. Over time, the number of pinned packages has been growing
including services and Oslo libraries where we can't follow upper-constraints
anymore[2]. Recently, Kolla has removed support for CentOS 7 so i doubt it makes sense to
keep pinning packages to keep RDO Trunk consistent artificially and continue running
promotion pipelines on a repo with so many outdated packages. Also, pinning these projects
makes that changes needed for CentOS 8 will not be in RDO and would need to be backported
manually to each package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in upper-constraints
(for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so no more promotions
based on it).
- We will keep running centos7-master DLRN builder, so that packages still builing with
Python 2 will be available in current repo [3] to be used by teams needing them until
migration to CentOS 8 is finished everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can remove CentOS 7
ones.
We understand this can add some pressure on moving to CentOS8 to the teams working on it,
but I'd say it's already a priority and it's justified at this stage.
What do you think about this plan?, is there any reason to keep CentOS 7 artificially
consistent and promoting at this point of the transition to CentOS 8?
Best regards,
Alfredo
[1]
https://review.rdoproject.org/r/#/q/topic:pin-py2<https://protect2.fir...
[2]
https://review.rdoproject.org/r/#/c/24796/<https://protect2.fireeye.co...
[3]
http://trunk.rdoproject.org/centos7-master/current<https://protect2.fi...
4:58 p.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Thu, Mar 12, 2020 at 3:55 PM Fox, Kevin M <Kevin.Fox(a)pnnl.gov> wrote:
The plan still is to support 7 and 8 in one version to facilitate migration?
I think the goal is to go back to Train and provide 8 packages for
that once we've gotten the current master full converted. So you would
be able to target a migration for Train. Since the upstream has
already dropped py2 support for Ussuri, it's not possible to do this
migration in Ussuri.
Thanks,
Kevin
________________________________________
From: dev <dev-bounces(a)lists.rdoproject.org> on behalf of Alfredo Moralejo Alonso
<amoralej(a)redhat.com>
Sent: Thursday, March 12, 2020 12:18 PM
To: RDO Developmen List; users(a)lists.rdoproject.org
Subject: Re: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS
8
Hi,
Note that all pins related to python2 support removal have been removed from RDO Trunk
master (Ussuri) today [1].
What that means for RDO users?
- Some packages are now failing to build in
https://trunk.rdoproject.org/centos7-master/report.html<https://protec...;,
this centos7-master RDO Trunk repo will not be consistent again and it's recommended
that anyone using RDO Trunk for master/Ussuri in CentOS 7 to move to CentOS 8 equivalent.
- Now RDO Trunk repo for CentOS 8 in master
https://trunk.rdoproject.org/centos8-master/report.html<https://protec...
is consistent and following master branch or using versions defined in upper-constraints
[2].
- Content in promoted repositories previously both for CentOS 7 and 8 should be
unaffected by this change.
- There are still two projects still pinned (mistral and neutron) for other unrelated
issues, we'll keep working to get them unpinned as soon as possible.
- This change has no impact in stable releases.
Please, let us know if you have any question or issue related to this.
Best regards,
Alfredo
[1]
https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+statu...
[2]
https://github.com/openstack/requirements/blob/master/upper-constraints.t...
On Thu, Feb 20, 2020 at 3:03 PM Alfredo Moralejo Alonso
<amoralej@redhat.com<mailto:amoralej@redhat.com>> wrote:
Hi,
I'd like to open a discussion about the status of RDO Ussuri repositories on
CentOS7.
As you know RDO and upstream teams (kolla, puppet-openstack, TripleO, TripleO CI, etc...)
have been working to switch to CentOS8 during last few weeks.
In order to make the transition easier from CentOS 7 to CentOS 8, RDO is still
maintaining Trunk repos consistent for both CentOS 7/Python 2 and CentOS 8/Python 3. As
OpenStack projects have been dropping support for Python 2, we've started pinning them
to the last commit working with Python 2[1], we were expecting that transition will finish
soon but it's still going on. Over time, the number of pinned packages has been
growing including services and Oslo libraries where we can't follow upper-constraints
anymore[2]. Recently, Kolla has removed support for CentOS 7 so i doubt it makes sense to
keep pinning packages to keep RDO Trunk consistent artificially and continue running
promotion pipelines on a repo with so many outdated packages. Also, pinning these projects
makes that changes needed for CentOS 8 will not be in RDO and would need to be backported
manually to each package. My proposal is:
- Unpin all packages in Ussuri to follow master trunk, or versions in upper-constraints
(for clients and libraries).
- RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so no more
promotions based on it).
- We will keep running centos7-master DLRN builder, so that packages still builing with
Python 2 will be available in current repo [3] to be used by teams needing them until
migration to CentOS 8 is finished everywhere.
- Projects which already have CentOS 8 jobs gating in master branch can remove CentOS 7
ones.
We understand this can add some pressure on moving to CentOS8 to the teams working on it,
but I'd say it's already a priority and it's justified at this stage.
What do you think about this plan?, is there any reason to keep CentOS 7 artificially
consistent and promoting at this point of the transition to CentOS 8?
Best regards,
Alfredo
[1]
https://review.rdoproject.org/r/#/q/topic:pin-py2<https://protect2.fir...
[2]
https://review.rdoproject.org/r/#/c/24796/<https://protect2.fireeye.co...
[3]
http://trunk.rdoproject.org/centos7-master/current<https://protect2.fi...
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
3:26 a.m.
New subject: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and transition to CentOS 8
On Thu, Mar 12, 2020 at 10:58 PM Alex Schultz <aschultz(a)redhat.com> wrote:
On Thu, Mar 12, 2020 at 3:55 PM Fox, Kevin M
<Kevin.Fox(a)pnnl.gov> wrote:
>
> The plan still is to support 7 and 8 in one version to facilitate
migration?
>
I think the goal is to go back to Train and provide 8 packages for
that once we've gotten the current master full converted. So you would
be able to target a migration for Train. Since the upstream has
already dropped py2 support for Ussuri, it's not possible to do this
migration in Ussuri.
That's accurate. Train is the version with both CentOS8 and CentOS7, while
ussuri is CentOS8 only.
You can start using RDO Trunk Train for CentOS8 repo already configuring
following repo files:
https://trunk.rdoproject.org/centos8-train/delorean-deps.repo
https://trunk.rdoproject.org/centos8-train/puppet-passed-ci/delorean.repo
About CloudSIG signed packages in CentOS mirrors for Train in CentOS8 we
are still working on it, We'll update on this ML when ready.
You can find some info about RDO moving to CentOS8 in
https://blogs.rdoproject.org/2020/02/migration-paths-for-rdo-from-centos-...
Regards,
Alfredo
> Thanks,
> Kevin
>
> ________________________________________
> From: dev <dev-bounces(a)lists.rdoproject.org> on behalf of Alfredo
Moralejo Alonso <amoralej(a)redhat.com>
> Sent: Thursday, March 12, 2020 12:18 PM
> To: RDO Developmen List; users(a)lists.rdoproject.org
> Subject: Re: [rdo-dev] Status of RDO Trunk Ussuri on CentOS 7 and
transition to CentOS 8
>
> Hi,
>
> Note that all pins related to python2 support removal have been removed
from RDO Trunk master (Ussuri) today [1].
>
> What that means for RDO users?
>
> - Some packages are now failing to build in
https://trunk.rdoproject.org/centos7-master/report.html<
https://protect2.fireeye.com/v1/url?k=2f60d3f0-73d5ec49-2f60f9e5-0cc47adc...;,
this centos7-master RDO Trunk repo will not be consistent again and it's
recommended that anyone using RDO Trunk for master/Ussuri in CentOS 7 to
move to CentOS 8 equivalent.
> - Now RDO Trunk repo for CentOS 8 in master
https://trunk.rdoproject.org/centos8-master/report.html<
https://protect2.fireeye.com/v1/url?k=01759922-5dc0a69b-0175b337-0cc47adc...
is consistent and following master branch or using versions defined in
upper-constraints [2].
> - Content in promoted repositories previously both for CentOS 7 and 8
should be unaffected by this change.
> - There are still two projects still pinned (mistral and neutron) for
other unrelated issues, we'll keep working to get them unpinned as soon as
possible.
> - This change has no impact in stable releases.
>
> Please, let us know if you have any question or issue related to this.
>
> Best regards,
>
> Alfredo
>
> [1]
https://review.rdoproject.org/r/#/q/topic:unpin-py2+(status:open+OR+statu...
<
https://protect2.fireeye.com/v1/url?k=49b1782b-15044792-49b1523e-0cc47adc...
>
> [2]
https://github.com/openstack/requirements/blob/master/upper-constraints.txt
<
https://protect2.fireeye.com/v1/url?k=6724d800-3b91e7b9-6724f215-0cc47adc...
>
>
>
> On Thu, Feb 20, 2020 at 3:03 PM Alfredo Moralejo Alonso <
amoralej@redhat.com<mailto:amoralej@redhat.com>> wrote:
>
> Hi,
>
> I'd like to open a discussion about the status of RDO Ussuri
repositories on CentOS7.
>
> As you know RDO and upstream teams (kolla, puppet-openstack, TripleO,
TripleO CI, etc...) have been working to switch to CentOS8 during last few
weeks.
>
> In order to make the transition easier from CentOS 7 to CentOS 8, RDO is
still maintaining Trunk repos consistent for both CentOS 7/Python 2 and
CentOS 8/Python 3. As OpenStack projects have been dropping support for
Python 2, we've started pinning them to the last commit working with Python
2[1], we were expecting that transition will finish soon but it's still
going on. Over time, the number of pinned packages has been growing
including services and Oslo libraries where we can't follow
upper-constraints anymore[2]. Recently, Kolla has removed support for
CentOS 7 so i doubt it makes sense to keep pinning packages to keep RDO
Trunk consistent artificially and continue running promotion pipelines on a
repo with so many outdated packages. Also, pinning these projects makes
that changes needed for CentOS 8 will not be in RDO and would need to be
backported manually to each package. My proposal is:
>
> - Unpin all packages in Ussuri to follow master trunk, or versions in
upper-constraints (for clients and libraries).
> - RDO Ussuri on CentOS 7 repo consistent link will not move anymore (so
no more promotions based on it).
> - We will keep running centos7-master DLRN builder, so that packages
still builing with Python 2 will be available in current repo [3] to be
used by teams needing them until migration to CentOS 8 is finished
everywhere.
> - Projects which already have CentOS 8 jobs gating in master branch can
remove CentOS 7 ones.
>
> We understand this can add some pressure on moving to CentOS8 to the
teams working on it, but I'd say it's already a priority and it's justified
at this stage.
>
> What do you think about this plan?, is there any reason to keep CentOS 7
artificially consistent and promoting at this point of the transition to
CentOS 8?
>
> Best regards,
>
> Alfredo
>
> [1] https://review.rdoproject.org/r/#/q/topic:pin-py2<
https://protect2.fireeye.com/v1/url?k=1402d0ff-48b7ef46-1402faea-0cc47adc...
>
> [2] https://review.rdoproject.org/r/#/c/24796/<
https://protect2.fireeye.com/v1/url?k=528d2347-0e381cfe-528d0952-0cc47adc...
>
> [3] http://trunk.rdoproject.org/centos7-master/current<
https://protect2.fireeye.com/v1/url?k=a4f15ee1-f8446158-a4f174f4-0cc47adc...
>
> _______________________________________________
> dev mailing list
> dev(a)lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/dev
>
> To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
>
1503
days inactive
1525
days old
16 comments
8 participants
participants (8)
-
Alan Pevec -
Alex Schultz -
Alfredo Moralejo Alonso -
Fox, Kevin M -
John Fulton -
Mike Burns -
Neal Gompa -
Wesley Hayutin