4 Commits (960ff51d075d588d91f43ea081cc5b72535209bb)

Author	SHA1	Message	Date
Sarat Kamisetty	dda62ec207	- scheduler extenders that are capable of maintaining their own ... node cache don't need to get all the information about every candidate node. For huge clusters, sending full node information of all nodes in the cluster on the wire every time a pod is scheduled is expensive. If the scheduler is capable of caching node information along with its capabilities, sending node name alone is sufficient. These changes provide that optimization in a backward compatible way - removed the inadvertent signature change of Prioritize() function - added defensive checks as suggested - added annotation specific test case - updated the comments in the scheduler types - got rid of apiVersion thats unused - using *v1.NodeList as suggested - backing out pod annotation update related changes made in the 1st commit - Adjusted the comments in types.go and v1/types.go as suggested in the code review	2017-02-23 10:25:42 -08:00
tanshanshan	a61b5f2490	PodFitsPorts has been replaced by PodFitsHostPorts	2017-01-11 14:52:45 +08:00
tanshanshan	60cf598ac1	fix scheduler extender example	2016-12-01 15:26:47 +08:00
Ravi Gadde	cadc24e9fd	Scheduler extension	2015-11-25 08:19:27 -08:00