The document discusses software defined infrastructure and how it can be implemented at airports. It describes how infrastructure used to be comprised of separate hardware components from different vendors, which was difficult to manage. Software defined infrastructure abstracts the control plane from the hardware and uses open APIs, virtualization, and centralized management to allow any application to run on any infrastructure. This makes infrastructure more scalable, flexible, and cost effective. The document provides examples of software defined infrastructure products and outlines steps to establish this at airports.

1. SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 1
REVOLUTION - SD- INFRASTRUCTURE
BY ADNAN SHABBIR
SR. IT CONSULTANT
SPECIALIZED ON AIRPORTS

2. AIRPORT INFRASTRUCTURE
YESTERDAY
01
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 2

3. LET’S DEPLOY AN APPLICATION
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 3
I have an app.
I need
infrastructure to
deploy that.
Who should I
ask?
I need processing, RAM,
storage, network and
security. Hey Teams?
Compute
Storage
Network and
cabling
Security
WE need to work together
on your requirements. Q2
is ok?
I need to buy
new servers
Disks.
RAID?
How many
ports? Where
to route?
VLANs?
This IP to that
IP, this port to
that port?
Intrusion?

4. App team
Compute
team
Processing
Memory
Storage
team
Storage
Network
team
Routing
Switching
Load
Balancing
Traffic
Engineering
Security
team
Rules
Intrusion
DEPLOYMENT FLOW
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 4
Integration

5.  Deployment requires
 Understanding requirements in language
teams know
 Designing a solution
 Solution creates more requirement
 Coordinate
 Procure and install
 Integrate
 Test
 Management and operation strategy and
tools
 Deployment cycle can take weeks and months.
HOW DEPLOYMENT WAS YESTERDAY
Network
Storage
CablingSecurity
Compute
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 5

6.  Multivendor environment
 Almost every component has its vendor
 Support skills and contracts from different
vendors for same infrastructure
 Difficult troubleshooting.
 No single ownership of problems
 Not scalable
 Hard to commission, hard to increase
capacity.
 Short life
 Hardware installed today could be good only
for a few years
 Not adaptable
 Closed systems with own operating system
 New feature integration takes ages
 Every equipment is updated separately
 Not flexible
 Changing requirements. Peak and lows.
HOW OPERATION AND MAINTENANCE WAS YESTERDAY?
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 6

7. AIRPORT INFRASTRUCTURE
NOW
01
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 7

8.  What IT infrastructure consists of (major blocks)?
 Servers
• to serve data, process it, present it.
• application, web, DB, middle tier etc
 Storage
• to save data
 Network
• to transfer data, to secure it, to load
balance it
• Switching, routing, firewall, load balancing,
IPS, wireless
 Hosts
• end user devices, to access application.
• PCs, laptops, mobiles, IP telephones, IP
cameras, PA, SACS
 Cabling
• physical layer
• Fibre, copper
WHAT IS IT INFRASTRUCTURE?
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 8
 Two major blocks
 Hardware
• CPU
• RAM
• DISK
• Switches (forwarders) ports
• Cables
• Changes are not frequent
 Rest is all services (software)
• Operating system
• Disk replication algorithm
• Routing
• Switching decisions
• Load balancing
• Firewall
• Intrusion prevention and detection
• Policies
• Require update frequently
• WHY NOT SEGREGATE THEM?

9. Management
Control
Compute and
Storage
Network Security
WHAT IF?
 Take control layer from all the components and
combine them into a single controller
 Just have OPEN standard APIs on every vendor
device and build a controller which integrate
with them all
 Single software controlling everything on
infrastructure.
 Single software for monitoring, configuration and
management for all infrastructure
 Single view, single flow and single ownership
 Vendor independent. Use any device, with any
controller, with any management software
 All control and management is run on general
purpose hardware
 This is real Cloud. An abstraction on all levels,
freedom on all levels.
IT IS NOT FUTURE. IT IS HAPPENING NOW
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 9

10.  Compute and storage
 Virtualization was introduced long back and is
very much used in many deployments
 Solution like VMWare, Hyper-V and KVM are
deployed widely
 OPEN standards are introduced and widely
adopted
 Most of the vendors support virtualization
 Network and Security had to follow
 Software Defined Networking (SDN) has started
completing the picture
 Vendors like Cisco and Juniper have
committed to SDN.
 Resource hungry enterprises like Google,
Facebook and Yahoo are running after such
solutions for their ever expanding data
centers.
Combined Viratualized or Software Defined
Infrastructure
INTRODUCING SOFTWARE DEFINED INFRASTRUCTURE
Virtual
Platform
Virtual
Network
SD-Infra
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 10

11.  VNF- Virtualized Network Function
 Network functions
 Routing
 Firewall
 Load Balancing
 Wireless controller
 QoS
 Intrusion Detection and prevention
 Switch Forwarding decisions
 Separate appliances in the past. Now just VMs.
 All the cost savings and operational easiness that
world got from virtualized platform is now
available for network
VNF AND SOFTWARE DEFINED INFRASTRUCTURE
 It is now ‘one liner vision’ of different vendors.
Juniper- ‘Any underlay for any
overlay for any app’
VMWARE- ‘One cloud, any
application, any device’
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 11

12. HOW TO BUILD SD- INFRASTRUCTURE?
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 12
Compute
hardware
Storage
hardware
Network
hardware
Virtualization Layer
Virtualized
Compute
Virtualized
Storage
Virtualized
Network
vCPU
vMemory
image
vDisk
volume
vRouter
vSwitch
vDistr-Switch
vFirewall
vLoad balancer
vWireless controller
Management
and
Orchestration
Control
Scripting and automation

13. HARDWARE- HOW IT LOOKS IDEALLY
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 13

14. OPEN NETWORK ARCHITECTURE
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 14

15.  Buy hardware from any vendor having OPEN
APIs for integration
 Virtualize the components
 Take brain away and control through a software
completely abstracting the underlay.
 Manage, configure, scale, operate, update
through one software
 It is INFRASTRUCTURE in true meaning, just like
roads- you build roads and bridges and cars,
buses, bikes or any other vehicle uses it
independent of make and model.
BUILDING SD-INFRASTRUCTURE
 And at the end
AUTOMATE the
whole process
 Use drop down menus, templates and provide
a full service at A CLICK
 Build once the infrastructure and then just
provide services.
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 15

16. PRODUCTS IN MARKET (EXAMPLES)- VMWARE
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 16

17. PRODUCTS IN MARKET (EXAMPLES)-VMWARE NSX
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 17

18. PRODUCTS IN MARKET (EXAMPLES)- VMWARE VSWITCH
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 18

19. PRODUCTS IN MARKET (EXAMPLES)- JUNIPER NFV
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 19

20. PRODUCTS IN MARKET (EXAMPLES)- REDHAT
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 20

21. PRODUCTS IN MARKET (EXAMPLES) - OPENSTACK
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 21

22. PRODUCTS IN MARKET (EXAMPLES) –ERICSSON (SP)
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 22

23. PRODUCTS IN MARKET (EXAMPLES) –ERICSSON (SP)
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 23

24.  AIRPORTS ARE MULTITENANT ENVIRONMENT BY NATURE
 Airports are used by airlines, ground handlers, restaurants, duty free, operations departments, police,
customs, security forces and list goes on.
 Tenants change year to year
 They are critical- operation and maintenance should be smooth and ideally outage free
 They are ever expanding
 All IT network required to be updated frequently.
 Services are introduced and updated often
 It is essentially a SERVICE PROVIDER NETWORK.
WHY ON AIRPORT?
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 24

25.  Offer
 Offer it as a complete solution for IT infrastructure of any airport
 OPEN
 With or without partners, as concept is OPEN or vendor independent by nature
 Customers can choose any vendor. Doesn’t change our blue print
 One design, different capacity
 Tailor the capacity to suit the requirements of customer, not the solution
 We may not need that much knowledge of vendor dependent technology. We evaluate based on
design and service requirement.
 First blue print
 Once we have a blue print of the design, we know almost everything.
STRATEGY
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 25

26.  More research
 Trainings on Openstack, VMWare and vendor solutions
 Establishment of a lab- could be with 3 to 6 components. 2 x servers, 2 storages, 2 switches
 Preparation of blue print with ADP-I watermark (could be first in industry for airport)
 Test the solution in lab, probably demonstrate or stage for customers.
 Setup demonstrations in Airshows.
STEPS AHEAD
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 26

27.  IT is getting virtualized very fast. We need to keep up.
 Enter early in market and be unique by providing a solution others may not thinking about. Be different
and ahead.
 This is happening NOW. It is not NEXT anymore.
 Q&A
CONCLUSION
SD infrastructure- Adnan Shabbir- 10/01/2017 PAGE 27