Академический Документы
Профессиональный Документы
Культура Документы
Tweet this
CTOs guide to SDN, NFV and VNF
Tweet this
CTOs guide to SDN, NFV and VNF
Contents
Server virtualisation introduces SDN 09 Deploying and managing SDN and VNFs 19
About Canonical 23
Tweet this
5
CTOs guide to SDN, NFV and VNF
Executive overview
Network infrastructure is following the path of Software Defined Networking SDN Virtualised Network Functions VNF
server hardware, which migrated from application- Software on commodity hardware that coexists The specific network function that is now
specific servers to virtual machines. Were now with or replaces traditional, proprietary a software service deployed on commodity
migrating from function-specific network network hardware, like switches and routers. hardware, for example firewalls, IP services
hardware to software-based virtual functions. DHCP/DNS/load balancing, VoIP, IMS
Network Functions Virtualisation NFV
message services, RANs, EPCs, and more.
For organisations that already have virtual Generally refers to virtualising higher level
machines deployed, youre already using SDN network functions, as software, on commodity
today. If you have a firewall or load balancing hardware. NFV infrastructure can run on top
service running as a virtual machine, youve of traditional network hardware, SDN-based
begun using NFV infrastructure, as well. networks, or a combination of both.
Tweet this
6
CTOs guide to SDN, NFV and VNF
Economic benefits of
software-based networking
Scaling and operating Decoupling Beyond upgrades
SDN and NFV offer nearly infinite economies as Moving network control out of proprietary New features and new network requirements
of scale. Most of the issues with oversubscribing hardware devices and into a software are increasingly being made. In a traditional
ports not having enough, or undersubscribing infrastructure, and migrating network network approach, these capabilities either
ports buying more than you need, are eliminated functions from single purpose hardware arent made available or require new hardware
when software is introduced to replace physical, to VNFs on commodity hardware, are both procurement, physical installation, and physical
single-function devices. Time is money, and in a examples of decoupling the desired function connection. With SDN and NFV infrastructures,
software-driven infrastructure, updates, upgrades from the hardware. Decoupling provides new features and capabilities are deployed
and changes are all faster and much simpler. an agility that has never before been available as software.
to network operators.
The cost of commodity hardware is typically much The same care must be taken when implementing
lower than that of function specific network For example, when you decouple system new software features as with new hardware,
equipment. Support costs also decrease, from performance data plane, from system so interoperability testing and architectural design
hardware maintenance cost to operational and configuration control plane, a network are still critical. The time to implementation
vendor support. upgrade from 4G to 5G can be done without is dramatically reduced, though. Further in
system configuration migration or redefinition. this eBook interoperability and performance
You just change the VNFs that control the testing are addressed as you read about
antennae. Similarly, an entirely new network OIL and V-PIL.
infrastructure could be overlayed
on an existing topology with SDN.
Tweet this
7
CTOs guide to SDN, NFV and VNF
Why now?
Tweet this
8
CTOs guide to SDN, NFV and VNF
Tweet this
9
CTOs guide to SDN, NFV and VNF
Tweet this
10
CTOs guide to SDN, NFV and VNF
Tweet this
11
CTOs guide to SDN, NFV and VNF
virtual machine
legacy switch
Tweet this
12
CTOs guide to SDN, NFV and VNF
D
ecrease capital and operational firewall
expenditure
router
D
ecouple the management control plane, virtual switch software
load balancer
from the device itself data plane, whereby
centralising network control
Tweet this
13
CTOs guide to SDN, NFV and VNF
Tweet this
14
CTOs guide to SDN, NFV and VNF
NFV infrastructure NFVi Virtualised Network Functions VNF NFV deployment and architecture
The NFV concept is newer than SDN. While SDN VNF refers to the functions that are being NFV infrastructure can be deployed using
focuses on network hardware and the separation virtualised in an NFV infrastructure. Like traditional network switching infrastructure,
of the data and control planes, NFV refers more SDN, this means that functions that used to be or with SDN, or a combination of the two.
to application and network specific functions. delivered by proprietary, stand-alone devices, At present, combined SDN/NFV/traditional
NFV infrastructure defines all of the components, are now being written as software that runs infrastructure is most common, although the
software and hardware, that enable NFV on Linux (like Ubuntu) on industry standard, components of the network core that support
for a given solution or organisation. commodity hardware. NFV are most often SDN-based.
Ubuntu
Core
Ubuntu
Core
legacy router
virtual switch Ubuntu Ubuntu
software
open compute SDN switch
Tweet this
15
CTOs guide to SDN, NFV and VNF
Tweet this
16
CTOs guide to SDN, NFV and VNF
Ubuntu
Core Ubuntu SDN SDN
Core software software
open compute SDN switch open compute SDN switch Ubuntu Ubuntu
Tweet this
17
CTOs guide to SDN, NFV and VNF
Tweet this
18
CTOs guide to SDN, NFV and VNF
The platform
As the Why Now? page of this eBook suggests, Scalable financial model that eliminates the Scalable services include offerings like
Ubuntu is the platform of choice for SDN and cost-prohibitive pain points of starting small BootStack, a managed, hosted Ubuntu
NFV infrastructure. Ubuntu is the basis for and growing big. Ubuntu Advantage for OpenStack offering. BootStack scales to
Ubuntu OpenStack and for hyperscale cloud OpenStack, which provides premium support hundreds of nodes, and includes OpenStack
computing. from Canonical, is priced with the economical training options, and optional SLAs. There
understanding of a hyperscale datacentre. is also the option to completely transfer
More than 65% of large OpenStack clouds
management and control of your BootStack
run on Ubuntu. Ubuntu hosts more OpenStack Scalable architecture from the kernel to
environment to your own qualified,
cloud workloads than all other operating the tools used to manage applications on
operations staff.
systems combined. Ubuntu, when features are implemented,
theyre all done with cloud scalability in mind.
The growing ecosystem of SDN and VNF
Technologies like the LXD container hypervisor
software is built for deployment on Ubuntu.
and FAN networking increase density of
services on physical servers. They also both
have scalable management interfaces, to
support hundreds of server nodes as your
cloud grows.
Tweet this
19
CTOs guide to SDN, NFV and VNF
Tweet this
20
CTOs guide to SDN, NFV and VNF
Tweet this
21
CTOs guide to SDN, NFV and VNF
Tweet this
22
CTOs guide to SDN, NFV and VNF
Conclusion
Tweet this
23
CTOs guide to SDN, NFV and VNF
About Canonical
Tweet this