Mastering Windows Server 2016 Hyper-V

(Romina) #1

Chapter 9: Implementing the Private Cloud, SCVMM, and


Microsoft Azure Stack


Explain the differences between virtualization and the private cloud.
Virtualization enables multiple operating system instances to run on a single physical
piece of hardware by creating multiple virtual machines that can share the resources
of the physical server. This enables greater utilization of a server’s resources,
reduction in server hardware, and potential improvements to provisioning processes.
The private cloud is fundamentally a management solution that builds on
virtualization but brings additional capabilities by interfacing with the entire fabric,
including network and storage, to provide a complete abstraction and therefore
management of the entire infrastructure. This allows a greater utilization of all
available resources, which leads to greater scalability. Because of the abstraction of
the actual fabric, it is possible to enable user self-service based on their assignment to
various clouds.


Master  It  Do  you need    to  change  your    fabric  to  implement   the private cloud?
Solution Typically, no. Provided your storage supports SMI-S to enable it to be
communicated to and from SCVMM and your compute and network resources
meet your needs in terms of your desired levels of capability, there should be no
need to change the actual fabric—only the management will change.

Describe the must-have components to create a Microsoft private cloud.
The foundation of a Microsoft private cloud solution comprises virtualization hosts
using Hyper-V and then SCVMM and Windows Azure Pack to provide the core fabric
management, abstraction, cloud creation, and end-user self-service functionality.
Orchestrator and Service Manager can be utilized to build on this core set of private
cloud functionality to bring more-advanced workflows, authorization of requests, and
charge-back functionality.

Free download pdf