HP SDN Document Portfolio Introduction

Transcription

1 HP SDN Document Portfolio Introduction Technical Solution Guide Version: 1 September 2013

2

3 Table of Contents HP SDN Document Portfolio Overview... 2 Introduction... 2 Terms and Concepts... 2 Resources, contacts, or additional links... 7 Learn more at hp.com/networking... 7

4 HP SDN Document Portfolio Overview The goal of this portfolio is to provide a deep dive description of the HP SDN solution. The portfolio is composed of the following documents: 1. HP SDN Introduction (this document) 2. HP OpenFlow and SDN Technical Overview Technical Solution Guide 3. HP OpenFlow Technical Overview Technical Solution Guide 4. HP VM and Ubuntu Overview Technical Solution Guide 5. HP Mininet Technical Overview Technical Solution Guide 6. HP SDN Controller Architecture Technical Solution Guide 7. HP SDN Controller Installation Technical Solution Guide 8. HP SDN Controller Network Service Modules - Technical Solution Guide 9. HP SDN Controller REST API and Security - Technical Solution Guide 10. HP SDN Controller Troubleshooting - Technical Solution Guide Introduction Software-Defined Networks (SDN) brings greater simplicity to your network. SDN delivered through HP will enable your organization to experience applications as never before, since the network is automatically tuned through SDN. As your organization realizes the full benefits of a SDN solution, you can achieve: Dynamic and rapid deployment of cloud applications Automation of network provisioning while eliminating configuration errors Increased IT efficiency with services orchestration The HP Virtual Application Networks Framework is a complete, end-to-end SDN solution that enables businesses to create a scalable, agile, and secure network that streamlines operations. Virtual Application Networks delivers business agility for software defined and traditional networks. Virtual Application Networks solutions delivered through HP Intelligent Management Center (IMC) enable policy-based automation and orchestration for traditional networks. HP s approach to transformational initiatives such as Software-defined Networks is a proven method that is grounded in realistic and practical steps based on service innovation, lifecycle approach and project experience in other domains such as Cloud. This document portfolio is designed for the SDN application developer and delves into the architecture of an SDN environment and the components that make up the environment. It also explores the steps to build a development environment and the process of building a customer SDN application. HP is a leader in SDN. Thank you for joining on this journey that will certainly change the world of networking. Terms and Concepts This section provides a high level overview of terms and concepts used throughout the documents in this portfolio. These brief introductions to the various SDN terms will aid with the comprehension of the different topics. OpenFlow Communications protocol between an SDN Controller and Routers & Switches HP SDN Controller uses OpenFlow for communication with network devices Managed by the Open Networks Foundation (ONF) 2

5 HP SDN Document Portfolio Introduction Figure 1: OpenFlow SDN: Software Defined Networking Includes network devices, Controllers, Applications and Managment Control plane moved from Routers & Switches to an external controller. Networks managed via applications using APIs to interface with a controller and the controller use OpenFlow to communicate with network devices. Figure 2: SDN Abstraction Simplified and generalized view of network (Hide complex lower level details to higher layers ) Programming Analogy: Higher level program languages compiled by a compiler into machine code for execution on many vendor hardware platforms Server Architecture Analogy: Standard OS on Standard Intel x86 systems Networking Abstraction: OSI Model Linux Open Source Operating System similar to Unix 90% of 500 fastest supercomputers run a variant of Linux Ubuntu Linux operating system distributed as free and open source HP SDN Controller requires Ubuntu Server OS HP SDN Developer machine used to provide GUI interface and other tools (curl, Eclipse) This machine is not required for deployment of SDN Controller Provides development tools for development of applications Network Engineers could use terminal on Mac OS or Putty on Windows for labs in this course (not recommended) Virtualization VMs used in labs for ease of deployment Creation of virtual machines (VM) that act like real computers within a host operating system Software is separated from underlying hardware resources Hypervisor Type 1: native or bare metal No host operating system (OS), just special virtualization software such as VMWare ESXi or KVM that hosts guest operating systems Ubuntu could run as a VM (guest OS) on top of bare metal hypervisor Type 2: hosted within another OS 3

6 Ubuntu could run as a VM (guest OS) running on Windows (host OS) The Controller requires Ubuntu Could be a physical or virtual machine VirtualBox Free Open Source virtualization software HP SDN provided images have been created for VirtualBox VMWare Virtualization software HP SDN provided images can be imported into VMWare VMWare workstation Guest virtualization on host operating systems VMWare ESXi Bare-metal virtualization KVM Kernel-based Virtual Machine (KVM) is a virtualization infrastructure for the Linux kernel Allows for bare-metal installation Java An object-oriented computer programming language that is specifically designed to have as few implementation dependencies as possible Intended to let application developers reuse code on multiple platforms Internal Controller applications (called modules) need to be written in Java The term applications is used for external applications OpenStack Keystone Provides centralized user authentication Used by SDN Controller for user authentication Definitions Users = normal users (SDN operators and administrators) Tenants = collections of resources (SDN tenant used by SDN Controller) Roles = Read & write or read only used in SDN Controller REST Representational state transfer (REST) is a style of software architecture for distributed systems such as the World Wide Web. REST has emerged as a predominant web API design model. HP SDN Controller uses a REST API Allows external applications to run API calls against SDN Controller Another example HP Intelligent Management Center (IMC) eapi VIRGO A completely module-based Java application server that is designed to run enterprise Java applications Provides a platform to develop, deploy, and service enterprise Java applications. HP SDN Controller use Virgo containers OSGi The Open Services Gateway Imitative (OSGi) framework is a modular system and service platform for the Java programming language that implements a complete and dynamic component model, something that does not exist in standalone Java/VM environments. This allows Java programs to use other Java programs as objects and provide application isolation Results in easier to re-use code SLF4 Simple Logging Facade for Java Java logging service Allows for plug in of desired logging framework at deployment time JSON JavaScript Object Notation 4

7 HP SDN Document Portfolio Introduction A text-based open standard designed for human-readable XML (easy for humans to read/write) Derived from the JavaScript scripting language for representing simple data structures and associative arrays, called objects Language independent, many programming language parsers Network Topology The arrangement of the various elements (links, nodes, interfaces, hosts, etc.) of a computer network Topological structure of a network and may be depicted physically or logically Physical topology refers to the placement of the network s various components, including device location and cable installation Logical topology shows how data flows within a network, regardless of its physical design Figure 3: Network Topology API Application Programming Interface Specifies how software components should interact with each other Often an API is a library that includes specifications for routines, data structures, object classes, and variables Northbound API An interface that conceptualizes the lower-level details (e.g., data or functions) used by, or in, the component Used to interface with higher-level layers using the southbound interface of the higher-level component(s) In architectural overview, the northbound interface is normally drawn at the top of the component it is defined in, hence the name northbound interface. Examples of a northbound interface are the Restful APIs and Java APIs used between the HP SDN Controller and SDN applications Southbound API Opposite of a northbound interface The southbound interface is normally drawn at the bottom of an architectural diagram Examples of southbound interfaces include OpenFlow or a command-line interface (CLI) Figure 4: APIs 5

8 6

9 HP SDN Document Portfolio Introduction Resources, contacts, or additional links HP SDN: HP SDN SDK and documentation: Learn more at hp.com/networking Sign up for updates hp.com/go/getupdated Share with colleagues Rate this document Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. October 2013