2017-08-30 15:07 GMT+02:00 Fabian Arrotin arrfab@centos.org:

On 21/08/17 16:57, Brian Stinson wrote:

...

Hi Folks,

We've had a few discussions around how to handle releasing CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) over the past few days.

When we last checked in, there was still a bit of work going on building and testing pre-release CR (the QA team has been hard at work), and the altarch builds were still in progress.

There are 2 ways the release might play out:

• If the altarch (aarch64, and ppc64{,le}) builds are finished, and we are otherwise ready: CBS and CI will be seeded from the mirrors just like usual, and CR will be available at roughly the same time as the rest of the mirror network

• If the altarch builds are not yet ready, the CentOS QA team may decide to release x86_64 ahead of the other arches. In that case, we will wait for ppc and aarch64 but still seed CI and CBS together as soon as the altarch builds are ready.

If there are any questions, feel free to comment here. As always we will post updates as we move forward.

Cheers!

-- Brian Stinson

I was dscussing with some people on IRC who got the false impression that what they were building and also testing in CI was tested against CR. I'm back from "offline mode" and had a quick check, but it seems that your proposal #2 was the one that was chosen : nothing pushed to CBS/CI so built/tested against 7.3 and not 7.3+CR

Just want to be sure that we communicate that as I saw some RDO folks mentioning Pike (next release) being released today and they hoped to follow closely the upstream release. I hope that then the 7.4.1708 release will not break their Pike builds and tests (released before 7.4.1708)

Also note qemu-kvm-ev is still qemu-kvm-ev-2.6.0-28.el7.10.1 http://cbs.centos.org/koji/buildinfo?buildID=17495 because without 7.4 bits in CBS I can't build qemu-kvm-ev-2.9.0-16.el7_4.3.1 http://cbs.centos.org/koji/buildinfo?buildID=19374 so enabling CR repo will break qemu-kvm-ev users.

-- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

Hi,

On 08/31/17 12:18, Karanbir Singh wrote:

x86_64 and ppc64 and ppc64le are ready to go, can we get those into CBS and CI and let aarch64 catchup ? It does not look like Jim's anywhere near closing that off.

Thomas, any options you can think through here ?

We can disable aarch64 and enable CR on specific tags if needed.

And then merge the aarch64 build, but it will be a lot of work on us.

It depends on the SIG deliverable.

I know virt SIG qemu-kvm-ev project needs CR to be able to be ready for 7.4 release day. That's an easy target as we are speaking about few packages and only rebuilds/unbranding from RH.

However I don't think we could do that for cloud SIG Openstack without adding a lot of confusion but I may be wrong.

On 08/31/2017 06:16 AM, John Mark Walker wrote:

What do you need to get aarch64 caught up? I may be able to help.

Access to time travel.

I kid, but largely it was because there was additional code required that wasn't part of the base 7.4 build for x86_64, and that wasn't available until a bit later in the build cycle.

-JM

---

*From:* CentOS-devel centos-devel-bounces@centos.org on behalf of Karanbir Singh mail-lists@karan.org *Sent:* Thursday, August 31, 2017 6:18:34 AM *To:* centos-devel@centos.org *Subject:* Re: [CentOS-devel] Plan for releasing CentOS CR into CBS and CI   x86_64 and ppc64 and ppc64le are ready to go, can we get those into CBS and CI and let aarch64 catchup ? It does not look like Jim's anywhere near closing that off.

Thomas, any options you can think through here ?

On 31/08/17 08:48, Sandro Bonazzola wrote:

...

2017-08-30 15:07 GMT+02:00 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org>:

On 21/08/17 16:57, Brian Stinson wrote:      > Hi Folks,      >      > We've had a few discussions around how to handle releasing CR      > (https://wiki.centos.org/AdditionalResources/Repositories/CR      https://wiki.centos.org/AdditionalResources/Repositories/CR) over the      > past few days.      >      > When we last checked in, there was still a bit of work going on building      > and testing pre-release CR (the QA team has been hard at work), and the      > altarch builds were still in progress.      >      > There are 2 ways the release might play out:      >      > - If the altarch (aarch64, and ppc64{,le}) builds are finished, and we      >   are otherwise ready: CBS and CI will be seeded from the mirrors just      >   like usual, and CR will be available at roughly the same time as the      >   rest of the mirror network      >      > - If the altarch builds are not yet ready, the CentOS QA team may decide      >   to release x86_64 ahead of the other arches. In that case, we will      >   wait for ppc and aarch64 but still seed CI and CBS together as soon as      >   the altarch builds are ready.      >      >      > If there are any questions, feel free to comment here. As always we will      > post updates as we move forward.      >      > Cheers!      >      > --      > Brian Stinson

I was dscussing with some people on IRC who got the false impression      that what they were building and also testing in CI was tested against      CR. I'm back from "offline mode" and had a quick check, but it seems      that your proposal #2 was the one that was chosen : nothing pushed to      CBS/CI so built/tested against 7.3 and not 7.3+CR

Just want to be sure that we communicate that as I saw some RDO folks      mentioning Pike (next release) being released today and they hoped to      follow closely the upstream release. I hope that then the 7.4.1708      release will not break their Pike builds and tests (released before      7.4.1708)

Also note qemu-kvm-ev is still qemu-kvm-ev-2.6.0-28.el7.10.1 http://cbs.centos.org/koji/buildinfo?buildID=17495 because without 7.4 bits in CBS I can't build qemu-kvm-ev-2.9.0-16.el7_4.3.1 http://cbs.centos.org/koji/buildinfo?buildID=19374 so enabling CR repo will break qemu-kvm-ev users.

-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel

On 08/31/2017 03:18 AM, Karanbir Singh wrote:

x86_64 and ppc64 and ppc64le are ready to go, can we get those into CBS and CI and let aarch64 catchup ? It does not look like Jim's anywhere near closing that off.

For aarch64, it's a bit more comprehensive than the rest of the distribution, because we had to wait to get additional pieces for the build. There's a 4.11 kernel, an updated qemu-kvm and about a dozen other packages that weren't released until earlier this week. Some of these are incompatible with the other parts of 7.4, so I've had to sort through them. They're also not currently in git.centos as they weren't part of the last push so I have to sort that out upstream as well.

Given the demands of the CentOS aarch64 community, releasing without the 4.11 kernel isn't an option.

Thomas, any options you can think through here ?

On 31/08/17 08:48, Sandro Bonazzola wrote:

...

2017-08-30 15:07 GMT+02:00 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org>:

On 21/08/17 16:57, Brian Stinson wrote:
> Hi Folks,
>
> We've had a few discussions around how to handle releasing CRFo
> (https://wiki.centos.org/AdditionalResources/Repositories/CR
<https://wiki.centos.org/AdditionalResources/Repositories/CR>) over the
> past few days.
>
> When we last checked in, there was still a bit of work going on building
> and testing pre-release CR (the QA team has been hard at work), and the
> altarch builds were still in progress.
>
> There are 2 ways the release might play out:
>
> - If the altarch (aarch64, and ppc64{,le}) builds are finished, and we
>   are otherwise ready: CBS and CI will be seeded from the mirrors just
>   like usual, and CR will be available at roughly the same time as the
>   rest of the mirror network
>
> - If the altarch builds are not yet ready, the CentOS QA team may decide
>   to release x86_64 ahead of the other arches. In that case, we will
>   wait for ppc and aarch64 but still seed CI and CBS together as soon as
>   the altarch builds are ready.
>
>
> If there are any questions, feel free to comment here. As always we will
> post updates as we move forward.
>
> Cheers!
>
> --
> Brian Stinson

I was dscussing with some people on IRC who got the false impression
that what they were building and also testing in CI was tested against
CR. I'm back from "offline mode" and had a quick check, but it seems
that your proposal #2 was the one that was chosen : nothing pushed to
CBS/CI so built/tested against 7.3 and not 7.3+CR

Just want to be sure that we communicate that as I saw some RDO folks
mentioning Pike (next release) being released today and they hoped to
follow closely the upstream release. I hope that then the 7.4.1708
release will not break their Pike builds and tests (released before
7.4.1708)

Also note qemu-kvm-ev is still qemu-kvm-ev-2.6.0-28.el7.10.1 http://cbs.centos.org/koji/buildinfo?buildID=17495 because without 7.4 bits in CBS I can't build qemu-kvm-ev-2.9.0-16.el7_4.3.1 http://cbs.centos.org/koji/buildinfo?buildID=19374 so enabling CR repo will break qemu-kvm-ev users.