Cloud & DevOps Program Executive Dashboard

Transcription

Cloud & DevOps Program Executive Dashboard
CLOUD & DEVOPS Executive Status Dashboard |June 18, 2015
KEY
No significant concerns
Needs immediate attention
Risks identified; under review
Major risks — no plan yet
Program Narrative
Executive Attention Needed
The program has made progress with deploying QlikView and fully expects to meet the deadlines for delivering the system to production. As reported
in the last Executive Committee meeting, migration focus has been on QlikView and IAM applications — 18 of the initially planned 25 applications in this
first wave will be migrated to the cloud. A future-state architecture, product roadmap, and comprehensive strategy has been developed and is being
used in the migration approach. The transition of HUIT staff to DevOps engineering roles, as well as migration application pace, have both proven to be
slower than expected.
Developing DevOps engineering skills requires a slower pace, more individual attention, and broader leadership support than expected.
Impact: Future staff transition will require existing DevOps engineering mentorship to be successful.
Mitigation: Delay embedding DevOps engineers in application teams until program end. Provide centralized operational support until then.
Application expectations around their level of involvement in the migration process is not in alignment with ongoing support need.
Impact: Application teams do not have time available to support the migration of their applications.
Mitigation: Broad communication to application teams and senior leadership to provide specific direction on goal setting and team expectations.
Existing HPAC cloud architecture needs to be updated in order to provide ongoing support.
Impact: The HPAC team will need to support the migration, which will require time they have not planned.
Mitigation: Work with HPAC leadership to identify a plan to meet their business objectives while stabilizing the environment.
CRITICAL SUCCESS FACTORS
Financial Planning
Staff Transition
Engagement & Collaboration
Training
IT Service Management
Change Management
• Financial model still being created; we have
asked AWS for direct assistance in assessing
the financial benefits of migration
• Budget and funding sources for FY16 are still
under development
• Active management of “Unscheduled” and
“To be retired” application list required to
ensure cost savings
• Sourcing manager position defined and
awaiting approval
• HPAC operations being managed through
newly defined SLA and active outreach
• Ongoing collaboration with QlikView team
involves shared member development
between the application and DevOps teams
• Python team training modules were
completed
• DevOps Bootcamp (conducted on site by
AWS) completed successfully
• SLA defined for existing HPAC production
environment; it provides template for
ongoing SLA creation
• WS TAM resources provided operational
support analysis
• Report providing HPAC environment
analysis was conducted by New Relic
• ATS and Cloud & DevOps program teams
are working closely to identify organizational
impact associated with the introduction of
cloud and DevOps engineers
IAM | 14 Apps
Infrastructure | 2 Apps
LTS | 11 Apps
Java/Tomcat (11)
• Create/Manage ID
• Identity Service API
• PIN2 Bridge
• CAS Authentication Engine
• Shibboleth IdP
• FindPerson API Service
• SailPoint IIQ Provisioning
• IDGen
• App Admin
• Claim App (HarvardKey)
• Account App
Java J2EE (1)
• OID
Apache Mod (10)
• Class Request Tool
• Historical Calendar (HUA)
• Sylvia Websites
• Book Label Generator (WPC)
• Compass (WPC)
• HA
• Inscriptio
• Preservation Website (WPC)
• Recall (HUA)
• SAVE
• ACORN, DB for the WPC
WAVES 0 AND 1 MIGRATION: APPLICATION LIST
AcTS | 19 Apps
Apache Mod (6)
• Harmony Lab
• Harvard Cards
• LTI iSites Academic Integrity Policy Tool
• Resource Finder
• GSAS “Help Button”
• Take a Sweater
TLT (13 Total)
Apache Mod (13)
• Canvas Courses by Account Report
• Course Creation Wizard
• Local Canvas Instance
• Qualtrics Single-Sign-On
• Qualtrics Taker Authentication
• Qualtrics Whitelist Tool
• Student Locations Tool
• Term Tool
• Canvas Lecture Video Tool
• Canvas Reserve Reading List Tool
• Canvas Section Tool
• Canvas Shopping Tool
• Canvas Whitelist Tool
ATS | 24 Apps
FAS Admin (5 Total)
Apache Mod (1)
• Writing Center Scheduler
Java/Tomcat (4)
• GCAST
• Power Financial Aid Award Letter
• OARS
CAADS (6 Total)
Windows (4)
• Harvard Campaign Dashboard (QlikView)
• Harvard Prospect Analyst Dashboard (QlikView)
• Harvard Inquiry Engine (QlikView)
• Human Resource Analytics (QlikView)
Apache Mod (7)
• HUIT Crucible
• HUIT Fisheye
• HUIT Greenhopper
• HUIT Subversion
• FAS IT MediaWiki
• FAS IT Subversion (Legacy)
• HUIT Github
Application Architecture (9 Total)
Java/Tomcat (1)
• HUIT JIRA
Windows (1)
• EMS/RoomBook
HR (2 Total)
Java J2EE (1)
• Document Imaging System (ImageNow)
Other (1)
• Historical Pension Payroll System (CORT)
OPP (2 Total)
Java/Tomcat (2)
• Course Catalog
• Cross-Registration
Java J2EE (2)
• Alumni Web
• Online Giving
Other (3)
• HU-LDAP Loader
• Harvard LDAP
• IdDB
Windows (1)
• Quest Active Roles
Java/Tomcat (1)
• Web Services (Presto)
CLOUD & DEVOPS Executive Status Dashboard |June 18, 2015
KEY PROGRAM INCREMENT ACTIVITIES
Team/
Status
Category
Architecture
Pre-work for migration is driven across three tracks:
Sprint 1
6/17-6/30
Sprint 4
7/29-8/11
Sprint 5
8/12-8/25
Sprint 6
8/26-9/8
Migrate 6 ‘Easy’ Applications to Dev/Stage
2 Apps
2 Apps
2 Apps
Migrate 6 ‘Easy’ Applications to Production
2 Apps
2 Apps
2 Apps
Activity
Sprint 2
7/1-7/14
Sprint 3
7/15-7/28
Deliver Complexity Matrix
Create Assessment Checklist
• The first track relates to the critical foundational elements,
such as service level agreements and tiers of service,
required prior to migration
Engagement
• The second track is specific to the information required
prior to the migration of applications
Perform Outreach to LAMP Patterns
Select 6 ‘Easy’ LAMP Applications
Select Candidates for PI-3
Conduct Kickoff for Microsoft Azure
• The final track is architecture-specific
Sourcing
Migration:
Pre-Work
Define Team for Azure Pilot
Define Use Cases for Azure Pilot
Engagement
Refine Application Onboarding Process
Perform Engagement for ‘Easy’ Applications
Complete HPAC SLA
Service
Complete QlikView SLA
Complete SLA for ‘Easy’ Applications
Deliver CloudOps Patterns for ‘Easy’ Applications
Architecture
Define DR Pattern (Non-Critical)
Define DR Pattern (Medium Criticality)
Atlassian (4)
The team will be migrating a total of 12 applications
and conducting a sourcing strategy pilot with Microsoft
consulting.
HPAC (1)
QlikView (1)
Migration
LAMP (6)
Azure (Pilot)
LAMP Self-Service
Lessons Learned
The team will build base skills associated with environment
creation and direct deployments. Automation steps will
follow in a future program increment.
Migrate Atlassian to Production
Migrate HPAC to State
Migrate HPAC to Production
Migrate QlikView to Production
Begin Migration of Azure Use Case
Self-Service Docs for LAMP Migrations
Publish Lessons Learned
Develop Standard Migration Stories (LAMP)
Create Lab for LAMP App Pilot
Staff Development
Train Cloud & DevOps Team (LAMP)
Expand Lab/Training to SOC
The team will implement the first service offerings for
CloudOps for all PI-2 migrations.
DR
CloudOps
The team will prioritize manual deployments to build a base
skill set. Operational runbooks will be captured to determine
how automation can be incorporated at a later time.
The team will build the network security system (with
firewalls) and build the Direct Connect service.
Implement DR Pattern for Non-Critical Applications (As Required)
Vet DR Strategy With Management
Monitoring
Monitoring v. 1.0: Nagios, CloudWatch, New Relic (Free)
Security
Security Monkey for Prod Applications (QlikView, HPAC)
Logging
Logging v. 1.0 for ‘Easy’ Apps
Architecture
Deliver Basic LAMP Architecture
DevOps
QA
Create Standard LAMP Test Cases
Finalize Cloud Firewall Architecture and Produce Budget Proposal
Network & Security
Procure Firewall (If Required)
Establish Direct Connect Billing