1. HUIT Cloud Initiative Update November, 2013 11/20/2013 Ryan Frazier & Rob Parrott

2. 2 Initial Harvard Cloud Strategy 2.5+ core FTEs + other supporting Draw from existing staff across HUIT (Infrastructure, ATS, CTO) Partner with Schools, particularly in RC and Academics Use ITCRB Funding to help with start-up Review at 6 months for progress & effectiveness Create Cloud Services Team (kick-off 8/26/13) Focus on Key Areas Address key use cases (Dev/Test, RC, Innovation/Sandboxes) Heavily leverage Amazon Web Services to start Evaluate supporting technologies and services Provide education and outreach to Harvard Support early adopters (Public websites, etc.) Integrate with Existing Initiatives Enterprise Architecture New application selection/development Organizational, process & operational changes Leverage strategic partnerships

3. 3 Key Deliverables: Year 1 (FY14) DeliverableDescriptionStatus (11/2013) Amazon Web Services for Harvard (*) General purpose cloud capability through Amazon Web Services, with enterprise agreement and billing enhancements. (8/2013) ✔ Harvard RC Cloud Cloud capabilities for research and teaching at Harvard. (Fall 2013 pilot) Delayed Hardware and networking nearly in place HUIT Testbed Cloud In house capability for cloud IaaS that is compatible with AWS. (Fall 2013 pilot) Delayed NOC lab currently used, hardware + networking pending Webroots PaaS An Webroots-like environment that provides a cloud “platform-as-a-service” capability to Harvard. (Winter 2014) Planned Cloud tools Adopt and develop tools needed to ease adoption of cloud (Fall 2013 & ongoing) In Development (Accelerated) Education, outreach and support Resources and support structures for early adopters, including ABCD cloud group, communities of practice around cloud, and online resources. ✔ >5 Amazon trainings ✔ cloud.huit website ✔ active consulting activities

4. 4 Other Activities: Supporting HUIT Cloud Adoption ProjectDescriptionStatus (11/2013) HPAC Website Migration to AWS Migrate HPAC websites from Rackspace to AWS (www.harvard, gazette.harvard, others) w/ support from HWP Active development Targeting Jan ’14 cutover LTS Innovation Pilot use of AWS for Library Lab Innovation Projects using Ruby on Rails Working with LTS to create reference implementation IAM ProgramUtilize AWS for IAM Program Multiple efforts with Cloud Engineering, Security, Infrastructure, and AWS resources Data Center Cloud Integration Integrate Data Center service offerings with cloud based services Focusing on back-up and storage use cases; POC targeted for winter’14, Pilot for late spring ’14 DVS Tape Archive Migration Move 500TB+ DVS tape archive to Amazon Glacier storage Technical solution development w/AWS Solutions Architect File Sharing Initiative Review options for file sharing options for end users Kick-off meeting with UC, Support Services on 11/18 SIS ProjectSIS Project Implementation Preliminary conversations on AWS usage Security review of AWS Review of options for use of Amazon Web Services for Level 3 & 4 classified data Approved for use (with appropriate use/control)

5. What we’ve learned Co-located, collaborative engineering team is a successful model Core Team, with representation from across HUIT, is effective at looking at issues and coordinating efforts (but not scalable) Few Universities have moved beyond the contracting point for external cloud services (from a central IT perspective) Internal billing systems have enabled distributed use (a challenge for other Universities) Amazon Web Services is at a tipping point for Enterprise adoption AWS has been highly engaged as a vendor and very interested in building a strong partnership Everyone is very excited about going to the cloud!

6. Emerging Challenges: Short Term Accelerating movement towards cloud adoption (in particular AWS) outstrips resources and capabilities No current support model for DevOps & related needs of those who want to transition to cloud Significant skills and resource gap Manage expectations Be willing to fail Learn from early adopters through coordination efforts Plan now to meet the growing gap 6 Mitigation

7. Challenges: Long Term Organizational readiness Skills gap Need to expand focus on architecture & engineering (away from operations) Expected growth in need for vendor management (beyond technical) Funding model impacts due to radical changes in service delivery modes (fixed costs, staff, “free market” selection of internal & external services) 7