Proposal: Describe possible project structure and implications

Initial thoughts around scoping Kubernetes resources to projects and the associated implications.

Intended as a complement to #891, but with more detail on the implementation consequences of project scoping throughout the stack.

Would like to get general agreement on an outline to proceed against to support an initial prototype in next couple weeks.
Not sure what you think won't scale.  
Assume 1KB of data needed to represent a pod.
Assume 1000 minions with 10 pods per minion for total of 10K pods.
So all the pod data takes up 10MB.
Seems to me that it is not a memory issue at all, not a network issue to list all the pods every few seconds, and not a CPU issue to scan all the pods repeatedly many times per second.


 datathen we could100K pods would 
The scheduler should not have trouble holding data about all the pods and minions in memory at the same time.   It should