Data Center Cloud Consolidation -1-

Transcription

1 Data Center Cloud Consolidation -1-

2 About RDS RDS is a vendor and technology neutral company, we test and evaluate the best and most secure technologies available today from the leading manufacturers. We customize each solution to meet our customer s unique requirements, making RDS a single source for choosing and implementing the best solutions to your most challenging problems. Our customers have relied on us to provide single source solutions since 1996.

3 Our Partners Our promises are real. Today, we have a growing list of deployments at prominent corporations and partners, including the ones shown below.

4 Overview Vision Objectives Strategies RDS strives to be one of the premier storage solutions designers in the network storage industry. To serve as an integrator to our clients by bringing hardware and software together into a seamless and viable solution. Cultivating longterm customer focused relationships. To leverage industry expertise and solve current integration needs by offering: Business Continuity Services Data Management Services Consolidation and Migration Services Networked Storage Services Consulting and Residency Services.

5 Our clients

6 Our clients

7 Why Cloud? Our Cloud methodology helps you to meet your business demands for ever-increasing speed, agility, and cost savings by providing effective tools for managing IT in a new cloud-based paradigm. Regardless of the type of cloud environment you deploy (private, public, hybrid, or a cloud bursting model), there are two foundational pillars that form the basis of successful cloud computing initiatives. Our compute platform provide both pillars - a web-based, self-service portal with an automation orchestration engine and a compute platform that is built from the ground up with the ability to be orchestrated. The solution has the following key attributes which are critical to the success of a development cloud deployment. Improving time to operational value: A shorter time is required to build the solution due to fewer elements, pre-integration, and a modular non-coding approach to content definition. A simple workflow takes 5 to 10 minutes to complete versus days in competing solutions. -7-

8 Why Cloud? (continued) Enhancing coverage and flexibility: The solution includes an industry-leading, comprehensive service catalog with strong ITIL support, governance policies over service consumption, and open standards Portlet integration. It works with any hardware and virtualization product in the market, as well as any management framework. In addition, it goes beyond simple provisioning cloud services to automation of the entire spectrum of operation processes for runtime production operation of cloud services and infrastructure. It also automates ongoing maintenance, health checks, incident management, compliance, capacity management, footprint optimization, and so on. Enriching user and administrator experience: Our Cloud methodology offers the market s best end-user storefront interface. It is easy to configure and operate workflows. Detailed automation summaries keep administrators in control and accountable -8-

9 Why Cloud? (continued) Reducing TCO: This right-size solution provides a core service automation stack (catalog, orchestrator) that works with existing ticketing systems, CMDB, resource managers, and infrastructure from any vendor. It does not force you to buy the entire portfolio but gives you the flexibility to buy what you need when you need it, from vendors you prefer with the capacity to grow as you grow. In addition, it offers a low license price compared to typical competition pricing. Our computing platform provides a highly available and flexible environment based on current Intel technology. RDS has been in this service industry for a long time, in this system integration efforts in recognizing that the in addition to a strong Service Catalog / Orchestration Engine offering. There has been a need in the industry for a compute platform that is designed from the start be orchestrated. -9-

10 Why Cloud? (continued) In response to this industry need, Cisco developed the Unified Computing Platform with the attributes listed below which enable pools of resources in a cloud to be deployed cost effectively within minutes and according to rapidly changing requirements for both virtualized and non-virtualized servers. Stateless Computing with Service Profiles-This capability abstracts the attributes of each server blade and essentially virtualizes the bare metal server underneath the hypervisor or single OS, allowing deployment of bare metal servers with the same ease as a virtual server. Unified Fabric- Provides every server in the system high I/O access to SAN, NAS or iscsi storage as needed within minutes without a separate storage network. Virtualization Aware Networking Enables the virtual; adapters to be assigned to individual virtual machines providing full network visibility to individual VMs. -10-

11 Why Cloud? (continued) Virtual Adapter Technology Allows the addition of up to 256 virtual Ethernet NICS and/or HBAs within minutes without adding additional hardware making the number of adapters in a system a boot time decision rather than an ordering time decision. Extended Memory Technology Cost effectively extends the memory available for two socket servers for application where memory rather can CPU is the key bottleneck (such as VDI). Single Point of Management Provides an GUI interface allowing all components within the compute system to be orchestrated as a whole according to predefined policy. -11-

12 Our template on (Gartner s) approach to a Cloud solution Exploratory Initiatives Strategic Planning Automation Disaster Recovery Project Initiatives Data Center Consolidation Server/Storage Virtualization Infrastructure Convergence Cloud Computing Negotiating Vendor Contracts Vendor Management Cost Optimization Infrastructure & Operations Maturity Reference: Gartner Report IT I&O Key Initiatives: Why, How and Who Publication Date : 3 May 2010

13 Server Computing Platform Overview Server virtualization impacts critical imperatives: (1) costs are lowered by the higher utilization rates achievable as compared to non-virtualized environments; (2) service reliability is improved by clustering and making I&O more manageable; and (3) agility is improved by the ability to respond more rapidly to workload levels. Virtualization Reference Architecture Two physical sites A total of ten (10) clusters consisting of thirty-two (32) ESX hosts Load balancing and VMware High Availability included One vcenter Server per site

14 Server Design Framework New Server infrastructure will be highly virtualized to facilitate cloud model ensuring rapid provisioning, resource pooling and high availability characteristics. Considerations Migrate from physical to virtual platform with same or better performance Align to the cloud computing model capable of dynamically allocating system resources Develop highly available server computing platform Maximize density and minimize power consumption All physical servers including ESXi hosts should boot from SAN Assumptions New hardware for server virtualization compute systems for Production and DR mirror systems to ensure a highly available environment SAN based storage platform with data replication between primary and secondary data centers Network design based on Cisco Nexus switches with capacity for 10GbE connections, fully redundant within the datacenter, and is resilient and capable of supporting N+1 failures Test and Development systems to be located in the second datacenter, and will utilize separate storage systems. Test systems to be repurposed as Production systems in the event of DR -14-

15 Storage Design Framework Storage consolidation, virtualization and optimization will provide significant savings. Strategic sourcing of enterprise solution, including storage, data replication, backup and recovery will further savings. Considerations Affordable, elastic storage, backup/recovery, and disaster purpose Implement Storage Virtualization Increase Storage Utilization and improve Hardware Utilization Allow online Data Movement Based Upon Business Value of Data Reduce Reliance on Higher Costs Tiers Provide capabilities for automation of manual tasks Consolidate Storage devices Reclaim trapped storage Reduce disc in reserve capacity on subsystems and on servers Automate Storage Optimization Implement dynamic tiering for data mobility across virtual storage tiers Reduce storage needs by elimination of redundant data using De-duplication techniques Reduce data backup time by archiving stale data out of the primary backup set Provide 3D scaling storage architecture to scale up, scale out and scale deep Optimize Backup/Recovery Implement Virtual Tape Library Backup to Cloud (Cloud storage service providers include Amazon Web Services, AT&T, Iron Mountain and Nirvanix) -15-

16 Storage Design Framework SAN Considerations Upgrade to Director Level Switches such as (CISCO s MDS or Nexus 3K, 5K, or 7K switches). Let us take CISCO Switches for example. MDS9509 s or NX 3K, 4K, 5K for Host Edge and Storage Edge which can support FCOE. MDS9513 or the NX 7K to function as Core switch and support Enterprise backup solution and DR platform setup Proposed Director level switches have advanced features for creation of virtual storage area networks for different environments for example Production, Test and Dev. Backup device can connect to Core switch and support enterprise backup/recovery of data stored in local drives or SAN devices -16-

17 Cloud Storage Platform Storage Low-cost, custom-built modular scale-out storage. Suggested use a mix of customdesigned and branded hardware, leverage existing data center investments. Design driven by optimization and innovation in our cloud storage environment with a focus on keeping costs down while simultaneously catering for near-unlimited capacity scaling based on customer demand. There are examples of leading "commodity" cloud storage providers shunning purchases of traditional branded storage arrays and opting to head down the innovation route. Amazon is a case in point, having validated this market early by offering Internet Protocol-based access to clusters of DAS; it claims to have designed its entire infrastructure (not just storage) from the ground up. Low-cost, custom-built, scale-out commodity storage hardware is strongly suited for large-scale cloud deployments, providing extreme scalability at low price points. While this approach offers high scalability at very low price points, it requires a significant amount of technical expertise and R&D investment, and continuous monitoring and design. The newer generation of scaleout architectures and/or object-based storage platforms, in which, the focus is on low-cost scalability. Integration of deduplication-enabled backup software/appliances, such as Symantec NetBackup and Commvault Simpana. Introduction of cloud storage gateway appliances (aka controllers or accelerators) can compress and deduplicate data on the way to the public-cloud storage environment and also make the internal data center agnostic to the architecture at the public-cloud provider location. -17-

18 Private Cloud Infrastructure Convergence Server virtualization impacts critical imperatives: (1) costs are lowered by the higher utilization rates achievable as compared to non-virtualized environments; (2) service reliability is improved by clustering and making I&O more manageable; and (3) agility is improved by the ability to respond more rapidly to workload levels. Features Powerful APIs for automation and customization Billing integration Multiple users and ACL for each organizations Dedicated portal views at every level Resource metering and usage accounting Automated fault tolerance Intelligent workload scheduling Integrated secure console access Scalable Design Thin Provisioning Fault Tolerance Design Principles Built on low-cost commodity hardware Built with multi-tenancy and tiered delivery Should be open and interoperable Fault tolerance should be inherent in the system Self-service driven by on-demand provisioning of CPU, RAM and Network Conform to existing business models -18-

19 RISK Management Consolidation of servers and storage at the strategic sites while virtualizing servers during the migration has minimal risk to the availability of the business function. Final cut-over of applications will be planned with failback options thoroughly tested. # Risk Mitigation Probability Impact 1 Migration to new datacentre facility may causes degradation of performance for some application due to network latency 2 Hard coded IP Address being embedded within applications application configurations 3 Storage devices damaged during the physical move 4 Slower than expected data migration over WAN to the new facility could prolong migration and/or problematic data migration Use WAN Optimization appliances to increase performance Use DNS Naming methodology to resolve Name to IP Address Back up all data before moving storage to leased storage devices Use reliable data replication appliances for migration 5 Upgrade during the migration process Freeze application upgrades during the migration process 6 Current staff s lack of expertise of new cloud computing platform Training requirements will be identified to prepare SJHS staff for day 1 support Medium Medium Low Medium Low Medium High High High Medium Medium Low 7 Likelihood of additional space being unavailable within the same co-location facility in a few years Lock-in growth space for near future and/or ensure right of first refusal clause in the contract with the service provider, whereby you would have the option of locking-in the last space before it was leased to someone else. Low Low -19-

20 Migration Plan A Low level step by step approach on how migration needs to be performed on the infrastructure (Server & Storage). Migration Approach Virtualize & Consolidate in flight Description Pros Cons Virtualize during moves Virtualize over the WAN 30% to 40% system reduction Utilizes virtual infrastructure within strategic site Greatly reduced physical complexity: systems & ports No hardware failure risk for VM Simple back-out (return to physical device) Single wire migration option Large project cost / time risk Time intensive Physical to virtual (P2V) copy Guidelines Boot from SAN for all open systems from the mirrored devices (replicated devices) as against local SAN devices. Re-cycle/reuse servers from existing Regional Datacenters (Prod) and install them in DR (PHX). Process controls should be set in place to incorporate in the Change management process to concurrently deploy/implement O/s & Application Upgrades in production and DR. Implementation Approach New hardware will be installed at the primary and the secondary data centers. Implement HDS s VSP to virtualize the storage platform to manage a multivendor storage arrays. Storage migration appliance. (tools such as (Ope Replicator, SAN Copy, Viacom DME, CISCO s DMM) VMware images of the existing 3.X & 4.X Versions of servers located and migrated to VMware 5.x platform at new primary and secondary sites. -20-

21 ?Questions

22 Thank You