What We Need Are Standards in the Cloud
summary
Argues that cloud success needs concrete, open interfaces and open formats with at least one open source implementation and royalty‑free patents, not vague promises; cites OVF, Amazon S3 and Rackspace APIs as examples of lock‑in risk and names adapters like jclouds and fog and Delta Cloud plus OpenStack and Google’s Data Liberation as practical tools. Recommends building interoperable implementations first, then standardizing, leaning on http as uniform interface and RESTful semantics to minimize vendor capture and enable portability.
AI-written summary · about
chapters (48)
- 0:00Start
- 0:53open standards?
- 1:0915 definitions
- 1:29rubber stamp
- 2:27non-profit maintainer
- 2:58free software
- 3:08open source definition
- 3:18balance
- 3:53open cloud manifesto
- 4:28trademarks
- 5:56open interfaces
- 6:08opendocument
- 6:21GET /document.odt
- 6:36google docs list api
- 6:47creative commons
- 7:22free cloud
- 7:38adapters: deltacloud, jclouds, fog...
- 7:51impedance mismatch
- 8:04what we need is an open cloud standard
- 8:33http: uniform interface
- 8:56metadata in headers
- 9:41design for failure
- 9:52need standards
- 10:36portability
- 10:49unfettered competition
- 11:32railway gauges
- 11:48what could possibly go wrong?
- 12:081865: narrow gauge
- 12:28electricity
- 12:44not to mention plugs
- 12:58cell processor
- 13:19internet standards
- 13:30http, ftp, bittorrent
- 13:40open wins
- 13:51next steps?
- 14:05consume services
- 14:56What We Need are Standards in the Cloud
- 15:49My name is Benjamin Black
- 17:13Independence
- 17:41A hierarchy of needs.
- 20:15The cycle
- 20:55Competition.
- 21:22Goal: Discovery
- 23:09Maturation.
- 23:37Successful standards formalize what is already true.
- 24:18There are no successful standards absent successful implementations.
- 27:17Standard specification
- 28:39Standard committees don't build.
