Difference between revisions of "Next middleware release"
Jump to navigation
Jump to search
m (renamed gLExec-wn into gLExec as it is more generic.) |
|||
Line 17: | Line 17: | ||
== Tentative draft plan == | == Tentative draft plan == | ||
* create UMD5/C7 with all products that offer support all over the next years (ideally until 2024) | |||
* | * once it's ready, ask sites to switch: UMD4/C7 -> UMD5/C7; this will provide sites with a supported OS including officially supported products at least until 2024, and could allow starting the slow retirement of UMD4 (SL6 retirement starting at end of 2020, C7 to be eventually used only for products phasing out and doomed to dismission). | ||
* UMD5/C8 gets filled meanwhile in parallel; you know, this relies very much on the product teams | |||
== Plans == | == Plans == |
Revision as of 11:26, 16 June 2020
Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
Plans on CentOS8 for UMD
- CentOS8 released in September 2019 https://lists.centos.org/pipermail/centos-announce/2019-September/023449.html
- same life cycle as RHEL https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates
- CentOS8 will be maintained until May 2029
- CentOS7 will be maintained until June 2024
- SL6 will be maintained until November 2020
- same life cycle as RHEL https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates
UMD5 with CentOS 7 and 8
- Pros
- remove unsupported software in UMD-4 which makes keeping the repository consistent hard to the UMD team
- Cons
- Have to maintain 2 versions for a given period, along with a campaign to replace repo configuration on the sites is needed (replace UMD4/CentOS7 with UMD5/CentOS7)
Tentative draft plan
- create UMD5/C7 with all products that offer support all over the next years (ideally until 2024)
- once it's ready, ask sites to switch: UMD4/C7 -> UMD5/C7; this will provide sites with a supported OS including officially supported products at least until 2024, and could allow starting the slow retirement of UMD4 (SL6 retirement starting at end of 2020, C7 to be eventually used only for products phasing out and doomed to dismission).
- UMD5/C8 gets filled meanwhile in parallel; you know, this relies very much on the product teams
Plans
Activity order is: Planned, Assigned, Started, Ongoing, Completed
ID | Creation date | Action | Assignee | Status | Completion date | Depends on |
---|---|---|---|---|---|---|
1 | 2020-02-12 | add CentOS8 to the supported platforms in the admin-repo | William | Done | 2020-02-17 | |
2 | 2020-02-10 | Get plans on CentOS8 for all CentOS7 products | Vincenzo | Started | ||
3 | 2020-02-10 | Create instructions for CentOS8 on the Frontend | Vincenzo | Planned | 8 | |
4 | 2020-02-10 | Preview repository for CentOS8 | Alessandro | Assigned | ||
5 | 2020-02-12 | Vincenzo to create the UMD5 release | Vincenzo | Done | 2020-02-17 | 1 |
6 | 2020-02-12 | create the configuration packages for UMD5/CentOS7 and UMD5/CentOS8 | William | Assigned | 1 | |
7 | 2020-02-12 | add CentOS8 value in the RT | Vincenzo | Done | 2020-02-19 | 1 |
8 | 2020-02-12 | test with a dry run the whole process throught C7 and C8 | Joao | Planned | 5, 6, 7 | |
9 | 2020-02-12 | publish UMD5 on the frontend (instructions + menu) | William | Planned | 3, 10 | |
10 | 2020-02-12 | include products and create UMD 5.0.1 | Joao | Started | 8 |
Supported products
Product | UMD4/CentOS7 | UMD4/CentOS8 | Status and comments |
---|---|---|---|
XROOTD | Y | ToBeIncluded | In EPEL8 |
Globus/GCT | Y | ToBeIncluded | In EPEL8 |
GFAL2 | Y | ToBeIncluded | In EPEL8 |
Davix | Y | ToBeIncluded | In EPEL8 |
ARC-CE | Y | ToBeIncluded | In EPEL8 |
StoRM | Planned | ? | Storm planned release in C7 for March 2020, plans for C8 to be provided |
VOMS-Admin | Planned | ? | VOMS Admin is not yet released for CENTOS 7, and that will be the main new package. |
VOMS-Server | Planned | ? | Minor changes will be introduced in the VOMS server package (mainly, a systemd unit file), and the codebase is the one that correctly builds against openssl 1.1 (i.e. 2.1.0). |
APEL | Y | ? | Should work on C8 (Python), but needs building and then testing. |
APEL-SSM | Y | ? | Should work on C8 (Python), but needs building and then testing. |
ARGUS | Y | ? | No feedback yet. |
BDII-CORE | Y | ? | No feedback yet. |
BDII-SITE | Y | ? | No feedback yet. |
BDII-TOP | Y | ? | No feedback yet. |
CanL | Y | ? | No feedback yet. |
Canl-java | Planned | ? | No feedback yet for C8. Planned on C7. |
CVMFS | Y | ToBeIncluded | Supported with cvmfs-2.7.0. |
DCACHE | Y | ? | No feedback yet. |
DPM | Y | ? | No feedback yet. |
UI | Y | ? | No feedback yet. |
WN | Y | ? | No feedback yet. |
Frontier-squid | Y | ToBeIncluded | The C6/C7 rpm tested successfully on C8, no problems found. |
FTS3 | Y | ? | No feedback yet. |
GFAL2 | Y | ? | No feedback yet. |
gLExec & LCMAPS | Y | Y | packages built and tested succesfully and available at http://software.nikhef.nl/dist/mwsec/rpm/epel8/ |
GridSite | Y | ? | No feedback yet. |
CGSI-GSoap | Y | ? | No feedback yet. |
QCG-COMPUTING | Y | ? | No feedback yet. |
QCG-NTF | Y | ? | No feedback yet. |
VOMS-CLIENTS | Planned | ? | No feedback yet for C8. Planned on C7. |
YAIM-CORE | Y | ? | No feedback yet. |
Globus-Default | Y | ? | No feedback yet. |
HTcondor | Y | ? | No feedback yet. |
HTcondor-CE | Y | ? | No feedback yet. |
Dynafed | Y | ? | No feedback yet. |
Globus-default-Security | Y | ? | No feedback yet. |
Globus-GRAM5 | Y | ? | No feedback yet. |
Globus-GridFTP | Y | ? | No feedback yet. |
Globus-MYPROXY | Y | ? | No feedback yet. |
Unsupported products
- CREAM: EOL at end of 2020
- L&B, lcg-clients, MPI, Proxy-Renewal, SLURM WN, TORQUE*, UNICORE*, WMS, SAGA, IGE-Security Integration, Gridway, GridSAFE, GSI_SSHTerm: already unsupported on C7