1
Annex 9: Private Cloud Specifications
The MoICT Private Cloud Solution is based on the Data Center Services (DCS) offering from CMS. DCS is comprised of a fabric in the form of one or more resource pools (clustered hosts running a supported hypervisor) and a fabric management component (System Center 2012 and associated products). A high level view of this relationship is provided below.
Figure1: High-Level DCS Component Relationships
While the implementation of each architecture varies based on the size, resource pool make-up (and versions), number of physical locations and workloads running within the DCS environment, the solution provides comprehensive IaaS services in a single architecture.
Fabric Management
DCS provides out-of-box (OOB) System Center virtualization infrastructure management capabilities with the core System Center products installed as part of the solution. The following products are leveraged within the Solution:
Cloud Services Process Pack
System Center Service Manager 2012 System Center Operations Manager 2012 System Center Virtual Machine Manager 2012 System Center Orchestrator 2012
2 Virtual Machine Manager
DCS requires System Center Virtual Machine Manager 2012. Two (2) SCVMM servers will be deployed and configured in a failover cluster during hydration using a dedicated SQL instance on the DCS virtualized SQL cluster.
Operations Manager
DCS requires System Center Operations Manager 2012. Two (2) servers will be utilized – one supporting up to 3000 OpsMgr agents and one providing high availability.
Operations Manager Installation uses a dedicated SQL instance on the DCS virtualized SQL cluster. The installation will follow a “split SQL configuration”:
SQL Server Reporting Services (SSRS)
OpsMgr components will reside on the OpsMgr VM Service Manager
DCS requires System Center Service Manager 2012. DCS installs the Service Manager Management Server on two virtual machines. A third virtual machine hosts the Service Manager data warehouse server. Both the Service Manager database and the data warehouse database use a dedicated SQL instance on the DCS virtualized SQL cluster. The Service Manager portal is hosted on a fourth system with the DCS Portal.
Orchestrator
DCS requires System Center Orchestrator 2012 and the System Center integration packs for Orchestrator. The Orchestrator installation uses a dedicated SQL instance on the DCS virtualized SQL cluster.
DCS hydrates two Orchestrator Runbook servers for High Availability and scale purposes. Orchestrator provides built in failover capability (it does not use failover clustering!). By default, if an Orchestrator server fails, any workflows that were running on that server will be started (not restarted) on the other Orchestrator server. The other reason two Orchestrator servers are deployed by default is for scalability. By default each Orchestrator Runbook server can run a maximum of 50 simultaneous workflows. This limit can be increased depending on server resources, but an additional server is hydrated to accommodate larger scale environments.
Data Protection Manager
System Center Data Protection Manager (DPM) 2012 is not hydrated by default in DCS v2.0 however it is installed and configured as part of a DCS solution. DPM enables VM level backups, while with customization file-level back-up will be implemented. To enable DPM, the DPM agent is installed in each desired VM and a protection group created for each. The DCS portal then can enable VM self-service file recoveries.
Configuration Manager
3 Server is installed to handle the inventory, software distribution and software metering. Redundancy is accomplished through the Hyper-V cluster.
DCS Portal Server
DCS provides a dedicated portal interface to expose System Center functionality and allow for provisioning and management of IaaS resources. The Cloud Service Process pack in the Foundation and Advanced configurations is utilized to support out-of-box functionality with respect to IaaS management.
This solution is illustrated in the diagram below with the servers/technologies hydrated by DCS 2.0;
Figure 2:DCS 2.0 General Architecture
Fabric
4
Figure 3:How Hyper-v nodes interconnects
As illustrated above, all physical servers have 4 NICs each.
HP Virtual System VS2 Solution for Microsoft [QTY:1]
Rack HP 42U 1075mm i-Series Shock Rack: HP 10K Rack Airflow Optimization Kit HP 42U 1075mm Side Panel Kit
virtualization host One (1) HP BLc7000 3 IN LCD ROHS Enclosure:
6X 2400W Platinum Efficiency FIO Power Supply bundle 6x HP Active Cool 2000 Fan Bundle
(2) HP c7000 Onboard Administrator with KVM Option (6) HP ProLiant BL460c G7 Server
(12) HP BL460c G7 Intel® Xeon® X5675 (3.06GHz/6-core/12MB/95W) FIO Processor
(72) HP 16GB 4Rx4 PC3-8500-R-7 R-DIMMs (192GB per server) (12) HP 146GB 6G SAS 15K 2.5in DP ENT HDD
Management Station Two (2) HP ProLiant DL360 G7 Server:
(16) HP 8GB 2Rx4 PC3-10600R-9 STD RDIMMs
(4) Intel® Xeon® X5675 (3.06GHz/6-core/12MB/95W) Processors (2) HP 1GB Flash Backed Cache
5 (4) HP 460w CS Platinum Power Supply Kit
(2) HP Integrated Lights-Out 3 (iLO 3) Advanced
HP Virtual Connect (1) HP Virtual Connect Flex-10 10Gb Enterprise Edition for BladeSystem c7000 Individual SAS
interconnect PN
(2) HP 3Gb SAS Switch BladeSystem SAN Solution for
BladeSystem
(1) HP P4800 42TB SAS SAN Solution for BladeSystem Switches (2) HP A5820-24XG-SFP
