1 / 9

Hawaii Data Center Transition Update

Hawaii Data Center Transition Update. 22 May 2014. A Quick Refresher…. Current State Environment. Permanent State. Tactical Enhancements. High Speed connectivity between DR Fortress, Systemmetrics, MRTC and Kalanimoku.

truong
Download Presentation

Hawaii Data Center Transition Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hawaii Data Center Transition Update 22 May 2014

  2. A Quick Refresher… Current State Environment Permanent State Tactical Enhancements High Speed connectivity between DR Fortress, Systemmetrics, MRTC and Kalanimoku State IT assets spread across 27+ departmental and ICSD data centers on Oahu Most State system housed in highly robust Tier 3 data center located away from likely disaster zones. Network Enhancements Judiciary Department data centers Primary DC (Oahu) Secondary DC (Maui) Satellite DC’s on NI’s DOE Kalanimoku Building Ready by July 2014 DR Fortress System Metrics MAUI MRTC Overflow Capacity for Kalanimoku and Dept DC’s Relocating Network Hub • The tactical moves provide some capacity and disaster recovery capabilities, affording minor risk mitigation until the permanent strategy can be implemented • Building the Virtualized environment at Kalanimoku with disaster recovery capability at DR Fortress • Contracting with the two island co-location facilities to provide overflow capacity in light of future system needs • Refurbishing Maui Research Technology Center to use for rudimentary disaster recovery • Enhance network connectivity with co-location providers and MRTC

  3. Planned Attributes of Hawaii’s Private Cloud Self-Service Interface • Portal (GUI or API) • Service-level requirements, actuals Operational Process Automation • Incident & Problem management • Change management • Provisioning and configuration management • Performance management and optimization Automation of Service Delivery • Service provider • Usage management and chargeback Automation of Resources • Provisioning • Migration/motion • Allocation/de-allocation Government Private Cloud Resource Virtualization • Virtual servers, operating systems, storage and network,

  4. Hawaii’s Private Cloud Services Once fully implemented, Hawaii’s Government Private Cloud will provide a standardized, self-service ‘shopping cart’ experience EXAMPLE ONLY Windows 2012 6.x

  5. Future Roles & Responsibilities • Patching will only be done for customers that have standardized (i.e. Windows 2012/Redhat 6.x) services • Customers who conduct P2V migrations to the virtual environment will be required to perform the above function

  6. Where are We Now? Real-Time Infrastructure We are here Sprawled Virtualized Automated Cloud- enabled Optimization Workloads Data Resources Identities Department Data Centers Provisioning Availability Asset, power costs down, flexibility up Service levels and agility up

  7. The GPC Project Plan - Crawl, Walk, Run Step 1: Build virtualized infrastructure at Kalanimoku (KB) as the primary location and establish back up capability at DR Fortress (DRF) Step 2: Begin migrating critical department workloads over to the virtual environment and alleviate risk of failures Step 3: Establish true Cloud services with self service, service catalog and chargebacks, • Continue migrations and stand up of new VM’s for departments • Establish self-service capability • Establish service catalog and chargebacks to departments • DR Fortress will become primary location, with Maui becoming backup/redundant location • Develop Service Management processes and SLA’s • Develop process for physical-to-virtual (P2V) and virtual-to-virtual (V2V) migrations • Develop applications prioritization and Migration Plan • Conduct Migrations • Stand up new Windows 2012 & Redhat 6.x VMs as requested • Establish some disaster recovery capability at DR Fortress • Install IBM Flex architecture in KB & DRF - COMPLETE • Conduct pilot migrations • Stand up new Windows 2012 & Redhat 6.x VMs as requested - COMPLETE • Begin department-by-department needs assessment for potential use of Cloud - STARTED April-June 2014 June-December 2014 2015 -

  8. Departmental Outreach and Collaboration We’ve already started meeting with Departments to identify initial requirements… Step 1: email the OIMT Cloud Team and set up a meeting Step 2: Complete and send the Cloud Scope Capture Sheet Step 3: Meet with the Cloud Team and determine best approach for migrating workloads into the virtual environment Cloud Scope Capture Sheet Departments that have completed Requirements Meetings

  9. We want to hear from you – oimt.cloud@hawaii.gov

More Related