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.

Using OpenStack to Control VM Chaos

323 views

Published on

Slides from a webinar that I and Dell Virtualization Evangelist Hassan Fahimi gave in March 2016. We provide a complete overview of OpenStack and Foglight for OpenStack.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Using OpenStack to Control VM Chaos

  1. 1. Using OpenStack to control your VM chaos David Strom and Hassan Fahimi Redmond Magazine Webinar 3/16
  2. 2. Who are we? David Strom, author and speaker Hassan Fahimi, Sr Product Manager, Dell
  3. 3. Agenda • Status report on OpenStack • Advantages and disadvantages • Who is using it and why • Deployment strategies and issues
  4. 4. What is OpenStack now? OpenStack is a single, open source platform for management of the three major cloud compute technologies; virtual machines, containers and bare metal instances.
  5. 5. OpenStack advantages
  6. 6. Quick deployment of your VMs
  7. 7. Self-service for your developers
  8. 8. Who is using it?
  9. 9. How much time does it take to deliver a new VM? • Developers need to be able to understand and then write stateless applications for the cloud • Also understand the differences between private clouds and ordinary VMs • Pair Java developers with sys admins
  10. 10. Big boosters
  11. 11. OpenStack core services
  12. 12. What is new in Liberty release? • Extensible Nova compute scheduler • Defined network QoS framework • Enhanced load balancing as a service • Magnum – better container mgmt. service • Heat orchestration enhancements such as role-based access controls
  13. 13. Issues still remain • Documentation is spotty once you get past the easy stuff • It is all about VMs. Don’t make this your first virtual rodeo • Neutron and software-defined networking support is still young and restless • Keeping up with release schedules can be brutal • OpenStack won’t replace your PaaS
  14. 14. Lots of deployment decisions • When to deviate from pure OpenStack code • What enhanced features make sense • Know the costs, your budget, staffing, skill sets • Get right vendor training and support • Understand remote management issues • Where to locate your cloud environment • Which OS projects/release to implement
  15. 15. One typical OS team • 2-3 system architects • 3-5 sys admins with Linux/ FOSS experience • Friendly network infrastructure team • Developers who know the cloud • C-level buy in
  16. 16. Next steps • Attend the next summit conferences • Keep up with the latest code releases • Understand the community and don’t fight city hall • There will be bugs, (don’t worry, be happy!)

×