Add initial resources.md for discussion

The first draft of a Kubernetes resource model.
In addition to scalars, Apache Mesos also allows resource types to be ranges of integers (e.g. ports) and sets of strings (e.g. device ids). Would you consider these types for Kubernetes as well, or would you stick to your quantitative rule, perhaps using integer port/device counts for the request value and metadata for specifically desired elements?