Bug 1303361

Summary:	[DOCS] [3.2] Document the restriction on targeting nodes for pod scheduling
Product:	OpenShift Container Platform	Reporter:	Vikram Goyal <vigoyal>
Component:	Documentation	Assignee:	brice <bfallonf>
Status:	CLOSED CURRENTRELEASE	QA Contact:	DeShuai Ma <dma>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	3.1.0	CC:	adellape, aos-bugs, dma, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-17 01:25:05 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:
Embargoed:
Deadline:	2016-03-15

Description Vikram Goyal 2016-01-31 11:09:01 UTC

In OSE 3.2, an administrator will not be able to schedule pods with a specific node in mind. 

As of creating this bug the work on this feature is still underway, so check closer to the development whether this will make it in 3.2 and if it will impact OSE 3.2.

Dev for this feature is:
Abhishek Gupta, John Lamb

Trello card is:
https://trello.com/c/cGz8l1zD/504-3-user-should-not-be-able-to-target-a-specific-node-for-pod-scheduling

QA for this feature is:
Deshuai Ma

Likely Guide:
It might be sufficient to put this as a warning or note in the Admin Guide here but please make sure to cover a use case and consider if this may need to be mentioned in other guides.
https://docs.openshift.com/enterprise/3.1/admin_guide/scheduler.html

Comment 2 brice 2016-03-22 04:44:27 UTC

PR created for this BZ:

https://github.com/openshift/openshift-docs/pull/1721

I'll put this onto QA.

Deshuai Ma, please let me know if any information needs to be added to the PR. The trello card above has the process, which you have tested before. Thank you!

Comment 3 DeShuai Ma 2016-03-22 05:05:01 UTC

add comment to your pr

Comment 4 DeShuai Ma 2016-03-22 05:05:37 UTC

When this pr is merged, I will verify this bug.

Comment 5 brice 2016-03-31 05:06:51 UTC

Deshuai Ma, this is ready for another QA. Unfortunately, I can't merge this until it passes QA, so if you have any issues with the PR as it is now, please let me know. Then once it is verified then it can be merged:

https://github.com/openshift/openshift-docs/pull/1721

Thanks!

Comment 6 DeShuai Ma 2016-03-31 05:44:04 UTC

(In reply to brice from comment #5)
> Deshuai Ma, this is ready for another QA. Unfortunately, I can't merge this
> until it passes QA, so if you have any issues with the PR as it is now,
> please let me know. Then once it is verified then it can be merged:
> 
> https://github.com/openshift/openshift-docs/pull/1721
> 
> Thanks!

Add comment to the PR. thanks.

Comment 7 openshift-github-bot 2016-04-15 06:04:47 UTC

Commit pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/ad3c731eb60cf066434291d439c7451131ea8504
Merge pull request #1862 from bfallonf/2-bz1303361

Bug: 1303361 Added info on constraining pod placement

Comment 8 brice 2016-05-17 01:25:05 UTC

Verified to be in the 3.2 docs:

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/cluster-administration/#controlling-pod-placement