Thanks for starting this thread!
Big +1 to that - thanks, Anthony! What I'd be especially interested to
hear about are your thoughts on the feasibility of providing a level of
abstraction at this point.
The main questions for me would be:
* What is the right interface: something that can instantiate a single
image (e.g. Docker)? Or a graph of images (e.g. Kubernetes)? Or both?
* How much commonality is there across providers? At present, the
"single image providers" seem much closer to providing a standard than
the "image graph providers"...but is the single image use case really
that compelling?
* Given that the predominant paradigm for containers is "instantiate and
don't change" (vs. traditional compute, which is more like "instantiate
and modify"), what is the core value of an abstraction over multiple
providers - especially if they are largely all compatible with one API?
I.e. if all I'm trying to do is instantiate a known image, why not
simply use the Docker client or API directly?
Would be great to learn more about how you see this space!
Regards
ap
