intercloud interoperabilitySam Johnston @samj <samj@samj.net>
interneta global network of networks
internet protocol (ip)    lingua franca of the internet
interclouda global cloud of clouds
cloud protocol?  lingua franca of the cloud?
start with http?most web services are http based
common functionalityencryption, authentication, proxying, load balancing, etc.
end up with soap?  simple object access protocol
POST /InStock HTTP/1.1Host: www.example.orgContent-Type: application/soap+xml; charset=utf-8Content-Length: 299SOAPAction:...
transport?  http? smtp?
interface?function calls & returns tbd
formats?data interchange formats tbd
complexitybarriers to entry, poor performance, low security, etc.
restrepresentational state transfer
http as intended    interface still tbd
http headers?no need for a new metadata channel
metadatalinking, categories, attributes
semantic webeav/cr (entity, attribute, value w/ classes & relationships)
occiopen cloud computing interface
cloud managementgood for new implementations & compatibility layers
safe extensibility?extensions? registries? namespaces? state machines?
what do we solve for?integration? interoperability? compatibility? portability?
integrationcombining components into an overall system
interoperabilityability to exchange and use information
compatibilityability to share the same environment
portabilitymigration of components between environments
how do we solve it?   open source? open standards?
open sourceuses copyrights to open products
open clouduses standard formats & interfaces to open services
internet emaillowest common denominator
smtpsimple mail transfer protocol
client access?out of scope (e.g. outlook to exchange)
management?out of scope (e.g. mmc to exchange)
portability?out of scope (e.g. attachments)
mail transferin scope (e.g. exchange to lotus notes)
simplelowest common denominator
swtp?simple workload transfer protocol?
workloadsvirtual machines, database snapshots, queue states, etc.
transporthypertext transfer protocol (http)
portabilityinternet media types (e.g. application/ovf)
discovery/robots.txt » /.well-known/ (rfc5785)? json-home?
enumeration? text/uri-list? xml? json?
annotation?“semantic” http headers? json? xml? in-band?
performance?premature optimisation - O(1) vs O(n+1)
migration?http move, copy, pass-thru authentication, etc.
workload formats?  out of scope (but still critical)
proprietary formats?  dmtf’s ovf ~= microsoft’s word doc?
virtual machinessimple disk image + attributes format
Intercloud interoperability
Intercloud interoperability
Upcoming SlideShare
Loading in …5
×

Intercloud interoperability

1,314 views

Published on

My presentation for the Zürich University of Applied Sciences (ZHAW) "Cloud-based Service Platforms for the Future Internet" conference held in Winterthur on 29 November 2012.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Intercloud interoperability

  1. 1. intercloud interoperabilitySam Johnston @samj <samj@samj.net>
  2. 2. interneta global network of networks
  3. 3. internet protocol (ip) lingua franca of the internet
  4. 4. interclouda global cloud of clouds
  5. 5. cloud protocol? lingua franca of the cloud?
  6. 6. start with http?most web services are http based
  7. 7. common functionalityencryption, authentication, proxying, load balancing, etc.
  8. 8. end up with soap? simple object access protocol
  9. 9. POST /InStock HTTP/1.1Host: www.example.orgContent-Type: application/soap+xml; charset=utf-8Content-Length: 299SOAPAction: "http://www.w3.org/2003/05/soap-envelope"<?xml version="1.0"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Header> </soap:Header> <soap:Body> <m:GetStockPrice xmlns:m="http://www.example.org/stock"> <m:StockName>IBM</m:StockName> </m:GetStockPrice> </soap:Body></soap:Envelope>
  10. 10. transport? http? smtp?
  11. 11. interface?function calls & returns tbd
  12. 12. formats?data interchange formats tbd
  13. 13. complexitybarriers to entry, poor performance, low security, etc.
  14. 14. restrepresentational state transfer
  15. 15. http as intended interface still tbd
  16. 16. http headers?no need for a new metadata channel
  17. 17. metadatalinking, categories, attributes
  18. 18. semantic webeav/cr (entity, attribute, value w/ classes & relationships)
  19. 19. occiopen cloud computing interface
  20. 20. cloud managementgood for new implementations & compatibility layers
  21. 21. safe extensibility?extensions? registries? namespaces? state machines?
  22. 22. what do we solve for?integration? interoperability? compatibility? portability?
  23. 23. integrationcombining components into an overall system
  24. 24. interoperabilityability to exchange and use information
  25. 25. compatibilityability to share the same environment
  26. 26. portabilitymigration of components between environments
  27. 27. how do we solve it? open source? open standards?
  28. 28. open sourceuses copyrights to open products
  29. 29. open clouduses standard formats & interfaces to open services
  30. 30. internet emaillowest common denominator
  31. 31. smtpsimple mail transfer protocol
  32. 32. client access?out of scope (e.g. outlook to exchange)
  33. 33. management?out of scope (e.g. mmc to exchange)
  34. 34. portability?out of scope (e.g. attachments)
  35. 35. mail transferin scope (e.g. exchange to lotus notes)
  36. 36. simplelowest common denominator
  37. 37. swtp?simple workload transfer protocol?
  38. 38. workloadsvirtual machines, database snapshots, queue states, etc.
  39. 39. transporthypertext transfer protocol (http)
  40. 40. portabilityinternet media types (e.g. application/ovf)
  41. 41. discovery/robots.txt » /.well-known/ (rfc5785)? json-home?
  42. 42. enumeration? text/uri-list? xml? json?
  43. 43. annotation?“semantic” http headers? json? xml? in-band?
  44. 44. performance?premature optimisation - O(1) vs O(n+1)
  45. 45. migration?http move, copy, pass-thru authentication, etc.
  46. 46. workload formats? out of scope (but still critical)
  47. 47. proprietary formats? dmtf’s ovf ~= microsoft’s word doc?
  48. 48. virtual machinessimple disk image + attributes format

×