Once upon a time…not soo long ago…
“NEW ORLEANS, May 6, 2003 — In his keynote address today at the 12th annual Windows® Hardware Engineering Conference (WinHEC), Bill Gates, chairman and chief software architect at Microsoft Corp., will showcase a concept of a Dynamic Data Center (DDC)”
I remember hearing about it for the first time, and thinking WOW…wouldn’t that be something…Imagine designing a system, with a tool (like visio)…designing your application along with the infrastructure integration and right clicking…and sending to production.
Almost decade later, I was able to build one ( a Dynamic Data Center) in only 24 hours…well, ok…it was actually 3 days ( 8 hours at a time…) but after those 24 hours (3 Days) we had a full, state of the art “Dynamic Datacenter” (aka = DCS) up and running!
The DCS reference architecture and reference implementation are blueprints for designing and implementing customized DCS solutions. Both were developed by a worldwide team of Microsoft Consulting Services (MCS) experts on Windows Server, System Center, and Forefront technologies. The reference architecture and reference implementation are designed to accelerate deployments, ensure quality and consistency of delivery, and simplify account planning and engagement scoping.
A few terms to know..
The Datacenter Services Solution is built using the Hydration v5 Framework. The framework is a lightweight scripting engine built on the Microsoft Deployment Toolkit 2010 Update 1. It allows for the building and sharing of Hydration Packs which define configuration and installation scripts for groups of products that make up a service. It also provides mechanisms to validate known-good configurations that are deployed using task sequences.
The fabric is all infrastructure and systems under the scope of control of the reference architecture. The fabric can consist of multiple sites and datacenters.
Sites / Datacenters
A physical location or site housing one or more resource pools.
A resource pool is comprised of server, network, and storage scale units that share a common hardware and configuration baseline but does not share a single point of failure with any other resource pool (other than the facility itself). Note that a resource pool could be subdivided further into Fault Domains with the definition of a fault domain being a group of physical infrastructure with a common configuration that doesn’t share a single point of failure with any other fault domain. For simplicity, in our solution a resource pool and a fault domain are equivalent.
A scale unit is a set of server, network, and storage capacity that is deployed as a single unit and is the smallest unit of capacity deployed in the fabric. Depending on the customer size, a scale unit may be a 4-node Hyper-V cluster or a full rack of 64 blade servers. It is typically sized as the average new capacity required quarterly in the environment. So rather than deploy a single server at a time, when additional capacity is needed, a new scale-unit is deployed to meet the need and leave room for the remainder of the growth anticipated in the quarter.
Private Cloud IaaS is an advanced state of IT maturity that has a high degree of automation, integrated-service management, and efficient use of resources. Virtualization can be a key enabler of IaaS but in most models, including the NIST cloud definition, virtualization as common, not and essential, attribute.
An infrastructure that is 100 percent virtualized may have no process automation; it might not provide management and monitoring of applications that are running inside virtual machines (VMs) or IT services that are provided by a collection of VMs. In addition to virtualization, several other infrastructure-architecture layers are required to achieve the essential cloud attributes.
A rich automation layer is required. The automation layer must be enabled across all hardware components—including server, storage, and networking devices—as well as all software layers, such as operating systems, services, and applications.
The Windows Management Framework—which comprises Windows Management Instrumentation (WMI), Web Services-Management (WS-Management), and Windows PowerShell—is an example of a rich automation layer that was initially scoped to Microsoft products, but that is now being leveraged by a wide variety of hardware and software partners.
A management layer that leverages the automation layer and functions across physical, virtual, and application resources is another required layer for higher IT maturity. The management system must be able to deploy capacity, monitor health state, and automatically respond to issues or faults at any layer of the architecture.
An orchestration layer that manages all of the automation and management components must be implemented as the interface between the IT organization and the infrastructure. The orchestration layer provides the bridge between IT business logic, such as "deploy a new web-server VM when capacity reaches 85 percent," and the dozens of steps in an automated workflow that are required to actually implement such a change.
The IaaS solution’s primary purpose is to host other layers such as the PaaS and SaaS.
The final layer is the user interface layer providing interfaces for both service providers and service consumers.
This is what the Core architecture looks like….
And a Few Shots from my Build….
Server Manager and VMM….
CPUs and RAM….
The Datacenter Services Basic Portal…
Assigned Quota Units out of the overall 100 units available on the Resource Pool…
I love these provisioning portals…this is where almost anyone can ask for a machine…here they can choose from a predefined template…small, medium, large….or silver, gold…whatever makes sense…
Choosing where and which….
As you can see, we are moving rapidly towards Dynamic Datacenters…with advanced portals…you’ll see more and more of templates and Services that can be automatically deployed to the datacenter….and can scale…up and out…
This is one cool example that not only is simple…but also worked amazing…(note: This is a different system…not the DCS that I built…)
Once you choose your template and what you want on it…the magic starts!
For those wondering….DCS 2.0 (Next Generation Aka: ….(Windows 8 and System Center 2012)…)….is right around the corner….
I hope you enjoyed this intro and my experience with today’s DCS….We all know that we are just at the beginning and I am super excited about this evolution!!