May 13-14, Copyright 2015 Open Networking User Group. All Rights Reserved Not For

Transcription

1 May 13-14, 2015

2 NSV Architecture

3 Test Architecture System Under Test Mgmt, Orch, etc. Test Solution VM VM Hypervisor Hypervisor IP Network

4 Methodology Each individual requirement had 1 test case associated with it (total of 10) Test objec@ve Test architecture Prerequisites Simulated traffic and procedure Expected results Valida@on condi@ons Common test plan for all vendors Most tests were service agnos@c Services were inline Traffic consisted mainly of hvp traffic with 100 clients and a server Tests were run in the vendor labs, with Ixia observing remotely via Webex

5 Avni NSV Verifica9on Tes9ng Grandhi Founding Architect Avni

6 Avni Industry s First So=ware Defined Cloud

7 NSV WG Use Case Feature Verification of Top Ten Requirements Pass 1. Co-exist w/ legacy network equipment; physical and virtual 2. Load, execute and move Network Services across multiple vendors platforms 3. An interface to decouple virtualized service instances from underlying infrastructure System Under Test Products Avni Software Defined Cloud ADC Service Controller: 2931 ESXI Hypervisor OpenStack Ixia IxLoad-VE Software Versions 2.0 Release Build Havana EA 4. Support provisioning of forwarding paths between Service Nodes from n vendors Mechanisms to allow Virtual Network Services to scale w/sla req. via n supported mechanisms: e.g., on-demand scaling or automatic scaling etc. Standard APIs for all applicable functions provided to other authorized entities (e.g. CMS, service instances, 3rd parties, etc.) Standard mechanisms to preserve system state & integrity & to replicate state between N platforms Mechanisms 4 NetOps to control and verify configuration of Virtual Network Services and elements that virtualize hardware resource Functionality exposed via APIs to be protected via standard security mechanisms appropriate for that layer 10. Ability to detect failure of service instance(s) and/or network reachability

8 Avni Demonstrated Capabili9es Successfully demonstrated all top 10 NSV test requirements Avni SoZware Defined Cloud works seamlessly across Hypervisors, within a Private Cloud, or across Hybrid or Public Clouds Addi@onal capabili@es demonstrated across Hypervisors & Clouds: 1. Zero Touch Deployment of a real world end- to- end app 2. Zero Touch Deployment of Virtual Network Services 3. Auto- magic migra@on of complete app stack across Hypervisors 4. Advanced authoriza@on and security requirements 5. SLA assurance and service con@nuity 6. Single pane of glass management for apps, network services across Clouds

9 5 Unique Capabili9es and Customer Benefits

10 Versa Networks NSV Verifica9on Tes9ng Darrell Long VP Products Versa Networks

11 Versa Networks: VMware ESXi- based Topology Test cases: 1, 5, 7, 10 Verified: Physical/virtual co- existence, on- demand scaling, state preserva9on & failure detec9on/handling VMware Hypervisor ESXi, 5.5.0, Versa FlexVNF sozware 15.1 beta Versa Director sozware 15.1 beta

12 Versa Networks: KVM- based Topology Test cases: 2, 3, 4 Verified: Mul9- vendor support, de- coupling services from infrastructure & provisioning forwarding paths KVM Hypervisor QEMU Open Contrail Controller Juniper vsrx Router JUNOS 12.1X46- D10.2 Versa FlexVNF sozware 15.1 beta Versa Director sozware 15.1 beta

13 NSV WG Use Case Feature Verification of Top Ten Requirements Pass 1. Co-exist w/ legacy network equipment; physical and virtual 2. Load, execute and move Network Services across multiple vendors platforms Products System Under Test Versa FlexVNF ESXI Hypervisor Palo Alto Networks Firewall Juniper vsrx Router Software Versions 15.1 beta 5.5.0, JUNOS 12.1X46- D10.2 KVM Hypervisor QEMU Open Contrail Controller Ixia IxLoad-VE EA 3. An interface to decouple virtualized service instances from underlying infrastructure 4. Support provisioning of forwarding paths between Service Nodes from n vendors Mechanisms to allow Virtual Network Services to scale w/sla req. via n supported mechanisms: e.g., on-demand scaling or automatic scaling etc. Standard APIs for all applicable functions provided to other authorized entities (e.g. CMS, service instances, 3rd parties, etc.) Standard mechanisms to preserve system state & integrity & to replicate state between N platforms Mechanisms 4 NetOps to control and verify configuration of Virtual Network Services and elements that virtualize hardware resource Functionality exposed via APIs to be protected via standard security mechanisms appropriate for that layer 10. Ability to detect failure of service instance(s) and/or network reachability

14 Versa Networks: Our Vision Network to enable Web- Scale IT SoZware that s open & programmable Mul@- func@on with flexible, policy- based service- chaining Elas@c, resilient & mul@- tenant Agile to deploy, provision & manage Cloud Management (CMS) & SDN controller- agnos@c Transform the Data Center & Network Edge White- box Network Services Network Services Virtualiza@on (NSV) SoZware- Defined WAN (SD- WAN) Inspired by Web- Scale visionaries, refined by Versa Networks Learn more, visit our booth or online: networks.com

15 Avi Networks NSV Verifica9on Tes9ng Guru Chahal VP of Products Avi Networks

16 Test Setup Palo Alto Networks Firewall L2/ L3 Network Infrastructure Ixia Server IxOS EA IxVM Client IxVM Server VMware vcenter Proprietary and Confidential 2015 Avi Networks CADP v15.2 Red Hat Enterprise Linux (Openstack Platform 5)

17 NSV WG Use Case Feature Verification of Top Ten Requirements Pass 1. Co-exist w/ legacy network equipment; physical and virtual 2. Load, execute and move Network Services across multiple vendors platforms 3. An interface to decouple virtualized service instances from underlying infrastructure Products System Under Test Software Versions Avi CADP V15.2 Build 5026 Red Hat Enterprise Linux OpenStack VWware vsphere Ixia IxLoad-VE 6.6 Platform Build EA 4. Support provisioning of forwarding paths between Service Nodes from n vendors Mechanisms to allow Virtual Network Services to scale w/sla req. via n supported mechanisms: e.g., on-demand scaling or automatic scaling etc. Standard APIs for all applicable functions provided to other authorized entities (e.g. CMS, service instances, 3rd parties, etc.) Standard mechanisms to preserve system state & integrity & to replicate state between N platforms Mechanisms 4 NetOps to control and verify configuration of Virtual Network Services and elements that virtualize hardware resource Functionality exposed via APIs to be protected via standard security mechanisms appropriate for that layer 10. Ability to detect failure of service instance(s) and/or network reachability

18 What Stood Out Sub-second failure detection VS migration (between ADCs on different blade servers) with less than 0.002% retries. Autoscale capacity in ~20 seconds (active-active configuration) 18 Proprietary and Confidential 2015

19 NEC NSV Verifica9on Tes9ng Donald Clark Director Business Development NEC

20 So=ware Defined Network Service Orchestra9on ProgrammableFlow SoZware Defined Network Fabric On demand of flows for service Appliance Pool (Physical + Virtual Network Services) 3 rd party tools RestAPIs DDoS WAN Optimizer Load Balancer Ixia Client Tool_1 Traditional Network Firewall SDN Fabric CLI/WebGUI PFC Ixia Client Tool_2 Ixia HTTP Server

21 NSV WG Use Case Feature Verification of Top Ten Requirements Pass 1. Co-exist w/ legacy network equipment; physical and virtual 2. Load, execute and move Network Services across multiple vendors platforms Products ProgrammableFlow PF6800 Controller Ixia IxLoad-VE System Under Test ProgrammableFlow Switches PF5240 ToR, PF5820 Spine Dell S4810 NoviFlow Radware Firewall F5 Load Balancer Riverbed WAN Optimization CentOS FW on Linux ESXi Hypervisor KVM Hypervisor Software Versions EA 3. An interface to decouple virtualized service instances from underlying infrastructure 4. Support provisioning of forwarding paths between Service Nodes from n vendors Mechanisms to allow Virtual Network Services to scale w/sla req. via n supported mechanisms: e.g., on-demand scaling or automatic scaling etc. Standard APIs for all applicable functions provided to other authorized entities (e.g. CMS, service instances, 3rd parties, etc.) Standard mechanisms to preserve system state & integrity & to replicate state between N platforms Mechanisms 4 NetOps to control and verify configuration of Virtual Network Services and elements that virtualize hardware resource Functionality exposed via APIs to be protected via standard security mechanisms appropriate for that layer 10. Ability to detect failure of service instance(s) and/or network reachability

22 NSV with ProgrammableFlow SDN - Key Takeaways Service chaining with the provisioning of forwarding paths (#1 & #4) On- demand service inser@on in a virtual network using CLI/GUI or RestAPIs Flexible per flow policy seqng and provisioning without encapsula@on Integra@on with physical and virtual network services Integra@on with 3rd party tools to configure/provision network (#6 and #9) Support open and standard APIs (JSON, XML format) for 3rd party tools Enabling agile network with for mission cri@cal applica@ons (#10) Lossless failover done within Open SDN switch fabric data path Node failure triggers automated redirec@on of traffic

23 Next Steps For more ONUG web site: hvp://opennetworkingusergroup.com/spring downloads/ NSV Working Group NSV Working Group White Paper, Requirements Lists, and RFI/Q Template NSV Test Plans Vendor booths What s next Refinement of NSV use case tests Prepara@on of NSV demos for Fall 2015 performance, interoperability (e.g. service chaining, orchestra@on) Poll results