Cloud Standards. Sam Johnston Google Zürich

Transcription

1 Cloud Standards Sam Johnston Google Zürich

2 Disclaimer Personal opinion May/may not reflect official Google position

3 Cloud Computing Internet-based computing, whereby shared resources, software, and information are provided to computers and other devices on demand, like the electricity grid. -- Wikipedia

4 Cloud Computing Second major paradigm shift mainframe > client-server > cloud Shift from IT as a product to IT as a service Similar to the introduction of power grids Disruptive innovation

5 Cloud Stack

6 Cloud Examples Applications: end user applications Gmail, Salesforce, Facebook/Twitter? Platform: developer components/runtimes App Engine, Azure, RDS, SimpleDB, S3 Infrastructure: raw computing resources Amazon EC2/EBS/VPC

7 Electricity Grid Relatively simple Standard voltages, frequency 60Hz vs 50Hz Myriad plugs ( interfaces ) Need an electron for the cloud: apulettes

8 Operating Environment Unix Philosophy: Do one thing... well. Infrastructure services emulate legacy: VMs Focus on platform services App Engine, Azure, Heroku [non-?]relational data stores, queues, etc. Others (e.g. Mechanical Turk)

9 Design Philosophy Design for failure Legacy: unreliable sw on reliable hw Cloud: reliable sw on unreliable hw Create marketable commodities: Gb/months CPU/hours

10 Cloud Standards A standard is an established norm or requirement There are no standards in the cloud Lots of specifications! Many argue it s too early for standards I argue if we don t act now it ll be too late

11 Alternatives Adapters (jclouds, deltacloud, etc.) Impedance mismatch Performance problems Transitional solution Vendor controlled de facto standards

12 Open Standards Copyrights, Patents, Trademarks Multiple interoperable implementations Process is difficult to test > DMTF Many/most are non-proprietary Each implementation is documented

13 Open Cloud Open Cloud Initiative (modeled after OSI) Balance between open and closed Open Protocols + Open Interfaces req d OpenDocument over AtomPub (GData) Open Source, Open Data optional Protects users & vendors

14 Open Cloud Example Google Document List API: GET /document.odt

15

16 Counter Example Microsoft Word Document (.doc) format Trade secret (20+ year reign) Rubber stamped as OOXML, still not fixed Strict vs Transitional Open Virtualisation Format (OVF) ~=.doc?

17 Infrastructure: Compute

18 Amazon EC2 Simple functional API for virtual machines 100% controlled by Amazon Web Services Copyright, patent, trademark problems? Used by AWS, Eucalyptus, OpenNebula Potential (risk?) of being de facto standard

19 Rackspace Cloud Servers RESTful web service for virtual machines JSON based Documentation under Creative Commons Used by Rackspace Cloud Servers Being ported to OpenStack?

20 Sun Oracle Cloud API RESTful web service for virtual machines JSON based Development status unknown Submitted to DMTF vcloud effort

21 OGF OCCI RESTful web service; HTTP based Multiple formats supported (JSON, XML,...) Attempt to develop API from scratch Overdue, ongoing consensus problems Starting point for future efforts?

22 VMware vcloud XML web service for virtual machines Hosted by DMTF; non-public process Controlled by VMware? Dependent on OVF

23 DMTF OVF Open Virtualisation Format (OVF) Pre-dates cloud More (over?) complicated than alternatives Fails to specify disk format; interoperable?

24 IETF Infrastructure API? Document de facto standard? Avoids vendor capture Requires implementor commitments Define blue sky protocol Use OCCI as a starting point? OpenStack as initial implementor?

25 Infrastructure: Storage

26 Amazon S3 HTTP based API for file management 100% controlled by Amazon Web Services Copyright, patent, trademark problems? Used by AWS, Eucalyptus Potential (risk?) of being de facto standard

27 SNIA CDMI CRUD for data elements Also configuration, metadata, etc. Great for enterprise storage Not so much for simplicity Multiple implementors (in theory)

28 IETF Storage API? HTTP? WebDAV? Something in between? No XML please Collections (buckets) are a challenge

29 Other APIs Need platform API More complex than infrastructure Better returns Examples: App Engine, Azure, Force.com Application APIs are application specific Example: Salesforce.com

30 Potential Work Items

31 Existing Standards Internet has TCP/IP Web has HTTP/HTML Proposal: cloud http tcp/ip

32 Uniform Interface Use HTTP as intended Web/Resource Oriented Architecture Metadata in headers (no envelopes) No SOAP, Atom, etc. Multiple/many mime-types for payloads

33 HTTP enhancements Promote HTTP for cloud resources Deviate from HTTP only where necessary Use content types as intended (eg OVF) Metadata in headers, not envelopes (SOAP) Need attributes/collections/categories/links

34 HTTP Verbs COPY MOVE LINK/UNLINK PATCH

35 Web Attributes Examples: ACLs, owners, VM memory, cores Model on cookies ( server-side cookies ) Define Attribute: HTTP header? Better than eg X-VM-Cores Currently just an idea

36 Web Categories Examples: us-east, windows, q Model on Atom categories Category: dog Category: dog; label="canine"; scheme=" See draft-johnston-http-category-header

37 Web Linking Modeled on Atom LINK Examples: VM apps, network, storage, docs Link: </vm01;start>; title=start; rel=action Linking, animating, annotating resources See draft-nottingham-http-link-header

38 Current Drafts draft-nottingham-http-link-header draft-dunbar-arp-for-large-dc-problem-statement draft-johnston-http-category-header draft-johnston-addressing-link-relations

39 External Drafts CloudAudit Advertises compliance for transparency CloudLog Defines structure for syslog entries Subject both to IETF standards process?

40 Next Steps Document existing standards: informational Proposed drafts for IETF-79: draft-johnston-cloud-*-00.txt draft-?-cloudlog-00.txt Cloud BoF at IETF-79