2. Squiz Cloud – Agenda
This presentation will cover:
> The origins of the Squiz Cloud
> Squiz case studies
> The G Cloud & the new practice of buying IT
3. Squiz Hosting – An Introduction
> We have an international footprint
5. The Squiz Network
> No contractors - owned & operated by Squiz
> Provides redundancy - Squiz connects to 4 upstream
providers
> Allows portability - Squiz owns its own (IPv4 & IPv6)
address space on the internet
> We control and maintain our own redundant routers,
firewalls and switching infrastructure.
6. The Origins of Cloud
Question
> The first demonstration of how to build very large internet
sites using large clusters of computers was done by:
> Stanford
> Berkeley
> Yahoo!
> Google
> IBM
7. The Origins of Cloud
The Berkeley NOW Project “Networks of Workstations”
8. The Origins of Cloud
The Sun E-10000 “Supermini”
> Up to 64 Processors
> Up to 64 GB of RAM
> Up to 20 TB of Disk
> Used by eBay, among others
The Personal Computer
> 200Mhz CPU
> 32MB of RAM
> 4GB Disk
10. The Origins of Cloud
Access is the killer App!
> Data & Services located in
Infrastructure the cloud
> Search, email, personal
communications, productivity, etc
> The idea of mobile access &
applications evolved.
> This requires scalability
11. The Origins of Cloud
You don’t buy servers anymore!
> You buy resources, only what you need
Welcome to utility (aka cloud) computing
> Enables 1 user/developer to build online services and
scale infinitely as required.
13. The Squiz Cloud – How it came to be
We live in an age of “Ready, fire, aim”
> Online solutions need to be agile, changing strategic
direction should not be difficult
Is your “aaS” covered?
> If your organisation’s web presence isn’t provided “as a
Service” – you may be missing the boat. Squiz can help!
Predicted growth has exceeded 500%
> Our cloud has gone through 5 significant expansion
phases in under 6 months.
14. How it came to be – the challenges
> Affordability (without sacrificing functionality)
> Agility (enables rapid deployment)
> Redundancy (ensures we meet uptime guarantees)
> Scalability (allows customers to survive infrequent
peaks)
> The Squiz Suite was born!
15. How it came to be – Our Options
> Rackspace or Amazon
16. How it came to be – Our Options
> Rackspace or Amazon
Offshore hosting doesn’t sit well with our government
clients.
> White-label
17. How it came to be – Our Options
> Rackspace or Amazon
Offshore hosting doesn’t sit well with our government
clients.
> White-label
If Squiz don’t control the infrastructure, Squiz can’t control
the quality.
> Continue to only provide dedicated (dinosaur) hosting
18. How it came to be – Our Options
> Rackspace or Amazon
Offshore hosting doesn’t sit well with our government
clients.
> White-label an Australian vendor
If Squiz don’t control the infrastructure, Squiz can’t control
the quality.
> Continue to only provide dedicated (dinosaur) hosting
That’s so last year.
19. How it came to be
Let’s build a cloud like Google!
20. Let’s build a cloud like Google!
> It should scale horizontally, without an expensive SAN
(Enables affordability)
21. Let’s build a cloud like Google!
> We should be able to provision remotely (Enables agility)
22. Let’s build a cloud like Google!
> We should be able to resize your services
(Enables scalability)
23. Let’s build a cloud like Google!
> The infrastructure needs to automatically heal
(Enables redundancy)
24. The Squiz Cloud
> It’s not VMWare!
> Did you know VMWare relies on a single point of failure?
WARNING!
25. The Squiz Cloud – It’s Applogic
> Combines traditional “grid” computing with new
virtualisation technologies
> Does not require shared storage devices, all physical
nodes combine to form extremely large resource
pools
> It is based on open-source virtualisation technologies
26. Cloud Computing & A Small Wedding
> A classic example of the value of Cloud
Computing
> Westminster Abbey receives approx 200,000
unique visitors a month
> Then there was a small wedding….
27.
28. But many organisations aren’t
> Traditional procurement lacks agility
> A time consuming and costly exercise
> So it’s not done very often…
> Focuses on selecting one or a small
number of vendors
> Creates a ‘locked in’ environment that is
hard to change
29. The G Cloud – Procurement for the SaaS
> Pre selects a large number of
vendors
> Short contract length
> Focuses on choice and flexibility
30. The G Cloud Process
> Vendor must sign up to a common set
of T&C’s
> Data must be portable
> Software must be interoperable
> SaaS delivered through Cloud
infrastructure
> Buy through the Cloudstore
31. Questions?
> Stephen Morgan - Director, Squiz Europe
> smorgan@squiz.co.uk
> @Stephen_Morgan
> http://uk.linkedin.com/in/stephenmorgan