Differences between revisions 11 and 12

Deletions are marked like this. Additions are marked like this.
Line 61: Line 61:
Line 78: Line 77:
 * 2019-09-13 Currently, we now have full os/ install trees and full !NetInstall and Everything ISOs for all 7 arches (i386, x86_64, ppc64le, ppc64, power9, armhfp, aarch64), in the QA tree. Now that we have all the os/ repos done and verified, we can do the update repos and the extras repos.
Line 79: Line 79:
 * 2019-09-13 Currently, we now have full os/ install trees and full !NetInstall and Everything ISOs for all 7 arches (i386, x86_64, ppc64le, ppc64, power9, armhfp, aarch64), in the QA tree. Now that we have all the os/ repos done and verified, we can do the update repos and the extras repos.
 * 2019-09-17 Release complete.
 * 2019-09-17 Release complete.

Updates At Bottom of Document as Needed

CentOS 7.7.1908 Rough Status Page

Red Hat Enterprise Linux 7.7 was released on 2019-08-06. We are currently building the CentOS 7.7.1908 release from those sources.

One major issue with this release is that the aarch64 and power9 (ALT) architectures are no longer being done as part of RHEL 7.7. The CentOS project is going to TRY to maintain our aarch64 and power9 arches in 7.7.1908 and throughout the entire CentOS 7 Linux life. Since the kernel-alt is no longer being maintained by Red Hat for RHEL-7.7 we are going to try to backport the currently maintained EL8 kernels for ppc64le and aarch64 into CentOS-7.7.1908.

General Steps

Steps needed to make a CentOS rebuild usually follow these steps:

  1. Red Hat makes the sources available.
    1. This used to be done via src.rpms but 7 changed to git repos (at https://git.centos.org/)

    2. The pushes from Red Hat happened on 2019-08-06.
  2. CentOS needs to look at the sources and determine what is needed to build these packages
    1. There are always packaging loops which need to be worked out. You need golang-(X-1) to build golang-X but golang-(X-1) doesn't exist yet.. how do you build a version and break the loop (ie - bootstrapping new packages)?
  3. CentOS needs to go through the source code and find out all the places where debranding is needed.
    1. No you can't just "sed s'/Red Hat/CentOS/' (someone always offers that)
    2. There are times when you do replace and times when you don't.
  4. Builds can start occurring through the system
    1. This usually requires a multi-loop as you do a build to get started
    2. Then rebuild that core with itself
    3. Then add some more and possibly repeat 1 && 2 a couple of times.

    4. Then you can start building out the rest of the packages
  5. The installer usually takes a certain amount of work to get packaged together.
    1. Some things need additional patches
    2. Some things just need to be ordered correctly
    3. Some things like shim signatures for Secure Boot take outside review by signing authority
  6. Continuous Release (CR) Repository
    1. The Continuous Release (CR) Repository is where updates that will be CentOS 7.7.1908 will initially be released to CentOS Users. Here is a detailed explanation of what the CR repo is.

    2. There is QA work for the CR rpms. Once we are satisfied with CR, we will release CR.
  7. Final ISO / Install Tree and Final QA work can begin
    1. Full trees for all arches will be assembled from the new CR packages and any older packages that were already part of the 7.6.1810 CentOS Linux release.
    2. The installer tree and the install media are created.
    3. Full QA testing of the Install Tree, Install Media is conducted.
    4. Zero Day updates and the extra repositories (extras, centosplus, all Special Interest group content, etc.) for the new release are compiled.
    5. These new repositories are released to the QA team for testing.
  8. A final build is released

The above is a 'you asked the people trying to build the train when it will arrive' guide. That said, every release is different and the order and additional steps get found and added each time.

Current Build Status

In the above roadmap, we are currently somewhere in the middle of step 6 but as part of that, we are working on those new power9 and aarch64 kernels backported from EL8.

The current status of all builds can be seen on CentOS Build Logs Server, look in the c7.1908.* directories

Architectures

Main architectures

The following arches are built automatically in parallel.

AltArch

Current Timeline

Item

Started

Ended

Status

Sources pushed to CentOS Git

2019-08-06

2019-08-06

DONE

Source code evaluation

2019-08-06

2019-08-07

DONE

Debranding patches added

2019-08-07

(on going for updates)

DONE

Build Loop 0

2019-08-07

2019-08-10

DONE

Build Loop 1

2019-08-10

2019-08-13

DONE

Build Loop N

2019-08-13

2019-09-13 (including new p9, aarch64 kernels)

DONE

QA CR

Mid-August

2019-09-13

DONE

CR Release

Mid-August

2019-09-13

DONE

Installer work

Early Sept

2019-09-13

DONE

Updates & Extras Repos

2019-09-13

2019-09-17

DONE

Final QA work

2019-09-15

2019-09-17

DONE

Release work

2019-09-15

2019-09-17

DONE

Updates

  • 2019-09-13 Currently, we now have full os/ install trees and full NetInstall and Everything ISOs for all 7 arches (i386, x86_64, ppc64le, ppc64, power9, armhfp, aarch64), in the QA tree. Now that we have all the os/ repos done and verified, we can do the update repos and the extras repos.

  • 2019-08-15 Currently working on the p9 and aarch64 kernels and validating the final CR manifest.
  • 2019-09-17 Release complete.

Definitions

  • DONE - Step is completed
  • Ongoing - Work is progressing
  • Not started - This step may require work from another step to reach some completion or requires time from a person who is working on other parts.
  • Build loop 0 - Getting an initial set of packages together which can then build more packages
  • Build loop 1 - Using the smallest set of packages to build a larger set which can then build more packages
  • Build loop N - I really don't know how many loops this is going to be.. so we will use N nomenclature.
  • Installer work - there is usually some work needed to make the installer actually work with various things like secure boot or different fonts or 'oh they fixed that in an upgrade.img., let us just short cut and put that here.'

About/Building 7 (last edited 2019-09-17 14:48:56 by AlanBartlett)