1 of 19

Designing the Next-generation Cloud Service

Christopher Manly

Cornell University

2 of 19

In the beginning, it was cloudy…

Step 3

Profit! (Oh, wait, no, we’re a University)

Step 2

???

Step 1

Cloudify Everything!

3 of 19

Cloudification Initiative

    • Enable adoption

Enablement

    • Train staff

Training

    • Connect practitioners

Community

    • Encourage good practice

DevOps

4 of 19

An Initiative is not a Service (but that’s okay)

No clear boundaries or scope

No clear ownership

Opt-in adoption

5 of 19

The Cloud Has Grown up (and so have we)

Multi-cloud support

Growth in spend

260 accounts

Staff turnover

Security/Compliance needs

6 of 19

It’s time to do service design

  • Understanding �User needs
  • Defining scope
  • Aligning with �Business Requirements

7 of 19

Our Process

  • Internal discussions
    • Leadership
    • Cloud Team
  • Campus stakeholder discussion
  • Do the service design
  • Vet design with stakeholders
  • Roll out revised service

8 of 19

What did we find?

9 of 19

Strengths

Enablement

Automation

Enterprise-level Finance

Problem Solving

10 of 19

Gaps – Team View

Compliance

Account FinOps

Local�Best Practices

Self-service tools

Knowledge sharing

11 of 19

Gaps – Customer View

FinOps support

Communication & Community

Operational Services

Research support

Instructional support

12 of 19

So What Now?

13 of 19

Reaffirm Core Service Model

Cloud enablement

Vendor Management

Consulting

Direct support

14 of 19

Rebuild Cornell’s Cloud Community

15 of 19

Push for FinOps staffing

16 of 19

Develop Compliance Strategy

17 of 19

Update Documentation

18 of 19

Iterate Continuously

19 of 19

Questions?