Date post: | 08-Sep-2014 |
Category: |
Technology |
Upload: | dataintegration |
View: | 164 times |
Download: | 1 times |
FUTURE PROOFING YOUR CAMPUSHow the digital revolution is changing universities approach to technology
Kelly ScottNetwork and Security Sales Specialist
MEMORY LANE
NETWORKS FOR A PURPOSE
NETWORKS GET IN THE WAY
15 YEARS AGO
5 YEARS AGO
TODAY
NETWORKS BECOME INVISIBLE
5
PROLIFERATION OF DATA & APPLICATIONS
WE ACTIVELY USE A DATA NETWORK EVERY 6 MINUTESOn average, every student will have 4 x devices each in 2014.
UNIVERSITY OF EXETER,2008We had a timely early adopter.
the requirements…A familiar list with a new impetus.
LOW COST OF OWNERSHIP
VLE AS A PRIORITY
DEVICE AGNOSTIC
INHERENT SECURITY Single management system
Wired and wireless, invisible and irrelevant to the CUSTOMER (not the student)
Application visibility
a single, physical network
OPEN APICLOUD READY
Fast, reliable, low-latency
Flexibility, dramatically increased longevity (15 years) and scalability
Dozens of buildings sprawling out from their campus across the city.
Plans to develop attractive
products and services for them – fast.
Much of the technology we needed to use was brand new.
It had to work with all the existing “stuff”
during migration.
It seemed like most of the place was being
rebuilt around us.
We needed UoE as much as they needed us. The team consisted of equal parts “us” and “them”.
Research partners, retailers and
incubator business All with hugely
different requirements from the same network.
reality
THE FUN PARTR&D in the sunshine
WHY IT WORKEDPeople, people and people – theirs and ours
AND STARRINGSupporting cast.
AND HANGERS-ON
THE RESULTWhat we (University of Exeter and Data Integration) achieved An
invisible
networkInherent security,
performance,
availability and
scalability
DR wasn’t a thing
we did, it was a
thing we just hadFlexibility
beyond anything we
had achieved before
SDN readiness by default
– no bottlenec
ks
A platform for automation, virtualisation and moving applications and services
internally and externally, seamlessly
NETWORK AS A SERVIC
E
Predictable costs for
many years to come – the fabled “price per
port”
DECISIONS, DECISIONS
If you DIY, ignore the badge
Simplify – use what you have, where you can
Support open standards: OpenStack, OpenFlow, ONF SDN, API and scripting
Design for your future. What might you need?
Address risk as an end-to-end metric, and be realistic about threats you face
What would I choose, if I were in the market for a network?
WHAT’S THE OUTCOME AT UOE?
The network is expanding, not being replaced
The network is invisible to users and services
UoE is off of the obsolescence train
The network is commodity
The network includes all of the networks – demarcation is moot
Why does any of this matter?
THANK YOU.