Unify the COE API for container operations

Currently, the Kubernetes is using "kubectl create" to create all of k8s objects including pod, rc, service, pv, pvc, hpa etc using either yaml, json, yml, stdin file format (https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_create.md); The marathon+mesos also using yaml, json file to create applications. It is difficult to unify the concept of all COEs but at least seems many COEs are trying to unify the input and output: all using same file format as input and getting same format output.

It is a good signal for Magnum and the Magmum can leverage those features to unify the client interface for different COEs. i.e we can use "magnum create" to create pod, rc, service, pv, pvc even marathon service etc.

- 'magnum create ’, with file which has Swarm/Mesos/Kubernetes specific payload.
- 'magnum container-create’, with simple list of options which work for Swarm/Mesos/Kub. it will be good option for users who just wants to try containers.
- 'magnum get' can get different objects like kubernetes.

root@db06b03:~# kubectl get
You must specify the type of resource to get. Valid resource types include:
   * pods (aka 'po')
   * replicationcontrollers (aka 'rc')
   * daemonsets (aka 'ds')
   * services (aka 'svc')
   * events (aka 'ev')
   * nodes (aka 'no')
   * namespaces (aka 'ns')
   * secrets
   * persistentvolumes (aka 'pv')
   * persistentvolumeclaims (aka 'pvc')
   * limitranges (aka 'limits')
   * resourcequotas (aka 'quota')
   * componentstatuses (aka 'cs')
   * endpoints (aka 'ep')
error: Required resource not specified.