canonical.comubuntu.com

The Network Revolution - changing how network services are enabled

John Zannos, Canonical | Ubuntutwitter: jaazannos | email: john.zannos@canonical.com

Story

You are probably automating things already. But ask yourself this - how many times have you scripted or automated the same thing, for different circumstances?

For example, you may have a puppet or chef script to deploy something in production. But you deploy it in test every day too. And on developers laptops. And each time you use a different bit of automation.

Juju is a higher-level tool. With Juju you can reuse your Chef or Puppet or Ansible scripts, everywhere. On laptops, on clouds, in virtual machines and on bare metal servers.

Juju allows you to crowd-source your operations for all the things where just being brilliant is good enough. Leaving you plenty of time to focus on the things where you want to be absolutely the best in the world.

TAD Summit LisbonNovember 2016

We are the company behind Ubuntu.

Canonical, the company behind Ubuntu

The only telecom problem that mattersCost

Revenues

Today

Telecoms need:

1 Exponentially cheaper

2 Launch daily

3 New revenues

Charms & Snaps

Cloudified Network cNF

Network Apps | Svcs

Cloud EdgeElastic hybrid cloud Transactional Edge ( IoT )

Public Clouds

Bulk compute data center

Cloud EdgeElastic hybrid cloud Transactional Edge ( IoT )

PrivateClouds

BareMetal

Public cloud | Private cloud | Containers | Serverless | Edge of network | IoT

Cloud EdgeElastic hybrid cloud Transactional Edge ( IoT )

NFV | NFVI | G-VNFM

Automated operations | Interoperability | Architectural Freedom | Economics

even free is expensive

Software cost

Operations cost

Economics

Automation

Hybrid-Cloud

Containers

Network Function Virtualisation

Network Function Virtualisation will soon be extinct.

Cloudified Network Functions (cNF)is the future

NFV● OpenStack based NFVI● Image based deployment● Ported Application Legacy ● Static application with little

automation

Container based NFVI● Modeled application control● Generic VNF Management ● Common API’s and Ops● Automated service deployment

Cloudified NF (cNF)● Cloud native elastic apps● MicroServices relations chaining● Predictive analytics data process● DevOps-based Operations● Full Automation

evolution….

Virtual machines

1:1 HW mapping

Traditional VNF SI

1-2 VNFs in POC

Siloed optimization

Virtual Machines (machine

containers)

Evaluating Cloudified NFs

<10 VNFs in production

Standard OSs for appliances

Hybrid infrastructure

Model-driven ops

CI pipeline

Auto onboarding tests

M1-2 VNFs in POC

Process containers

Cloudified NF (cNF)

E2E Service model

Network slice

AppStore-enabled edge

Start 1-2 yrs 3-5 yrs 5 yrs

the journey …

Leading SP disruptors

Traditional vendors not

moving fast enough

Identify & work with disruptor vendors.

Workarounds...

Specific VNFM Vendor struggling to support a generic VNFM in the short term.

Use a proxy charm as a wrapper around the specific VNFM.

Short term validate against a vendor neutral OpenStack cloud .No testing automation

Specific VNF image

hardware requirements

VM image requires HW accelerations.

VNFs Initially Virtual Machines

Few Cloudified VNFs

Three lessons …..

There is no free lunch , there is

always virtualization overhead

VM overhead

Micro services &

network slicecNF difficult to implement

…but the future and some are doing now!

Flexibility Initially Virtual Machines

Few Cloudified VNFs

Able to modify and scale

as required

Apps not VM images

vs

SLAs adherence 1:1 hardwired with “some” cloud

characteristics

SLA compliant by

design

There is no free lunch , there is always

virtualization overhead

Little overhead and scale as

required

VM overhead

Micro services &

network slicing

Can be only accomplished

with cloudification (cNF)

Difficult to implement, new solutions

the phase change of modern software

Host Linux Filesystem

Machine Containers

Process Containers

Snap extends host

Snap

Application Containers

VirtualMachines

Traditional operations Traditional operations Mesos / Kubernetes / Swarm

KVM LXD Docker / Rkt / OCID

20

model-driven, reusable, open source, devops

22

Continuous Evolution

Ubuntu Core Store

- Set goals clearly on cNF not NFV- Start right, iterate quickly- Build bridge strategies- Modelling is a business imperative- Embrace speed and disruption

result: More services faster

Questions

BACKUP

JUJU ENVIRONMENT

The Juju environment BEFORE running the vIMS test as shown in the Juju GUI

The Juju Environment BEFORE and AFTER running the vIMS test

The Juju environment AFTER running the vIMS test as shown in the Juju GUI

Add relations between Clearwater Homestead, Bono and VoIP test to start the IMS test

Remove one of the relations between IMS and VoIP test to prepare the setup for another test run

DEPLOYING THE IMS TEST

• When juju relations are added the test will start automatically

• Add relations between ixia-ims-voip-test and Homestead,Bono. Then commit and deploy changes.

NFVI hardware

VNF vendors

Customers

MANO NFVO (Orchestrators)

VNF Types SD-WAN, vCPE, vEPC, vIMS, FWaaS, LBaaS, vCDN

NFVI partners