23
Sync in an NFV World www.calnexsol.c om

Sync in an NFV World (Ram, ITSF 2016)

Embed Size (px)

Citation preview

Page 1: Sync in an NFV World (Ram, ITSF 2016)

Sync in an NFV World

www.calnexsol.com

Page 2: Sync in an NFV World (Ram, ITSF 2016)

2

• What is Virtualisation? What is NFV?• Standards for NFV• Why does NFV affect sync?• Challenges, Questions, Thoughts• Summary

Sync in an NFV World

Page 3: Sync in an NFV World (Ram, ITSF 2016)

3

What are Virtualisation and Network Function

Virtualisation?

Page 4: Sync in an NFV World (Ram, ITSF 2016)

4

Doing in software what is traditionally done in hardware by emulatingthe hardware

Virtualisation

We replace this With this

Page 5: Sync in an NFV World (Ram, ITSF 2016)

5

• Network Functions Virtualization • The replacement of dedicated network elements with software

implementations running on standard servers

What is NFV?

RouterFirewall

NAT

RNC

SGSN/GGSN

Media Gateway

Dedicated hardware for each function

Virtual Appliance

Virtual Appliance

Virtual Appliance

Virtual Appliance

Virtual Appliance Virtual

Appliance

Virtual Appliance

Standard shared hardware, virtual functions

Page 6: Sync in an NFV World (Ram, ITSF 2016)

Virtualisation Layers

6

COTS Hardware running a Type 1 Hypervisor (e.g. VMWare)

COTS Hardware running a Traditional OS (e.g. Linux or Windows)

Type 2 Hypervisor (E.g. KVM/QEMU or Virtual Box)

VM running a guest OS

VM running a guest OS

VM running a guest OS

VM running a guest OS

VM running a guest OS

VM running a guest OS

Virtual Network Functions

Virtual Network Functions

Virtual Network Functions

Virtual Network Functions

Virtual Network Functions

Virtual Network Functions

Physical NICs Physical NICs

Virtual NICs and Switches

Virtual NICs and Switches

COTS = Commercial Off the Shelf SystemOS = Operating SystemNIC = Network Interface CardVM = Virtual Machine

Page 7: Sync in an NFV World (Ram, ITSF 2016)

7

Why adopt NFV?

Massively Increased FlexibilityGreatly Increased Speed of Deployment and Reconfiguration

+

Page 8: Sync in an NFV World (Ram, ITSF 2016)

8

Standards

Page 9: Sync in an NFV World (Ram, ITSF 2016)

9

ETSI NFV Reference Architecture

Page 10: Sync in an NFV World (Ram, ITSF 2016)

10

• ETSI have finalized several Standards, Recommendations and Use Cases for NFV.• http://www.etsi.org/technologies-clusters/technologies/nfv

• Virtualization Requirements document, Section 5.8:• http://www.etsi.org/deliver/etsi_gs/NFV/001_099/004/01.01.01_60/gs

_NFV004v010101p.pdf• Service Assurance suggests the use of IEEE 1588 timestamps• Implemented on the NIC to establish a common time base for physical

layer and upper layer processes• Timestamps to be used as precise time labels for all event processes

Standards for NFV Sync

Page 11: Sync in an NFV World (Ram, ITSF 2016)

11

Why does it affect Sync?

Page 12: Sync in an NFV World (Ram, ITSF 2016)

12

1) Accurate Sync needs deterministic elements and quality components

2) Software is both slower and less deterministic than hardware

3) The underlying processor hardware is usually clocked by a relatively low quality oscillator

Why Does it affect Sync?

Page 13: Sync in an NFV World (Ram, ITSF 2016)

13

Disk

Process 1

Process 2

Process 3

Process 4

Processor

Process 5

Interrupt Routine

Interrupt

What Makes Software Less Deterministic?

The processor is usually shared between multiple processes.The number of active processes typically varies dynamically.Processes can be swapped out to disk to make space – this takes time.Interrupts can happen at any time – disrupting the flow of operations

Sche

dule

r

Page 14: Sync in an NFV World (Ram, ITSF 2016)

14

1) Memory access times vary depending on typecache, static, dynamic, virtual, etc.

2) Modern processor techniques make predictability difficult.Predicting exactly how long a sequence of instructions will take is very difficult

3) Multi-threading and different numbers of processor cores.

4) Processors execute at different speeds at different times A given piece of software will run at a different rate on different machines.

5) Software is written in high level languages which are then compiledEach time the code is changed, the sequence and therefore the timing changes.

What Else Makes Software Less Deterministic?

Page 15: Sync in an NFV World (Ram, ITSF 2016)

15

Challenges, Questions and Thoughts for NFV Sync

Page 16: Sync in an NFV World (Ram, ITSF 2016)

16

How Do We Get Accurate Time Into a VM?

VM running a guest OS

VM running a guest OS

VM running a guest OS

• A sync chain requires dedicated hardware• Virtualising it will not be good enough for most real world applications• A boundary clock is a hardware function – making use of oscillators, PLL’s etc.• As soon as we cross into the software domain, things become less predictable.

??

Page 17: Sync in an NFV World (Ram, ITSF 2016)

17

Page 18: Sync in an NFV World (Ram, ITSF 2016)

18

External GM compares returned time to GPSLessons: Connectivity to cloud instances is key. Enormous variation

depending on VM technology. Possible to sync reasonably well with off the shelf technology now given smart enough smoothing.

An example from FinanceFSMLabs TimeKeeper based system

holds Amazon VM instances to within 10 microseconds accuracy over internet

High precision time sourceAWS instance that

acts as boundary clock to serve slaves within the AWS cloud

Page 19: Sync in an NFV World (Ram, ITSF 2016)

19

A suggestion for Telecoms

Page 20: Sync in an NFV World (Ram, ITSF 2016)

20

A suggestion for Telecoms (contd.)

Page 21: Sync in an NFV World (Ram, ITSF 2016)

21

How accurate might we be able to make a software PTP implementation?

How accurately might we be able to transfer and maintain time within a VM with or without specialised hardware?

How can we solve the measurement challenge – how to verify accuracy?

Questions – Research Needed

Page 22: Sync in an NFV World (Ram, ITSF 2016)

22

• NFV is coming, like it or not• Most major operators are considering it, if not actively planning for it• Probably the biggest shake-up of telecoms networks since voice-data convergence 10 years ago

• Sync will be affected• NFV doesn’t remove the need for sync, sync methods need to evolve• New models of operation will be established• New opportunities will be created

• The industry is moving forward• Techniques to lock SW to HW • Techniques to maintain SW accuracy• Network & equipment architecture ideas

• Are we looking at a new generation of hardware or architecture?

Summary

Page 23: Sync in an NFV World (Ram, ITSF 2016)

Questions? Ask them! Go to:

@ calnexsol.com/en/blog

and Ask Tim

Tim’s Time& Sync Blog