Budget requests for FY2020-Q4

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
Hardware Location:
Requestor: lgriffin@redhat.com
Council Rep: Martin Kosek
Reason for Purchase:
Desc of Purchase:
Additional Notes:
Quotes URL:
QTY:
Unit Cost:
Q4 Cost:
CY20 Total Cost:
Why can this not be shared: These systems are being purchased to
locate in a community region where internal work would be exposed to
external viewing. They are in a sense shared with the community that
CentOS and Fedora get product work from.
Can the workload be virtualized: These systems are being bought to
virtualize work loads which can not be put into AWS or similar
clouds due to build system architectural requirements.
What product will stop shipping:
What critial Red Hat services will stop functioning:
What community facing project will suffer and how:
Describe the status of the existing hardware:

CentOS Stream RHEL-9 Servers

Date: 2020-08-24
From: 700
Target CC: 700
CC: 700
CY20 R&D Initiative: RHEL-9
CY20 Interlock: N/A
Original Shared Lab: N/A
Sub-Team: CPE
Shared Lab: N/A
Resource Type: Non-shared
Hardware Location: Morrisville (RDU-CC)
Requestor: lgriffin@redhat.com
Council Rep: Martin Kosek
Reason for Purchase: Currently CentOS Stream does not have any servers which are under any sort of warranty and are over 5 years old. In order to make sure that C9 is able to meet its deadlines without significant risk, we are looking to buy hardware with warranties.
Desc of Purchase: 3 Dell R640 servers with 384 GB RAM and 48 cores
Additional Notes:
Quotes URL:
QTY: 3
Unit Cost:
Q4 Cost:
CY20 Total Cost:
Why can this not be shared: These systems are being purchased to
locate in a community region where internal work would be exposed to
external viewing. They are in a sense shared with the community that
CentOS and Fedora get product work from.
Can the workload be virtualized: These systems are being bought to
virtualize work loads which can not be put into AWS or similar
clouds due to build system architectural requirements.
What product will stop shipping:
What critial Red Hat services will stop functioning:
What community facing project will suffer and how:
Describe the status of the existing hardware:

Date: 2020-08-24
From: 700
Target CC: 700
CC: 700
CY20 R&D Initiative: None
CY20 Interlock: None
Original Shared Lab: N/A
Sub-Team: CPE
Shared Lab: N/A
Resource Type: Non-shared
Hardware Location: IAD2
Requestor: lgriffin@redhat.com
Council Rep: Martin Kosek
Reason for Purchase: to replace 5 to 6 year old equipment
Desc of Purchase: A purchase of 6 systems to allow for Fedora to
move to OpenShift 4
Additional Notes:
Quotes URL:
QTY:
Unit Cost:
Q4 Cost:
CY20 Total Cost:
Why can this not be shared: These systems are being purchased to
locate in a community region where internal work would be exposed to
external viewing. They are in a sense shared with the community that
CentOS and Fedora get product work from.
Can the workload be virtualized: These systems are being bought to
virtualize work loads which can not be put into AWS or similar
clouds due to build system architectural requirements.
What product will stop shipping:
What critial Red Hat services will stop functioning:
What community facing project will suffer and how:
Describe the status of the existing hardware:

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
Hardware Location:
Requestor: lgriffin@redhat.com
Council Rep: Martin Kosek
Reason for Purchase:
Desc of Purchase:
Additional Notes:
Quotes URL:
QTY:
Unit Cost:
Q4 Cost:
CY20 Total Cost:
Why can this not be shared: These systems are being purchased to
locate in a community region where internal work would be exposed to
external viewing. They are in a sense shared with the community that
CentOS and Fedora get product work from.
Can the workload be virtualized: These systems are being bought to
virtualize work loads which can not be put into AWS or similar
clouds due to build system architectural requirements.
What product will stop shipping:
What critial Red Hat services will stop functioning:
What community facing project will suffer and how:
Describe the status of the existing hardware: