Add initial resources.md for discussion

The first draft of a Kubernetes resource model.
The problem I have with this grouping is that I am SURE there will be differences between resource dimensions.  Consider named disks - they don't have a request, they have an list of {name, request} pairs.  Ditto for {name, limit}, {name, capacity}.  What about a hypothetical SSD resource that allows the user to specify a layering tech (SLC/MLC)?  Do we define an array "layering" that just has SSD in it but not CPU?