SA7 IaaS procurement

SA7 IaaS procurement
TF-CPR, 17 March 2015, Amsterdam
Michel Wets
[email protected]
Connect | Communicate | Collaborate
1
STRATEGY
Collaborate,
to enable and facilitate our community
to use online services
on a large scale, with the right conditions
STANDARDS
MAKE & BUY
IN-HOUSE & OUTSOURCED
REQUIREMENTS
CATALOGUE
COLLABORATIO
N
SUITES
REALTIME
COMMUNICATIO
N
FILE STORAGE
AND SYNC
INFRASTRUCTU
RE
AS A
SERVICE
FOUNDATION
AREAS
ADOPTION
ORGANISATIONAL STRUCTURE
A NEW TASK IN GN3PLUS YEAR 2
6
1
2
3
4
5
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
Connect | Communicate | Collaborate
4
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
Connect | Communicate | Collaborate
5
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.
Connect | Communicate | Collaborate
6
Service uptake
" Providers realise that current supply chains do not match
institution needs
" Providers are willing and able to create alternative solutions
Connect | Communicate | Collaborate
7
Costs unpredictability
" Institutions need more cost predictability
" A form of fair use waiver of data egress charges would aid
uptake
Connect | Communicate | Collaborate
8
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
Connect | Communicate | Collaborate
9
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.
Connect | Communicate | Collaborate
10
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
Connect | Communicate | Collaborate
11
Documentation
" SA7 homepage:
https://intranet.geant.net/SA7/SitePages/Home.aspx
" Cloud Strategy document: Link
" Cloud standards: https://cloudstandards.cesnet.cz/en/index
" Cloud requirements: Link
" Cloud Catalogue: https://catalogue.clouds.geant.net/
Connect | Communicate | Collaborate
12
Questions?
Connect | Communicate | Collaborate
www.geant.net
www.twitter.com/GEANTnews | www.facebook.com/GEANTnetwork | www.youtube.com/GEANTtv
Connect | Communicate | Collaborate
13