Date: 2020-08-24 From: 700 Target CC: 700 CC: 700 CY20 R&D Initiative: RHEL-9 CY20 Interlock: Original Shared Lab: N/A Sub-Team: CPE Shared Lab: N/A Resource Type: Non-shared

CentOS 2 42 U rack (6k/rack) = 12k 4 APC power distribution racks (2k/pdu) = 8k 6 Dell R640's {standard build} 20k/per {dedicated to stream} = 120k 2 Dell R740's {standard build} 30k/per {dedicated to storage} = 60k 2 10 gig juniper network switch (12k) = 24k 2 1 gig juniper network switch (8k) = 16 4 Power 9 systems (35k/system) = 140k 4 Power 10 systems (40k/system) = 160k

Known Tasks to work on [x] install kernel02 for jforbes [x] finish retrace03 install for shipment to RDU-CC [x] Debug jcline login problem [x] Rebuild kernel02 for different needs [ ] finish copr-vmhost installs for shipment to RDU-CC [ ] install with RHEL-8 [ ] set up copr-vmhost01 to mount storinator for backups of COPR

MVFE- Minimal Viable Fedora Environment PHX2 - Chandler Arizona datacentre RDU-CC Morrisville NC datacentre community cage IAD2 - Ashburn Equinix datacentre Week 00 (2020-03-02 -> 2020-03-08) [ ] Hardware shipping needs to be planned out [ ] Rack layouts for IAD2 and RDU-CC need to be finalized [ ] Work with RH IT on what they need in network diagrams

--- title: Infrastructure Meeting template tags: Fedora, Infra, CPE --- # Infrastructure Meeting Send on IRC a day before meeting (#fedora-noc #fedora-admin #fedora-releng #fedora-apps) ``` REMINDER: There will be a Fedora Infrastructure meeting tomorrow (2019-09-05) at 15:00 UTC in #fedora-meeting-1. Please check the agenda at https://hackmd.io/@ssmoogen/HyqIIdlmS and mail updates to sysadmin-main members. ``` On the day of the meeting send the following ``` REMINDER: There will be a Fedora

# EPEL-8 FAQ and Packaging Procedures ## Introduction When a new Red Hat Enterprise Linux occurs, one of the steps to get EPEL going for it is branching of various packages into new namespace. The EPEL Steering Committee does not mass branch all existing packages into the namespace because it has caused multiple problems: 1. The package maintainers did not want to support the package in the newer version of EPEL. Package maintainers may only want to support certain versions of Enterprise Linux

Meeting Minute 2019-07-22 === ###### tags: `Templates` `Meeting` :::info - **Location:** BlueJeans - **Date:** 2019-07-22 - **Agenda** 1. Walk through signup flow `5 min` > Smoogen 2. Sprint planning `45min` 3. Revisit onboarding v1 `20min` - **Participants:** - Smooge (SS) - Karsten Hopp - Contyk - Mohan - Merlin - - **Contact:** Smooge <smooge@redhat.com> - **Host:** SS - **Reference:** None ::: ## Questions and Comments 1. When will we do branch to RHEL8 2. Get

# Risk Management Plan * Project Name: * Date: * Prepared By: ## Risk Matrix | RISK | Impact | Probabilty | Score | | -------- | -------- | ---------- | ----- | | Text | Text | Text | Text | | Text | Text | Text | Text | ## Risk Analysis ### RISK Score Matrix | X | 0 | 1 | 2 | 3 | 4 | 5 | | ----- | ---- | ---- | ------ | ------ | ------ | ------ | | **0** | LOW | LOW | LOW | LOW | LOW | LOW | | **1** | LOW | LO

# Project Scope Statement * Project Name: * Projected Start: * Projected End: * Projected Duration: ## Project Purpose: ## Desired Results: ## Exclusions: ## Communication Needs: ## Acceptance Criteria: ## Constraints: 1. Top Constraint 2. Second... ## Approvals: | Key StakeHolder | Interview Date | Approval | | --------------- | -------------- | -------- | | Text | Text | Text | | Text | Text | Text |

# Key Stakeholder Interview * Interviewee: * Interviewer: * Date: ## Project Purpose: ### (Key Reason for Project) ## Description: ## tl;dr: * What are the Key Deliverables * When are they to Be Delivered * How are they to be Delivered ### Long Form ## Desired Results: ### Prioritized List of Specific and Measurable Deliverables 1. First Deliverable 1.1. First Measure 2. Second Deliverable 2.1. First Measure ## Exclusion: ### (Items Out of Scope ) * First item out of scope * Second item o

# EPEL-8 RELENG STEPS The following is a reverse engineering of what is needed to set up and run a new EPEL release. It goes from steps that we find and did to make EPEL-8 in Fedora staging. We will review these notes to see what is needed to redo and later to be done in production High Level Steps ================ 0. Create the Package keys for EPEL-8 1. Create the epel8-base tag 2. Add to epel8-base the external repos pointing to http://kojipkgs.fedoraproject.org/repo/rhel/rhel8/koji/la

# EPEL-8 Production Layout ## TL; DR: 1. EPEL-8 will have a multi-phase rollout into production. 2. EPEL-8.0 will build using existing grobisplitter in order to use a 'flattened' build system without modules. 3. EPEL-8.1 will start in staging without grobisplitter and using default modules via mock. 4. The staging work will allow for continual development changes in koji, 'ursa-prime', and MBS functionality to work without breaking Fedora 31 or initial EPEL-8.0 builds. 5. EPEL-8.1 will look to

# Update on EPEL-8 Status ## Why is EPEL-8 Taking So Long (tl;dr:) 1. Getting koji to work smoothly with modules has been hard. A multi-level fix has had to be worked to get it working in staging. * Needed a way to split out default modules to deal with koji merge options. [Grobisplitter](https://github.com/puiterwijk/grobisplitter) was written to do this * [Koji](https://pagure.io/koji) needed further patching to deal with src.rpms with same NVR but different targets (some python2 and pyt