Bug 1371074

Summary:	NVidia GPU support
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED DEFERRED	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	aos-bugs, davidjbrewer, decarr, fedoraproject, javier.ramirez, jchaloup, jeder, jkaur, joarcher, jokerman, mbarrett, mmccomas, sreber, tvvcox, wmeng
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-12 13:54:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jaspreet Kaur 2016-08-29 09:41:42 UTC

1. What is the nature and description of the request?
   -Nvidia GPU support for pods scheduling and resource monitoring 
   https://github.com/kubernetes/kubernetes/issues/19049


2. Why is this needed? (List the business requirements here)
This is required so that we can run hpc based workload in opesnhift

3.How would you like to achieve this? (List the functional requirements here)
        - Node need to provide the GPU hardware information along with the CPU, memory information to the Master. 
        - To schedule Pods based on GPU. 


4. Is there a specific timeline dependencies?
asap

5. Are you able to assist in testing this functionality if implemented?
yes

Comment 7 john archer 2017-07-19 14:39:08 UTC

How can I determine or see the planned target OCP release? or K8S version?

Comment 9 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.