SURFCloud Strategy, Walter van Dijk, SURFnet

Report
SURF Cloudstrategy
TF-MSP MALTA - 27 NOVEMBER 2014
Walter van Dijk
Version: 0.1
27 November 2014
This tale started in 2011
Lots of momentum after study trip
Group of university board members visited:
• University of California, Berkeley
• University of Washington
• Google
• IBM
• Microsoft
Position Paper Cloud: Cloud First strategy:
 “Cloud not question if, but how and when”
 “Let’s act together”
 “SURF, please take the lead”
 “Sense of urgency, act now!”
http://www.surf.nl/cloud/
A lot has happened since…
 Vendor management team cloud services
250+ service providers connected to SURFconext
 Network opened up for cloud service providers: NetherLight
 Template Sourcing Strategy
 Project ‘Orchestrating the Cloud: i-Strategy’
 Set of legal terms, drafted in close collaboration with experts from the sector
 Joint architecture guidelines: HORA
 Special Interest Group Cloud Adoption
 One-stop shop for cloud services: cloud.surfspot.nl
The Gartner hypecycle: position of cloud?
Plateau of productivity on the horizon
However…
 The uptake of public cloud services by IT-management
lags behind expectations
 Privacy and information security are serious concerns
in our constituency
 Various customer segments have recently indicated that
they want SURF to develop community cloud services
in order to have a real choice
Cloud ambition SURF
In 2018 the SURF-constituency contracts a substantial part
of its required cloudservices from SURF
Underlying principles Cloudstrategy SURF
 We make a difference by putting the needs of higher education first
 SURF offers the full cloud spectrum: “users are choosers”
 SURF is a trusted partner
 Development of services jointly with early adopters: co-creation
 Available services offered to all SURF institutions via ‘one stop shop’
 SURF takes care: contractterms, vendormanagement, support etc
The SURF Cloud Approach
Phase-1:
1.
Institutions initiate an “Early Adopters Group” for a new cloudservice
1.
Requirements are defined jointly by EAG & SURF
2.
Delivery models are explored
3.
Choice of deliverymodel is made
Phase-2:
5.
Depending on the type of deliverymodel commitment will be confirmed
6.
Start acquisition (‘buy’) or joint service development (‘make’)
Phase-3:
7.
Service available for all connected institutions
SURF Cloud Continuum: freedom to choose
Guidance required on
functionality
Alignment with SURF
core competencies “make”
Impact on primary
processes HighEd
Alignment with SURF
core competencies “buy”
Keep financial benefits
within the sector
No guidance
possible on
functionality
Distance to primary
processes HighEd
Economies of scale
translate into better
terms & conditions
Community Cloud (‘make’)
Connect
Public Cloud (‘buy’)
Examples SURF cloud delivery models
Public Cloud
Community Cloud
Mix & Match
SaaS
MS Exchange
SURFdrive/ownCloud
PaaS
MS Azure
SURF PaaS
IaaS
HigherEd IaaS
SURF IaaS
Datacenters
HigherEd datacenters
SURF datacenters
Peerings/NetherLight
SURF-netwerk
SURF-netwerk
Underlying principles in every delivery model:
 Contract based on “insourcing to” SURF
 Compliant with legal framework HigherEd


’
Offered to all member institutions
Authentication via SURFconext
Criteria delivery models: institution
influence on functionality
cooperation/sharing
confidentiality
Public cloud
Mix & match
Data classification lower
Community Cloud
HORA
Data classification higher
Legal terms cloudservices HigherEd
B2C
B2B2C
B2B
cost / value
Lower
Higher
Criteria delivery models
 Alignment with core competencies SURF
 Potential to scale up towards other higher education and research institutes
 Differentiating factors in comparison with public cloud functionality
 Potential for innovation: integration with other SURF services
 Legitimacy: no market disruptions
 Financial investments versus customer commitment
 Availability of essential personnel resources
Ambitions SURF subsidiaries
 SURFsara: develops community cloud services based on in-depth
knowledge of high performance cloud computing and data management.
 SURFnet: connects all cloud services to the SURF infrastructures and
safeguards that all services comply fully with requirements in the areas
of security and privacy.
 SURFmarket: takes care of efficient and legitimate acquisition of public
cloud services as well as of community cloud components. The complete
portfolio is available via a one-stop-shop.
MAKE
CONNECT
BUY
SURF Cloud Governance
 Decision making in three phases:
 Phase-1: collecting requirements and assessment service models
 Phase-2: joint procurement or service development
 Phase-3: service provisioning
 Cooperation with “Early Adaptors Groups” is project based: joint steering group
 Decision making on SURF portfolio by SURF management team
 Decision making based on business models, including:
 Weighting of relevant criteria
 Business-case
 Risk analysis
 Tariff proposal
 After ultimately 4 years a decision is made about continuation of the service under the same
or under another service model
Current status (november 2014)
Universities:
 Joint development of personal storage service: SURFdrive
 New initiative on cooperation on webservices/webhosting
Other sectors:
 Six universities of applied science have requested to start a project on IaaS services
 Four academic medical centers have requested to start a project on MS Exchange services
 Eight academic medical centers have indicated that they want to explore cooperation with
SURF on a joint community cloud (IaaS, Sharepoint, IdM, Exchange etc)
And finally SURFnet…
 remains committed to European cloud collaboration within GN3+ and GN4
 actively shares experience with ownCloud / SURFdrive with other NREN’s
 is involved in NREN initiated arrangements with (cloud) vendors in the area of joint
procurement
 is very keen on collaboration with NREN’s !
THANK YOU

similar documents