Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

(SCALE 12x) OpenStack vs. VMware - A System Administrator Perspective

17,278 views

Published on

By Dmitri Zimine, CTO of StackStorm (www.stackstorm.com)
SCALE 12x Conference
February 22, 2014
Los Angeles, CA

VMware has achieved broad usage, with some studies indicating that 80% or more of enterprises now use some VMware products. OpenStack, on the other hand, has quickly become the most important OpenSource community since Linux itself.

What’s it like to use OpenStack for virtualization and private cloud? And how does that compare to VMware’s solutions?

Published in: Technology

(SCALE 12x) OpenStack vs. VMware - A System Administrator Perspective

  1. 1. OpenStack  vs  VMware   A  System  Administrator   Perspec2ve     Dmitri  Zimine,  StackStorm  
  2. 2. OpenStack  vs  VMware  
  3. 3. New  tools  vs  Enterprise  Suites  
  4. 4. DevOps  for  Infrastructure  .next   •  Reliable,  repeatable,  tested  automa2on   •  Infrastructure  as  a  code   •  Good  engineering  prac2ces    Versioning,  TDD,  CI,  CD,  refactoring…   •  High  efficiency  and  agility    at  scale!  
  5. 5. Ef<iciency  boost   ITIL   Entrprs   10,000:1   100:1   Servers  per  Admin  
  6. 6. Ef<iciency  boost   ITIL   Entrprs   100:1   DEVOPS   1000:1   Servers  per  Admin   10,000:1  
  7. 7. 10x  
  8. 8. New  generation  of  tools   1.  OpenSource   2.  Support  infrastructure  as  code   3.  Leverage  social  coding  
  9. 9. #1.  OpenSource   It’s  not  about  “free”:   • Control   • Agility   • Bug?  fix  it!  Feature?  Build  it!     • Share  (see  “Social)        
  10. 10. #2.  Infrastructure  as  code     • Full  API  for  automa2on   • Defini2ons  and  configs  in  Git   • Support  TDD,  con2nuous  integra2on,   con2nuous  deployment,  refactoring…  
  11. 11. #3.  Social  coding   Engage  community     to  create    and  exchage  content   • Boosts  produc2vity   • Rewards  contributors   • Fuels    #1  and  #2  
  12. 12. New  generation  of  tools   1.  OpenSource   2.  Support  infrastructure  as  code   3.  Leverage  social  coding   4.  More  demanding  
  13. 13. Stories   OpenStack  vs  VMware,   compare  and  contrast  
  14. 14. Story  #1   Troubleshooting  
  15. 15. Story  #2   API  and  UI  
  16. 16. Story  #3   Scheduler  and  AfAinity  Rules  
  17. 17. vSphere  DRS  Af<inity  
  18. 18. Nova  Scheduler  con<ig  
  19. 19. Custom  scheduler  <ilter  
  20. 20. Story  #4   Heat  Templates     and  vCAC  Blueprints  
  21. 21. OpenStack  Heat  Template  
  22. 22. VMware  vCAC  -­‐  blueprint  
  23. 23. VCAC  -­‐  artefacts   h]ps://communi2es.vmware.com/thread/470692  
  24. 24. Story  #5   Put  it  all  together  
  25. 25. OpenStack  vs  VMware  
  26. 26. GAP   10%     OpenStack,   Devops,     DIY  tools,   Promise  of  10x   90%     VMW,   Tradi2onal  IT,   Enterprise  Suites  
  27. 27. Product  needs  to  change   •  OpenStack  becomes  Enterprise  class   •  More  like  vSphere   •  Easier  to  use  
  28. 28. Ease  of  use…  to  whom?  
  29. 29. Ease  of  use…  to  whom?   •  Depends     – Who  you  are   – What  you  know   – What  you  trying  to  do  
  30. 30. Ease  of  use…  why?   •  It’s  not  about  forcing  OpenStack     into  enterprise   – To  make  10x  more  admins  busy   •  It’s  about  bringing  Devops  to  enterprise     – And  gegng  10x  efficiency  gain  
  31. 31. 10x  
  32. 32. Horses  vs  Tractors  
  33. 33. Horses  vs  Tractors   1890  -­‐  40-­‐50  labor-­‐hours  required  to   produce  100  bushels  (5  acres)  of   wheat  with  gang  plow,  seeder,   harrow,  binder,  thresher,  wagons,   and  horses   1930  -­‐  15-­‐20  labor-­‐hours  required   to  produce  100  bushels  (5  acres)   of  wheat  with  3-­‐bo]om  gang   plow,  tractor,  10-­‐foot  tandem   disk,  harrow,  12-­‐foot  combine,   and  trucks    
  34. 34. Horses  vs  Tractors   40-­‐50  labor-­‐hours   15-­‐20  labor-­‐hours    
  35. 35. Horses  vs  Tractors   4x  
  36. 36. Devops  promise?   10x  
  37. 37. •  Vendors:  stop  building  horse  wagons   – Because  they  are  “easy  to  use”   •  Sys  admins:  learn  to  drive  tractors   – even  if  are  clumsy:  driving  is  good  skill  
  38. 38. Products  DO  need  to  change   •  Power  tools  for  power  users   •  Support  Infrastructure.next  and  devops   •  VMWare   •  Cisco,  EMC,  NetApp,  BMC,  F5…   •  Or  else…  
  39. 39. OpenStack  and  vSphere  at  PayPal   Source:  "Marriage  of  Openstack  with  KVM  and  ESX  at  PayPal"     OpenStack  Hong  Kong  2013,  h]p://bit.ly/1bmw0qY    
  40. 40. Sys  admins  need  to  change   •  Power  tools  require  power  users   •  Pick  new  skills,     Or  else  …  
  41. 41. THE  BIGGEST  WINNERS:     STARS  AND  SUPER  STARS     One  machine  can  do  the  work  of     <ifty  ordinary  men.     No  machine  can  do  the  work     of  one  extraordinary  man.      -­‐  Elbert  Hubbard  
  42. 42. Automation  keeps  the  best  part   •  More  demanding     •  More  crea2ve   •  More  fun  
  43. 43. SUMMARY  
  44. 44. Transformation   •  Main  drivers:  efficiency  and  agility   •  “Devops”  movement  shows  how  to  get   there   •  Products  will  support  “devops”,  or  die   •  Sys  admin  job  will  change  –  demanding,   crea2ve,  fun  
  45. 45. Winners   •  Vendors  who  got  it  right   •  Star  and  super  star  sys  admins  
  46. 46. Shape  your  world   The  best  way  to  predict  the   future  is  to  create  it      -­‐  Abraham  Lincoln  
  47. 47. We  want  to  hear  from  you   •  VMware    -­‐  PMs,  Customer  Advocacy   •  Openstack  developers   •  Startups  like  us  -­‐  @Stack_Storm     •  Me  -­‐  dz@stackstorm.com  
  48. 48. Discussion  
  49. 49. References   •  Infrastructure  as  code,  detailed  slideshare  on  comparing  coding  vs.  infra   as  code  by  Patrick  Debois h]p://www.slideshare.net/jedi4ever/code-­‐but-­‐not-­‐as-­‐we-­‐know-­‐it-­‐ infrastructure-­‐as-­‐code   •  Blog  on  Infrastructure  as  code  vs.  automa2on  from  Kiel  of   Thoughworks: h]p://kief.com/infrastructure-­‐as-­‐code-­‐versus-­‐automa2on.html       •  Mistral:    h]ps://wiki.openstack.org/wiki/Mistral   •  Ken  Hui  of  Rackspace  on  VMware  and  OpenStack:    h]p://cloudarchitectmusings.com/2014/01/23/bridging-­‐the-­‐gap-­‐ explaining-­‐openstack-­‐to-­‐vmware-­‐administrators-­‐the-­‐talk-­‐track/  s   •  Servers  per  admin  stats  -­‐  for  instance,  here:     h]p://www.computerworld.com.au/ar2cle/352635/ there_best_prac2ce_server_system_administrator_ra2o_/  

×