1Connect | Communicate | Collaborate

SA7 IaaS procurement

TF-MSP, 18 March 2015, Amsterdam

Michel Wets

michel.wets@surfnet.nl

REQUIREMENTS CATALOGUE

STRATEGY STANDARDS

COLLABORATION

SUITES

REALTIMECOMMUNICATIO

N

FILE STORAGEAND SYNC

INFRASTRUCTURE

AS ASERVICE

ADOPTION

FOUNDATION

AREAS

MAKE & BUYIN-HOUSE & OUTSOURCED

Collaborate,to enable and facilitate our community

to use online serviceson a large scale, with the right conditions

4Connect | Communicate | Collaborate

Iaas procurement

1. IaaS services are rapidly maturing and can lower institutions datacenter TCO for ad hoc and even standard computations

2. JISC survey showed that total institutions spending on datacenter in UK is around 250 million euro per year

3. 5 NRENs (CARNet, HEAnet, JISC, NORDUnet and SURFnet, are participating in centralized IaaS procurement

4. 10 other NRENs also expressed interest to make these services available in 2015

5. All other European NRENs will be able to take up the procured services too

5Connect | Communicate | Collaborate

Current IaaS problems:

1. Conditions of use are not transparent

Snowden revelations have raised awareness on privacy & security concerns

2. Service uptake is not aligned with institution processes

Institutions can’t use credit card, need PO based ordering

3. Costs are not predictable, need bill-shock prevention. Data egress charges are too unpredictable and can add up quickly

6Connect | Communicate | Collaborate

Conditions of use

Provider responses to Cloud Requirement Document can be used to assess CSP abilities and security/privacy aspects

These give good information for requirements to be used in tender documents.

7Connect | Communicate | Collaborate

Service uptake

Providers realise that current supply chains do not match institution needs

Providers are willing and able to create alternative solutions

8Connect | Communicate | Collaborate

Costs unpredictability

Institutions need more cost predictability

A form of fair use waiver of data egress charges would aid uptake

9Connect | Communicate | Collaborate

Show case: JISC AWS services

Amazon contracted Arcus to provide AWS services through dedicated web portal

Allowing institutions to take up AWS services in a way which fits their processes

With post paid options, multi-level authorization and PO numbers

Initial reactions from JISC institutions are positive

10Connect | Communicate | Collaborate

Procurement process

Full OJEU restricted procedure

Using procurement to support the dialogues with the providers

Targeting especially Amazon, Microsoft, Greenclouds, Google and Cloud Sigma.

Contacting providers before tender publication to:

Sell our requirements: why should they participate in this

Listen to their abilities: what can (and can’t) they do.

This should ensure that the tender document does not come as a surprise and matches their abilities while setting a high minimum standard guaranteeing that the offer matches our needs.

11Connect | Communicate | Collaborate

Procurement process (2)

Send RFI to check abilities

Use restricted procedure with dialogue sessions to allow for feedback on draft RFP

Translate Cloud Requirements Document answers to contract details

And make sure that the tender document represents the needs, wishes and abilities of the NRENs and their institutions

Including conditions to make the procurement and adoption sustainable

12Connect | Communicate | Collaborate

Documentation

SA7 homepage: https://intranet.geant.net/SA7/SitePages/Home.aspx

External website: http://clouds.geant.net

Cloud Strategy document: Link

Cloud standards: https://cloudstandards.cesnet.cz/en/index

Cloud requirements: Link

Cloud Catalogue: https://catalogue.clouds.geant.net/

13Connect | Communicate | Collaborate

14Connect | Communicate | Collaborate

www.geant.net

www.twitter.com/GEANTnews | www.facebook.com/GEANTnetwork | www.youtube.com/GEANTtv

Connect | Communicate | Collaborate

Questions?