This document discusses how OpenStack can help telecom companies transform by enabling cross-border communication and applications. The author argues that with over 6.8 billion cellphone users worldwide, telecom networks must support global connectivity and cloud-based applications and services. OpenStack allows telecoms to build public, private and hybrid clouds that can scale enormously while integrating with other technologies. This represents a new era for telecom where they become cloud companies enabling ubiquitous communication and access to data anywhere in the world.
2. Introduction
My name is Chet Golding. I’m a Principal Cloud
Architect at Zefflin Systems.
I’ll keep this intro short so if you’d like to know more
about me see the following links:
https://www.linkedin.com/in/chetgolding
http://www.zefflin.com
Chet.golding@zefflin.com
I have worked with a few of the Telecom’s in the US and
abroad on projects where OpenStack was and is a key
component.
Strategic, and Technical architecture from small to very large
scales (5 servers to 325,000 servers.)
IaaS, PaaS and SaaS product roadmap, selection and POCs
into production.
Vendor integration alliances related to OpenStack integrations
in Telecom Cloud
3. Crossing Borders
What borders?
Territorial – the ones on a map, engaging people.
Technological – Products that do and don’t play well together.
Building Alliances, Invention, and Visions.
Economic – OpenStack plays well in the enterprises of larger,
medium and small countries. You can run it at home.
Social – organic global teams solving common problems
Enabling people through open technology. Developers
world wide are provided with frameworks to collaborate
across the globe developing more complex applications
faster and with less effort.
Delivering Amazing things.
5. Consider
(See data references at the end of the deck.)
A Telecom’s users are world wide. That is our civilization.
The number of Cell Phone in Population:
Approximately 6.8 billion cell phones are in use world wide.
In the US up to 90% of American adults owned a cell by
Jan 2014, and as many as 42% may have owned a tablet
computer.
Ericsson report predicts 9.2 billion cell subscriptions by end
2019
Other emerging trends
Cluster computing cell phones are edging toward reality.
DroidCluster moving compute from backend to the mobile
device presented at PhoneCom in 2012.
Shared memory distributed computing and MIT’s DIPLOMA
BOINC on google play: distributed compute model via cell
phones
6. Isn’t everything a mobile app?
(Millions, no Billions of people don’t know the difference.)
7. A new era
(The phone company is a cloud company.)
OpenStack is helping Telecoms transform their industry, why?
Proven to be a foundation of cloud operations with elastic and durable
private, public and hybrid models.
Operates with other industry adopted products like VMWare or RedHat
Is supported and provided as distributions from major vendors
Available globally.
The app on a cell isn’t just an app but one that uses the cloud to provide
the user experience across borders anywhere on the planet.
Telecom adds compliance, security and provides for public safety.
The greatest challenges arise from a need to make these experiences look
simple to the customer.
OpenStack helps provide all of these things at the velocity of cloud to
deliver at the velocity of changing technology the Telecom must provide
and make it look easy.
8. Is this cool?
(We’re not in the failure business. We’re in the communication business.)
We talk to people in other countries as never before.
We access data, enjoy art, spread news, and share our
photos and feelings.
People all over the planet make calls across borders
because people live on the other side.
Cell users are Children from 5 to 85 (or more) they have to
be easy, pleasing and dependable.
Telecommunications is for people.
Telecom needs to “just work” the way lifting a handset off a
hook resulted in dial tone in years past
If it works, we get to be human.
10. A NIST model
Cloud Provider
Service Orchestration
Cloud Carrier
Cloud Consumer
Cloud Auditor
Cloud Service
Management
Service Layer
Physical Resource Layer
Security
Privacy
Cloud Broker
Performance
Audit
Business
SupportResource Abstraction and
Control Layer
Hardware
Facility
Portability
Interoperability
Provisioning
Configuration
Service
Intermediation
Service
Arbitrage
Service
Aggregation
IaaS
SaaS
PaaS
Security
Audit
Privacy
Impact Audit
11. Model Overlap with Cloud Management Platform
Physical
Server
(Node)
Physical
Server
(Node)
Physical
Server
(Node)
Physical
Server
(Node)
Physical
Server
(Node)
Abstracted Infrastructure
Physical Networking (Switches, Routers, Fiber, Cell Towers, etc owned by the org)
SaaS
(Software Development, Build, deployment and orchestration of applications and
services)
PaaS
(Software Development, Build, deployment and orchestration of applications and
services)
Public PaaS
Public IaaS
Public Data Network (the internet and the Telecom)
IaaS
(Hypervisor, Virtualization and Orchestration
Compute, Network and Storage)
CMP
Cloud
Management
Platform
IT Operations
Governance
Orchestration
Broker
Functions
Business
Security
Interoperability
Standardization
ITIL
CMDB
Monitoring
On Premise
Public
Hybrid
12.
13. Consumption Models
CMS with No Central PaaS
Elastic
Beanstalk
Azure App
Services
Cloud
Foundry
AWS ec2 Azure Openstack
1
CMP
CloudFoundry (One Central PaaS)
AWS ec2 Azure Openstack
2
CMS
Platform (Blueprinting)
(Central PaaS Multi Provider IaaS/Pass)
Elastic
Beanstalk
Azure App
Services
Cloud
Foundry
AWS ec2 Azure Openstack
3
1. CMS to consume the cloud native PaaS
and IaaS of cloud providers
2. CMS integrated with Central PaaS and
disable the cloud native PaaS.
3. CMS with capability to integrate with
Central PaaS and use Blueprinting to
retain the cloud native PaaS.
14. Model Migrations
Hybrid
1
1. App from direct HW to KVM
2. App from KVM or HW to OpenStack Private
3. App from 1, 2 or 3 to IaaS
4. App from 1,2,3,4 to 5 (App and SaaS)
5. App from 1-5 to 6 (PaaS/SaaS)
App
HW
App
Basic
KVM
HW
App
Open
Stack
HW
App
IaaS
App
/SaaS
IaaS
App
/SaaS
PaaS
IaaS
Private Public
2 3 4 5 6
17. A simple project roadmap
Investigation
Vendors
POCs
Project
Definition
Limited
Deployment
Production &
Support
• Ideation and Goals
• Requirements
• Project requirements clear
• Timeline needs
• Project Sponsor Buy In
• Team committed
• Scale up
• Continuous Engineering
• Cloud private, public,
hybrid beta
• Production deployment
at scale
• Beta Scale
• %open source
%premium
• Production Scale
• %open source
%premium
18. A higher capacity roadmap
Investigation
Vendors
POCs
Project Scopes
10,000 Servers
Twin
Datacenter
500 servers
Beta
Test and
Blueprint
• Ideation and Goals
• Requirements (Capacity)
• Project requirements clear
• Timeline needs
• Project Sponsor Buy In
• Team committed
• Scale up
• Continuous Engineering
• Cloud private, public,
hybrid beta
• Production deployment
at scale
• Beta Scale
• %open source
%premium
Expansion
Planning
Project Staging
2,000 Server
Per DC
Datacenter Add
Cycles
Blueprint cut to
production
Production
• Is it really 2 years?
19. Goals and Critical Masses
Supported by a Global Community of Platforms and Services
20. Scale of Civilization
(More food for thought.)
• Where are we today?
• Designing for Servers, market segments, or civilization?
Servers Stacks Apps Segments Cities Countries Civilizations
21. Reaching Goals and Opportunities
(How much of this is happening now?)
Mobile Global First – Transform the Cloud
Open Standards for Cloud Development of all mobile OS platforms via virtual
machines – IOS, Android, WinOS, Mozilla and so on.
The cloud is in your pocket – one location, all your data, all your apps, all you –
100% backed up worldwide. Go anywhere and we won’t forget you.
All Cell towers and cell phones hosting data – vast CDN
Communication resources – 100% pay as you use, emergency grace – we got your
back
Location as a Service – Be anywhere, GPS anywhere, view anywhere, search where
you are, etc. Claim as a customer – “My data is everywhere.”
3G, 4G and beyond – speed and raw availability.
Business continuity – like air. Make it zero cost, default – sorry we won’t do it
wrong any longer.
Automatic data replication
Automatic silent system migration – if region fails, sorry but your server just
didn’t go down – we’re not in the failure business
22. Project Evangelism
(This is a good idea. Promote it.)
People have awesome ideas
They do need the tool chains at their finger tips [now]
They do need wealth of knowledge
We desperately need critical mass
Lets foster personal growth
Support OpenStack
Support Open Source global development, education, and access
We are best suited to make all this happen when we work
together Crossing Borders with OpenStack
The Telecom is delivering on this today
24. References Slide
• Cell Phone in Population.
– Approximately 6.8 billion cell phones in use world wide.
• Ref: https://en.wikipedia.org/wiki/List_of_countries_by_number_of_mobile_phones_in_use
– 90% of American adults owned a cell by Jan 2014, 42% a tablet computer.
• Ref: http://www.pewinternet.org/fact-sheets/mobile-technology-fact-sheet/
– Cluster computing cell phones are edging toward reality:
• Ref: http://www.hpcwire.com/2015/01/27/new-purpose-old-smartphones-cluster-
computing/
– Linux clusters on cells since 2011 in education:
• ref: https://www.ibr.cs.tu-bs.de/papers/buesching-icdcs2012-slides.pdf
– Shared memory distributed computing and MIT’s DIPLOMA:
• Ref http://web.mit.edu/anirudh/www/diploma-camera-ready.pdf
– Ericsson report predicts 9.2 billion cell subscriptions by end 2019
• Ref: http://www.ericsson.com/res/docs/2014/ericsson-mobility-report-june-
2014.pdf
– Concepts of mobile cloud – where is your data?
• Ref: http://www.datacenterknowledge.com/archives/2011/05/09/the-mobile-cloud-
what-it-is-why-it-matters/