Keynote: JP Schmetz - How i learned to stop worrying and love

753 views
678 views

Published on

Jean-Paul Schmetz, HackFwD - How I learned to stop worrying and love the Cloud
---
Please contact us for a downloadable copy of the slides at CloudOps.Summit@googlemail.com .

Follow us on Twitter @CloudOps_Summit and
Facebook http://www.facebook.com/CloudOps

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
753
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Keynote: JP Schmetz - How i learned to stop worrying and love

  1. 1. How  I  learned  to  stop  worrying   and  love  the  cloud   Cloudops     17-­‐03-­‐2011  
  2. 2. An  Epiphany  389  
  3. 3. An  Epiphany  389   Boulder  Creek  Fault  
  4. 4. An  Epiphany  389   389   Boulder  Creek  Fault  
  5. 5. An  Epiphany  389   389   Boulder  Creek  Fault   So  I  asked  for  more  informaGon…  
  6. 6. And  the  first  few  pages  of  the  presentaGon     were  pictures  of  machines  
  7. 7. To  me  it  looked  like  this  And  I  decided  to  understand  what  was  wrong  
  8. 8. What’s  wrong  with  Hardware  1.  It’s  a  fixed  asset  that  needs  to  be  planned  
  9. 9. What’s  wrong  with  Hardware  1.  It’s  a  fixed  asset  that  needs  to  be  planned   –  In  most  cases,  you  cannot  plan  for  any  Gmeframe  
  10. 10. What’s  wrong  with  Hardware  1.  It’s  a  fixed  asset  that  needs  to  be  planned   –  In  most  cases,  you  cannot  plan  for  any  Gmeframe   –  So  people  overplan  (too  many  machines,  too   many  top-­‐line  configuraGons)  
  11. 11. What’s  wrong  with  Hardware  1.  It’s  a  fixed  asset  that  needs  to  be  planned   –  In  most  cases,  you  cannot  plan  for  any  Gmeframe   –  So  people  overplan  (too  many  machines,  too   many  top-­‐line  configuraGons)   –  And  you  pay  (or  commit  to  pay)  in  advance.  Bite-­‐ size  increases  difficult  because  of  approval  
  12. 12. What’s  wrong  with  Hardware  2.  Once  the  machines  are  there  
  13. 13. What’s  wrong  with  Hardware  2.  Once  the  machines  are  there   –  ApplicaGons  and  data  will  fill  them  like  gas  
  14. 14. What’s  wrong  with  Hardware  2.  Once  the  machines  are  there   –  ApplicaGons  and  data  will  fill  them  like  gas   –  If  your  requirements  change,  machines  are   simply  unused  
  15. 15. What’s  wrong  with  Hardware  2.  Once  the  machines  are  there   –  ApplicaGons  and  data  will  fill  them  like  gas   –  If  your  requirements  change,  machines  are   simply  unused   –  You  cannot  scale  up  fast  and  you  certainly   cannot  scale  down  at  any  speed  
  16. 16. What’s  wrong  with  Hardware  3.  Once  a  machine  is  installed  
  17. 17. What’s  wrong  with  Hardware  3.  Once  a  machine  is  installed   –  You  program  and  configure  it  as  if  it  will  remain   the  same  forever  
  18. 18. What’s  wrong  with  Hardware  3.  Once  a  machine  is  installed   –  You  program  and  configure  it  as  if  it  will  remain   the  same  forever   –  SoXware  and  hardware  become  too   interconnected  someGmes  even  by  design  
  19. 19. What’s  wrong  with  Hardware  4.  There  is  NEVER  an  opGmal  to  think  or  act   differently  
  20. 20. What’s  wrong  with  Hardware  4.  There  is  NEVER  an  opGmal  to  think  or  act   differently   –  If  you  introduce  the  idea  of  cloud,  people  will   approach  as  if  it  were  alternaGve  hosGng  and   your  vendor  will  gladly  underprice  to  keep  you   hooked  
  21. 21. What’s  wrong  with  Hardware  4.  There  is  NEVER  an  opGmal  to  think  or  act   differently   –  If  you  introduce  the  idea  of  cloud,  people  will   approach  as  if  it  were  alternaGve  hosGng  and   your  vendor  will  gladly  underprice  to  keep  you   hooked   –  Your  applicaGon  developers  will  predict  mayhem  
  22. 22. What’s  wrong  with  Hardware  4.  There  is  NEVER  an  opGmal  to  think  or  act   differently   –  If  you  introduce  the  idea  of  cloud,  people  will   approach  as  if  it  were  alternaGve  hosGng  and   your  vendor  will  gladly  underprice  to  keep  you   hooked   –  Your  applicaGon  developers  will  predict  mayhem   –  As  a  compromise,  your  tech  people  (you?)  will   propose  to  build  an  internal  cloud  system…  
  23. 23. It’s  not  an  evoluGon  
  24. 24. It’s  not  an  evoluGon  •  Using  the  cloud  like  you  use  a  fixed  asset   system  will  never  yield  any  advantage  
  25. 25. It’s  not  an  evoluGon  •  Using  the  cloud  like  you  use  a  fixed  asset   system  will  never  yield  any  advantage  •  You  have  to  think  and  build  differently  
  26. 26. It’s  not  an  evoluGon  •  Using  the  cloud  like  you  use  a  fixed  asset   system  will  never  yield  any  advantage  •  You  have  to  think  and  build  differently  •  Learn  from  people  who  can  afford  to  start   from  scratch  (start-­‐ups)  
  27. 27. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)  
  28. 28. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)   cpu  
  29. 29. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)   cpu   ec2-­‐run-­‐instances  ami-­‐6138dd08  -­‐k  pstam-­‐keypair      
  30. 30. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)   ram   cpu   ec2-­‐run-­‐instances  ami-­‐6138dd08  -­‐k  pstam-­‐keypair      
  31. 31. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)  ec2-­‐create-­‐volume  –size  10   FS   ram   cpu  
  32. 32. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)   FS   ram  ec2-­‐acach-­‐volume  volume_id  -­‐-­‐instance  instance_id  -­‐-­‐device  device     cpu  
  33. 33. How  to  think  right  •  Hardware  is  soXware  (it  always  sort  of  was…)   FS   ram   queues   storage   DNS/ email   Load   cpu  
  34. 34. What  do  you  get?  
  35. 35. What  do  you  get?  •  It’s  basically  an  object  or  a  class.  
  36. 36. What  do  you  get?  •  It’s  basically  an  object  or  a  class.   –  You  can  construct  it  
  37. 37. What  do  you  get?  •  It’s  basically  an  object  or  a  class.   –  You  can  construct  it   –  It  can  do  inheritance/delegaGon  (get  the  code  to   do  your  work  from  a  repository,  assume  a  role)  
  38. 38. What  do  you  get?  •  It’s  basically  an  object  or  a  class.   –  You  can  construct  it   –  It  can  do  inheritance/delegaGon  (get  the  code  to   do  your  work  from  a  repository,  assume  a  role)   –  Get  the  data  it  needs  (from  scratch  or  cloning  it   from  another  object)  
  39. 39. What  do  you  get?  •  It’s  basically  an  object  or  a  class.   –  You  can  construct  it   –  It  can  do  inheritance/delegaGon  (get  the  code  to   do  your  work  from  a  repository,  assume  a  role)   –  Get  the  data  it  needs  (from  scratch  or  cloning  it   from  another  object)   –  ParGcipate  in  the  system  unGl  told  to  stop  or  it   crashes  
  40. 40. What  do  you  get?  •  It’s  basically  an  object  or  a  class.   –  You  can  construct  it   –  It  can  do  inheritance/delegaGon  (get  the  code  to   do  your  work  from  a  repository,  assume  a  role)   –  Get  the  data  it  needs  (from  scratch  or  cloning  it   from  another  object)   –  ParGcipate  in  the  system  unGl  told  to  stop  or  it   crashes   –  Combine  to  create  more  complex  objects  
  41. 41. Example  Search   Search  Search   Search   Search  object   object   object  object   object   1000x  
  42. 42. Example   input   sns  Search   Search  Search   Search   Search  object   object   object  object   object   1000x  
  43. 43. Example   input   sns  Search   Search  Search   Search   Search  object   object   object  object   object   1000x   load  balancer   End  user  
  44. 44. How  to  upgrade?   input   sns  Search   Search  Search   Search   Search  object   object   object  object   object   1000x   load  balancer   End  user  
  45. 45. How  to  upgrade?   input   In  a  fixed    asset  environment   there  are  two  possibiliGes:   sns    Search   Search  Search   Search   Search  object   object   object  object   object   1000x   load  balancer   End  user  
  46. 46. How  to  upgrade?   input   In  a  fixed    asset  environment   there  are  two  possibiliGes:   sns     Overplan  mode:    Search   Search  Search   Search   Search   -­‐  Upgrade  the  part  that  is  object   object   object  object   object   1000x   unused  offline   -­‐  Switch  between  versions  on   the  front-­‐end   load  balancer     End  user  
  47. 47. How  to  upgrade?   input   In  a  fixed    asset  environment   there  are  two  possibiliGes:   sns     Overplan  mode:    Search   Search  Search   Search   Search   -­‐  Upgrade  the  part  that  is  object   object   object  object   object   1000x   unused  offline   -­‐  Switch  between  versions  on   the  front-­‐end   load  balancer   Full  capacity:     -­‐  Use  the  maintenance   window  and  pray  that  it   works  out   End  user    
  48. 48. How  to  upgrade?   input   sns   In  any  case:  it’s  a  mess  +  if  not  Search   Search  Search   Search   Search  object   object   object  object   object   automated,  lots  of  manual  sys  admin   1000x   work   load  balancer   End  user  
  49. 49. How  to  upgrade?   input   sns  Search   Search  Search   Search   Search  object   object   object  object   object   dev   1000x   load  balancer   End  user  
  50. 50. How  to  upgrade?   input   sns   sns2  Search   Search  Search   Search   Search  object   object   object  object   object   dev   1000x   load  balancer   End  user  
  51. 51. How  to  upgrade?   input   sns   sns2  Search   Search  Search   Search   Search   Search   Search  Search   Search   Search  object   object   object  object   object   dev   object   object   object   object  object   1000x   1000x   load  balancer   End  user  
  52. 52. How  to  upgrade?   input   sns   sns2  Search   Search  Search   Search   Search   Search   Search  Search   Search   Search  object   object   object  object   object   dev   object   object   object   object  object   1000x   1000x   load  balancer   End  user  
  53. 53. How  to  upgrade?  input   sns2   Search   Search  Search   Search   Search   dev   object   object   object   object  object   1000x   load  balancer   End  user  
  54. 54. How  to  upgrade?   input   sns2  Total  Cost:     Search   Search  Search   Search   Search   dev   object   object   object   object  object  -­‐  Duplicate  system  for   1000x   a  few  hours  ($170/ hour)  -­‐  No  manual  labor  –   cloning  is  just  a  script  -­‐  No  risk  of  failure   load  balancer  -­‐  No  maintenance   window   End  user  
  55. 55. How  to  downgrade?  input   sns2   Search   Search  Search   Search   Search   dev   object   object   object   object  object   1000x   load  balancer   End  user  
  56. 56. How  to  downgrade?   input   sns2  Total  Cost:     Search   Search  Search   Search   Search   dev   object   object   object   object  object  -­‐  500  ec2-­‐stop-­‐ 500x   instances  calls  -­‐  Maybe  calls  to  load   balancer  -­‐  Immediate  results   load  balancer   End  user  
  57. 57. FAQ  •  Costs  –  do  you  save  money?  
  58. 58. FAQ  •  Costs  –  do  you  save  money?   –  Not  so  much  if  you  do  not  program  differently    
  59. 59. FAQ  •  Costs  –  do  you  save  money?   –  Not  so  much  if  you  do  not  program  differently   –  Massively  if  you  do    
  60. 60. FAQ  •  Costs  –  do  you  save  money?   –  Not  so  much  if  you  do  not  program  differently   –  Massively  if  you  do   •  Always  right  size  –  immediate  benefits    
  61. 61. FAQ  •  Costs  –  do  you  save  money?   –  Not  so  much  if  you  do  not  program  differently   –  Massively  if  you  do   •  Always  right  size  –  immediate  benefits   •  Never  unused  capacity  because  of  mismatches    
  62. 62. FAQ  •  Costs  –  do  you  save  money?   –  Not  so  much  if  you  do  not  program  differently   –  Massively  if  you  do   •  Always  right  size  –  immediate  benefits   •  Never  unused  capacity  because  of  mismatches   •  Never  stuck  in  dead  ends  where  you  cannot  upgrade    
  63. 63. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.    
  64. 64. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.     –  There  is  an  ownership  bias  at  work  though  
  65. 65. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.     –  There  is  an  ownership  bias  at  work  though  •  Reliability  through  soXware  
  66. 66. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.     –  There  is  an  ownership  bias  at  work  though  •  Reliability  through  soXware   –  Instances  can  take  themselves  out  of  loop  when   they  have  trouble  
  67. 67. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.     –  There  is  an  ownership  bias  at  work  though  •  Reliability  through  soXware   –  Instances  can  take  themselves  out  of  loop  when   they  have  trouble   –  Use  a  chaos  monkey  to  make  sure  your  system  is   safe    
  68. 68. FAQ  •  Reliability:   –  Cloud  service  are  not  less  nor  more  reliable  than   other  systems.     –  There  is  an  ownership  bias  at  work  though  •  Reliability  through  soXware   –  Instances  can  take  themselves  out  of  loop  when  they   have  trouble   –  Use  a  chaos  monkey  to  make  sure  your  system  is  safe   –  Assume  failure  in  the  code  
  69. 69. FAQ  •  Clusterf**k  
  70. 70. FAQ  •  Clusterf**k   –  One  Amazon  data  center  goes  down  completely  
  71. 71. FAQ  •  Clusterf**k   –  One  Amazon  data  center  goes  down  completely   –  Not  really  a  problem:  you  can  be  in  up  to  7  data   centers  at  the  same  Gme.  
  72. 72. FAQ  •  Clusterf**k   –  One  Amazon  data  center  goes  down  completely   –  Not  really  a  problem:  you  can  be  in  up  to  7  data   centers  at  the  same  Gme.  •  Clusterf**k^2  
  73. 73. FAQ  •  Clusterf**k   –  One  Amazon  data  center  goes  down  completely   –  Not  really  a  problem:  you  can  be  in  up  to  7  data   centers  at  the  same  Gme.  •  Clusterf**k^2   –  All  Amazon  data  centers  go  down  at  the  same   Gme  and  all  the  data  is  lost  forever  
  74. 74. FAQ  •  Clusterf**k   –  One  Amazon  data  center  goes  down  completely   –  Not  really  a  problem:  you  can  be  in  up  to  7  data   centers  at  the  same  Gme.  •  Clusterf**k^2   –  All  Amazon  data  centers  go  down  at  the  same   Gme  and  all  the  data  is  lost  forever   –  Somewhat  a  problem,  but  all  your  system  images   and  volumes  can  be  saved  on  site  and  reloaded   elsewhere  (e.g.  with  Nimbula)  
  75. 75. FAQ  •  Data  ProtecGon  Laws  
  76. 76. FAQ  •  Data  ProtecGon  Laws   –  Usually  the  last  (desperate)  argument  
  77. 77. FAQ  •  Data  ProtecGon  Laws   –  Usually  the  last  (desperate)  argument   –  You  can  have  data  domesGcally  
  78. 78. FAQ  •  Data  ProtecGon  Laws   –  Usually  the  last  (desperate)  argument   –  You  can  have  data  domesGcally   –  It’s  Unix  –  encrypt  the  data  you  need  encrypted  
  79. 79. How  to  get  there  •  Start  with  what  you  build  yourself  and   experiment  
  80. 80. How  to  get  there  •  Start  with  what  you  build  yourself  and   experiment  •  Try  to  expose  yourself  to  startups  and  see   how  they  do  what  they  do  
  81. 81. How  to  get  there  •  Start  with  what  you  build  yourself  and   experiment  •  Try  to  expose  yourself  to  startups  and  see   how  they  do  what  they  do  •  If  you  use  vendors  system  and  just  install  and   maintain  them,  educate  yourself  and  try  to   find  a  vendor  that  thinks  right  
  82. 82. How  to  get  there  •  Start  with  what  you  build  yourself  and   experiment  •  Try  to  expose  yourself  to  startups  and  see   how  they  do  what  they  do  •  If  you  use  vendors  system  and  just  install  and   maintain  them,  educate  yourself  and  try  to   find  a  vendor  that  thinks  right  •  If  your  revenue/job  depends  on  the   inefficiency  being  solved,  start  to  pivot    
  83. 83. Thank  you     and  Good  Luck!  

×