Issue link: https://insights.oneneck.com/i/1293607
20 Containers For Dummies, HPE and Docker Special Edition These materials are © 2017 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. Want to change hypervisors? No problem! A hypervisor change is a huge pain in the neck! It's one of the reasons they don't happen often. But, when they do, you have to convert each and every virtual machine to the new virtual machine format and migrate to the new platform. Some downtime is more than likely as a result. Most organizations can handle a little bit of downtime, but many can't, and the kind of disruption imposed by essentially ripping and replacing underlying virtual infrastruc- ture can be significant. That said, there are often really desirable cost incentives to con- sider a hypervisor change, particularly because the leading hyper- visors at this point have practically the same features and general capabilities. HPE IT: OR MAYBE NO HYPERVISOR AT ALL! Docker containers can run on bare metal just as easily as they can on a hypervisor. Data center architectures can help bring to these bare- metal deployments the kind of flexibility that is often considered the sole purview of virtualization. Sean Sargent and Elliot Berg, Solutions Architects at HPE Pointnext, HPE's consulting arm, have deep experience with emerging data center architectures. Interviewed for this book, Sargent and James indicated that HPE has "invested in things like the composable infra- structure API that was exposed to HPE's OneView management tool. We found that if we use OneView, we can remove things such as the hypervisor from our configuration, and run Docker native platforms on our bare-metal infrastructure. We still get a virtual machine–like experience for provisioning and managing. And for the parts that OneView doesn't have, like object store and DNS as a Service, or load balancer service, we can leverage the components from those from other APIs, such as Helion OpenStack."