network virtualisation technologies with virl

Cisco Virtual Internet Routing Labs (VIRL)

Brian DaughertyTechnical Leader, CCIE 5879

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 3

The Challenge

You want to develop the next big thing:• SDN controllers, agents, plugins

• Orchestration tools

• Network-aware services

You need a network to develop against

But you don’t have one

The one you need is:• Easy to build

• Easy to configure

• Easy to scale

- or at least the one you need

• Easy to take with you

• Inexpensive

© 2014 Cisco and/or its affiliates. All rights reserved. Cisco Public

Virtual Network Orchestration

Rapid network design and deployment

Real Cisco (and other) network operating systems - synched with platform releases

Integration of ‘real’ and virtual networks

Fast and scalable – 10s to 100s of routers

No cost for developers

VIRLVirtual Internet Routing Lab

Introducing Virtual Internet Routing Lab (VIRL)

VIRL – A Brief Tour


Virtualized Network Operating Systems

IOS-XR NX-OS IOS-XE IOS

Virtualized in IOS-XRv

Virtualized in NX-OSv

Virtualized in CSR1000v / Ultra

Virtualized in IOSv

Servers

Such as Ubuntu, vPagent, Jump-

Host, Others


Physical Host

Host O/S

HyperVisorQEMU/

VMs

Nested Virtualization


Keystone (Identity Services)

Glance (Image / Repository Services)

Nova(Compute Services)

Neutron(Networking Services)

Swift(Object

Services)

Cinder(Block

Storage Services)

Horizon

(Da

shb

oa

rd)

AP

Is / CLI

IaaS / cloud orchestration software – creates, links, and deletes virtual compute and network resources according to API- or CLI-based instructions

Built on OpenStack


The graphical topology editing

Enables rapid definition of network elements: Routers Links Protocols Facilities

Supports complex topologies

Manages simulations

VM Maestro


Topologies are represented in XML

Files are highly portable and shareable

Integrated support for GIT repositories enables multi-user sharing, versioning

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><topology xmlns="http://www.cisco.com/VIRL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" simulationEngine="OPENSTACK" schemaVersion="0.6" xsi:schemaLocation="http://www.cisco.com/VIRL http://cide.cisco.com/vmmaestro/schema/VIRL.xsd"> <extensions> <entry type="String" key="management_network">flat</entry> <entry type="Boolean" key="AutoNetkit.enable_cdp">true</entry> <entry type="Boolean" key="AutoNetkit.enable_OnePK">true</entry> <entry type="String" key="AutoNetkit.address_family">dual_stack</entry> <entry type="String" key="AutoNetkit.ipv4_infra_subnet">10.0.0.0</entry> <entry type="String" key="AutoNetkit.ipv4_infra_prefix">8</entry> <entry type="String" key="AutoNetkit.ipv4_loopback_subnet">192.168.0.0</entry> <entry type="String" key="AutoNetkit.ipv4_loopback_prefix">22</entry> <entry type="String" key="AutoNetkit.ipv4_vrf_loopback_subnet">172.16.0.0</entry> <entry type="String" key="AutoNetkit.ipv4_vrf_loopback_prefix">24</entry> <entry type="Boolean" key="AutoNetkit.enable_routing">true</entry> <entry type="String" key="AutoNetkit.IGP">isis</entry> </extensions> <node location="518,292" subtype="IOSv" type="SIMPLE" name="Core"> <interface name="GigabitEthernet0/1" id="0"/> <interface name="GigabitEthernet0/2" id="1"/> <interface name="GigabitEthernet0/3" id="2"/> </node> <node location="519,172" subtype="IOSv" type="SIMPLE" name="A1"> <interface name="GigabitEthernet0/1" id="0"/> <interface name="GigabitEthernet0/2" id="1"/> <interface name="GigabitEthernet0/3" id="2"/> </node> <node location="648,368" subtype="IOSv" type="SIMPLE" name="A3"> <interface name="GigabitEthernet0/1" id="0"/> <interface name="GigabitEthernet0/2" id="1"/> <interface name="GigabitEthernet0/3" id="2"/> </node> <node location="403,382" subtype="IOSv" type="SIMPLE" name="A2"> <interface name="GigabitEthernet0/1" id="0"/> <interface name="GigabitEthernet0/2" id="1"/> <interface name="GigabitEthernet0/3" id="2"/> </node>

Topology Representations


AutoNetKit

Network Information DB

XML Topology Definition

Configurations

Topology Renderings

AutoNetKit: Understands OS-specific configuration constructs

Presents graphical representations of topology attributes

Converts configurations between different OS-types and platforms

AutoNetKit Auto-Configuration


Framework OS-specific configuration generated for each node

AutoNetKit Device Awareness


OSPF area values set on each node

BGP route-reflector clusters and AS’s configured

AutoNetKit Visualizations


Create Routers•Identify Type / Flavor•Associate Image (Glance)•Identify / Assign Resources•Associate Configuration•Launch the VM (Nova)

Create Networks / Links•Identify Links and End-Points•Assign End-Points to VMs•Assign Network / Link Characteristics

•Launch the Switch (Quantum)

XML Topology Definition

The Services Topology Director orchestrates the creation of VIRL virtual routers and inter-router links based on the XML-based topology definition and configurations based by VM Maestro

Services Topology Director


VM Maestro

Services Topology Director

Topology Graph with Router Configurations

1

Topology Graph

2

Router Configurations

3

Topology Views4

5 6

Virtual Machines / Switches

7

8

A1-Console: 17000A1-Aux: 17001…

VIRL Workflow

Connecting VIRL to the ‘Real World’


eth0

eth1

eth2

br-eth1

br-ex

br-int

br-ex(172.16.2.250)

br-eth1(172.16.1.250)

lo:1(127.0.1.1)

int-br-eth1

user.snat(10.11.11.n)

DHCPT2

.

.

.

.

.

.

user.rtr

.

.

.

phy-br-eth1

AutoNetkit

A-BT101

C-AT301

B-CT102

user(10.11.12.n)

DHCPT1

Console: 17021Console: 17020

10.10.10.130

VIRL Internal Networking


eth0

eth1

eth2

br-eth1

br-ex

br-int

br-ex(172.16.2.250)

br-eth1(172.16.1.250)

lo:1(127.0.1.1)

int-br-eth1

flat.snat(10.11.11.n)

DHCPT2

flat.rtr

phy-br-eth1

AutoNetkit

A-BT101

C-AT301

B-CT102

172.16.1.n

flat(172.16.1.n)

DHCPT1

.

.

.

.

.

....

10.10.10.130

VIRL External Management-Plane


br-int

eth0

eth1

eth2

br-eth1

br-ex

br-ex(172.16.2.250)

br-eth1(172.16.1.250)

lo:1(127.0.1.1)

user.snat(10.11.11.n)

DHCPT2

user.rtr

phy-br-eth1

AutoNetkit

A-BT101

C-AT301

B-CT102

user(10.11.12.n)

DHCPT1

flat

int-br-eth1

flatT400 flat

.

.

.

.

.

....

.1Q-1010.0.1.2

.1Q-2011.0.1.3

.1Q-1010.0.1.5

.1Q-2011.0.1.4

10.10.10.130

VIRL External Data-Plane

VIRL Deployment Options


Multiple projects and users

Delivered via OVA for ESXi

Scale to dozens of vCPUs and Terabytes of memory

100s or 1000s of virtual nodes

Multiple network operating systems

Community supported

Monitoring / Analytics enabled

UCS / Server-Based Deployment


Suitable for personal / mobile use

Delivered via OVA for VMware Fusion, Workstation, Player

Scale limited by resources - ~8 vCPUs, 32G of memory

10-15 nodes typical for IOSv

Multiple network operating systems

Community supported

Monitoring / Analytics enabled

PC-Based Deployment


Number of nodes

Number of links

Virtual machine types and numbers

Protocols and features

Images used

ANK feature use

VM Maestro features use

File imports and exports

Monitoring and Analytics

VIRL Demonstration


DevNet VIRL Lab

VIRL

VMM (Linux Mint)

Fla

t

SN

AT

MG

T

VIRL

VMM (Linux Mint)

VIRL

VMM (Linux Mint)

VIRL

VMM (Linux Mint)

Fla

t

SN

AT

MG

T

1 2 3 N

……………………………………………..

ESXi

DevNet Subnets

Desktops

vSpherePython

API

CSR1000v

External

Portal

Python API

DesktopsDesktops

Desktops

network virtualisation technologies with virl

Technology

cisco andor

cisco public topologies

cisco public suitable

cisco public multiple

cisco public flat flat

deployment real cisco

cisco public ospf area

network resources