DOCSLIB.ORG

Utilizing P4 Switches in Container Networking

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Utilizing P4 Switches in Container Networking Bachelor Informatica Utilizing p4 switches in con- tainer networking Ries van Zon - 11302836 June 15, 2020 Informatica | Universiteit van Amsterdam Supervisor(s): Msc Sara Shakeri, dr. Paola Grosso Signed: Signees page 2 Abstract Containers are very popular these days and there are several software tools by which a container can be created. To connect containers the most popular method is utilizing an overlay network method. A container overlay network is easy to deploy. The drawback is that with creating an overlay network each packet will get an extra layer of encapsulation. We try to find an alternative for the overlay solution by creating connectivity between docker containers using a p4 switch. A TCP connection is created between local containers. Currently, there is no TCP connection possible between two containers on a different host. We narrowed down what the problem could be. Our findings show that the problem occurs at L4. L3 and L4 (concerning TCP) connections between Docker containers on the same host are possible. For containers on different hosts (After NAT is applied) L3 connectivity is possible but the connection at L4 is refused. page 3 page 4 Contents 1 Introduction 7 1.1 Introduction.......................................7 2 Theoretical background9 2.1 Process isolation....................................9 2.1.1 Namespaces...................................9 2.2 Containers........................................ 10 2.2.1 Linux container................................. 10 2.2.2 Docker containers............................... 10 2.3 p4 switches....................................... 11 2.3.1 Defenition of a simple p4 program...................... 12 2.3.2 Deployment of a p4 program......................... 15 2.4 Overlay network.................................... 16 3 Related work 17 3.1 Connectivity of docker containers........................... 17 3.2 Usage of p4 in SDN.................................. 18 4 Method 19 4.1 Establishing connectivity between containers using a p4 switch.......... 19 4.1.1 Connecting a Docker container to a p4 switch................ 19 4.2 TCP connection between containers using a p4 switch............... 20 4.2.1 Network topologies............................... 24 4.2.2 TCP connection between containers in a single host............ 26 4.2.3 TCP connection between containers in multiple hosts........... 30 5 Discussion 33 5.1 Multiple containers on the same host......................... 33 5.2 Single container, multiple hosts............................ 34 5.3 Firewall settings.................................... 34 6 Conclusions 37 6.1 Conclusion....................................... 37 6.2 Future work....................................... 37 6.2.1 Ethics...................................... 38 Appendices 43 A Appendix A 45 5 CONTENTS page 6 CONTENTS CHAPTER 1 Introduction 1.1 Introduction Containers are very popular these days and there are several software tools by which a container can be created. Like Docker. A container is just another way of virtualization. Despite virtual machines that use separated hardware and on top of that separated operating system, in con- tainers, the virtualization is at OS level and they share the host's kernel. Therefore, comparing with Virtual Machines (VMs) the number of resources that are utilized in container technologies is much less. [8]. Another advantage of containers is that they are quick to set up and easy to deploy[8]. Containers can also run on any distribution not dependent on the hardware of the distribution. To connect containers the most popular method is utilizing overlay network methods. A container overlay network is easy to deploy. The drawback is that with creating an overlay network each packet will get an extra layer of encapsulation. This decreases performance. Since there is more and more data send through the network nowadays, it's important to minimize the overhead where possible. The challenge is to create a network of containers, with the benefits of containers but without or at least with reduced overhead. We will try to accomplish this by implementing a p4 switch. A p4 switch is a switch from which we can program the data plane. With a p4 switch, we have more control over the incoming packets and how to forward them. P4 allows building more intelligent control mechanisms with regards to packets. To implement the p4 switch we have to find a way to change the docker default settings making a container more flexible and giving us more control over a container. To do this we have to be careful not to lose the advantages of a docker container which docker provides. To answer the research question • how can we minimize the overhead in Docker container networks by using mod- ern technologies such as p4 switches? First, we will focus on establishing connectivity between containers. In the chapter 2 (background) and chapter 3 (related work), we will show how a container can be con- nected to a p4 switch. In the chapter 4 (method), we will examine several implementations with two network settings, for a docker container, to set up a TCP connection between containers. The method chapter focusses on the question: { how can we create connectivity between containers by utilizing a p4 switch? In the chapter 5 (Discussion) we will discuss and evaluate the results after which will we draw some conclusions and propose some topics for future work in the chapter 6 (Conclusion). 7 1.1. INTRODUCTION page 8 CHAPTER 1. INTRODUCTION CHAPTER 2 Theoretical background 2.1 Process isolation Around '79 the chroot command was introduced in Linux systems. The chroot command on Unix operating systems is an operation that changes the apparent root directory for the current running process and its children. When you change root to another directory you cannot access files and commands outside that directory. With the chroot command we could create the impression of an isolated process. Chroot simply modifies pathname lookups for a process and its children, prepending the new root path to any name starting with /. The current directory is not modified and relative paths can still have access to any location outside of the new root. This is seen as the start of process isolation which has led to the containers of today. 2.1.1 Namespaces Namespaces are used to isolated different sets of global resources and restrict access to an inner process to its sandbox. There are seven types of namespaces [9] of which three are of special importance concerning a container: • Network namespace (netns) • Control group namespace (cgroup) • Process ID (pid) Network namespace Network namespaces visualize the network stack. On creation, a network namespace contains only a loopback interface. Each network interface (physical or virtual) is present in exactly one namespace and can be moved between namespaces. A network namespace isolates net- work devices, ports and has a private set of ip addresses, its routing table, ARP table, and other network-related resources. Destroying a network namespace destroys any virtual interfaces within it and moves any physical interfaces within it back to the initial network namespace. Initially, all the processes share the same default network namespace from the init process. By convention when a named network namespace is created it's an object at =var=run=netns=name that can be opened and listed by the command ip netns. The network namespace does not belong to any process yet. By attaching the network namespace to the network namespace of a process we isolate the network resources of that process. Cgroups A control group (cgroup) is a collection of processes that are bound by the same criteria and associated with a set of parameters or limits. These groups can be hierarchical, meaning that each 9 2.2. CONTAINERS group inherits limits from its parent group. The kernel provides access to multiple controllers (also called subsystems) through the cgroup interface A cgroup namespace virtualizes the contents of the =proc=self=cgroup file. Processes inside a cgroup namespace are only able to view paths relative to their namespace root. PID namespace PID namespaces are nested, meaning when a new process is created it will have a PID for each namespace from its current namespace up to the initial PID namespace. Hence the initial PID namespace can see all processes, but with different PIDs than other namespaces will see processes with. 2.2 Containers 2.2.1 Linux container Linux Containers is an virtualization method for running multiple isolated Linux systems (con- tainers) on a host using a single (Linux) kernel. The Linux kernel provides the cgroups functionality that allows limitation and prioritization of resources (CPU, memory, block I/O, network, etc.) without the need for starting any virtual machines, and also namespace isolation functionality that allows complete isolation of an appli- cation's view of the operating environment, including process trees, networking, user IDs and mounted file systems. LXC combines the kernel's cgroups and support for isolated namespaces to provide an isolated environment for applications. A container is a process from which different namespaces are isolated by attaching different customized namespaces to the namespaces of the process. Each process has its own idea of its root. By default, the root of a process is set to the system root. We can change the root of a process with the chroot command. When we create a container we create it from the context of the current process where from where the command is executed. This means that by default the root of the container is set to the root of the process from which the container was created. Today's container makes use of two features of the kernel: cgroups and namespaces. Before cgroups every process resources were managed individually. Applications that had more processes running using were using more system resources. With cgroups we can create a subgroup and assign a certain amount of system resources to that subgroup. All sub-processes belonging to that subgroup can only use the resources that were assigned to their subgroup they belong too. If we list (command systemd-cgls cpu) the cgroups we see that for each container a subgroup is created.
Load more

Recommended publications
  • Cisco Nexus 1000V Switch for KVM Data Sheet
    Data Sheet Cisco Nexus 1000V Switch for KVM Product Overview Bring enterprise-class networking features to OpenStack cloud operating system environments. The Cisco Nexus ® 1000V Switch for the Ubuntu Kernel-based Virtual Machine (KVM) reduces the operating complexity associated with virtual machine networking. Together with the OpenStack cloud operating system, this switch helps you gain control of large pools of computing, storage, and networking resources. The Cisco Nexus 1000V Switch provides a comprehensive and extensible architectural platform for virtual machine and cloud networking. This switch is designed to accelerate your server virtualization and multitenant cloud deployments in a secure and operationally transparent manner. Operating as a distributed switching platform, the Cisco Nexus 1000V enhances the visibility and manageability of your virtual and cloud networking infrastructure. It supports multiple hypervisors and many networking services and is tightly integrated with multiple cloud management systems. The Cisco Nexus 1000V Switch for KVM offers enterprise-class networking features to OpenStack cloud operating system environments, including: ● Advanced switching features such as access control lists (ACLs) and port-based access control lists (PACLS). ● Support for highly scalable, multitenant virtual networking through Virtual Extensible LAN (VXLAN). ● Manageability features such as Simple Network Management Protocol (SNMP), NETCONF, syslog, and advanced troubleshooting command-line interface (CLI) features. ● Strong north-bound management interfaces including OpenStack Neutron plug-in support and REST APIs. Benefits The Cisco Nexus 1000V Switch reduces the operational complexity associated with virtual machine networking and enables you to accomplish the following: ● Easily deploy your Infrastructure-as-a-service (IaaS) networks ◦ As the industry’s leading networking platform, the Cisco Nexus 1000V delivers performance, scalability, and stability with familiar manageability and control.
    [Show full text]
  • CCNA-Cloud -CLDFND-210-451-Official-Cert-Guide.Pdf
    ptg17120290 CCNA Cloud CLDFND 210-451 Official Cert Guide ptg17120290 GUSTAVO A. A. SANTANA, CCIE No. 8806 Cisco Press 800 East 96th Street Indianapolis, IN 46240 ii CCNA Cloud CLDFND 210-451 Official Cert Guide CCNA Cloud CLDFND 210-451 Official Cert Guide Gustavo A. A. Santana Copyright© 2016 Pearson Education, Inc. Published by: Cisco Press 800 East 96th Street Indianapolis, IN 46240 USA All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without written permission from the publisher, except for the inclusion of brief quotations in a review. Printed in the United States of America First Printing April 2016 Library of Congress Control Number: 2015957536 ISBN-13: 978-1-58714-700-5 ISBN-10: 1-58714-7009 Warning and Disclaimer ptg17120290 This book is designed to provide information about the CCNA Cloud CLDFND 210-451 exam. Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information is provided on an “as is” basis. The author, Cisco Press, and Cisco Systems, Inc. shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book or from the use of the discs or programs that may accompany it. The opinions expressed in this book belong to the author and are not necessarily those of Cisco Systems, Inc.
    [Show full text]
  • Solving the Virtualization Conundrum
    White Paper Solving the Virtualization Conundrum Collapsing hierarchical, multi-tiered networks of the past into more compact, resilient, feature rich, two-tiered, leaf- spine or SplineTM networks have clear advantages in the data center. The benefits of more scalable and more stable layer 3 networks far outweigh the challenges this architecture creates. Layer 2 networking fabrics of the past lacked stability and scale. This legacy architecture limited workload size, mobility, and confined virtual workloads to a smaller set of physical servers. As virtualization scaled in the data center, the true limitations of these fabrics quickly surfaced. The economics of workload convergence drives compute density and network scale. Similarly, to meet dynamic needs of business stakeholders, growing data centers must deliver better mobility and its administration must be automated. In essence, virtualized networks must scale, be stable and be programmatically administered! What the Internet has taught us is that TCP/IP architectures are reliable, fault tolerant, and built to last. Why create yet another fabric when we can leverage open standards and all the benefits that layer 3 networks provide. With this settled, we can work to develop an overlay technology to span layer two networks over a stable IP infrastructure. This is how Virtual eXtensible LAN (VXLAN) was born. arista.com White Paper At Arista we work to bring VXLAN to the mainstream by co-authoring the standard with industry virtualization leaders. We’re also innovating programmatic services and APIs that automate virtualized workflow management, monitoring, visualization and troubleshooting. VXLAN is designed from the ground up to leverage layer 3 IP underlays and the scale and stability it provides.
    [Show full text]
  • Understanding Linux Internetworking
    White Paper by David Davis, ActualTech Media Understanding Linux Internetworking In this Paper Introduction Layer 2 vs. Layer 3 Internetworking................ 2 The Internet: the largest internetwork ever created. In fact, the Layer 2 Internetworking on term Internet (with a capital I) is just a shortened version of the Linux Systems ............................................... 3 term internetwork, which means multiple networks connected Bridging ......................................................... 3 together. Most companies create some form of internetwork when they connect their local-area network (LAN) to a wide area Spanning Tree ............................................... 4 network (WAN). For IP packets to be delivered from one Layer 3 Internetworking View on network to another network, IP routing is used — typically in Linux Systems ............................................... 5 conjunction with dynamic routing protocols such as OSPF or BGP. You c an e as i l y use Linux as an internetworking device and Neighbor Table .............................................. 5 connect hosts together on local networks and connect local IP Routing ..................................................... 6 networks together and to the Internet. Virtual LANs (VLANs) ..................................... 7 Here’s what you’ll learn in this paper: Overlay Networks with VXLAN ....................... 9 • The differences between layer 2 and layer 3 internetworking In Summary ................................................. 10 • How to configure IP routing and bridging in Linux Appendix A: The Basics of TCP/IP Addresses ....................................... 11 • How to configure advanced Linux internetworking, such as VLANs, VXLAN, and network packet filtering Appendix B: The OSI Model......................... 12 To create an internetwork, you need to understand layer 2 and layer 3 internetworking, MAC addresses, bridging, routing, ACLs, VLANs, and VXLAN. We’ve got a lot to cover, so let’s get started! Understanding Linux Internetworking 1 Layer 2 vs.
    [Show full text]
  • Infrastructure : Netapp Solutions
    Infrastructure NetApp Solutions NetApp October 06, 2021 This PDF was generated from https://docs.netapp.com/us-en/netapp-solutions/infra/rhv- architecture_overview.html on October 06, 2021. Always check docs.netapp.com for the latest. Table of Contents Infrastructure . 1 NVA-1148: NetApp HCI with Red Hat Virtualization. 1 TR-4857: NetApp HCI with Cisco ACI . 84 Workload Performance. 121 Infrastructure NVA-1148: NetApp HCI with Red Hat Virtualization Alan Cowles, Nikhil M Kulkarni, NetApp NetApp HCI with Red Hat Virtualization is a verified, best-practice architecture for the deployment of an on- premises virtual datacenter environment in a reliable and dependable manner. This architecture reference document serves as both a design guide and a deployment validation of the Red Hat Virtualization solution on NetApp HCI. The architecture described in this document has been validated by subject matter experts at NetApp and Red Hat to provide a best-practice implementation for an enterprise virtual datacenter deployment using Red Hat Virtualization on NetApp HCI within your own enterprise datacenter environment. Use Cases The NetApp HCI for Red Hat OpenShift on Red Hat Virtualization solution is architected to deliver exceptional value for customers with the following use cases: 1. Infrastructure to scale on demand with NetApp HCI 2. Enterprise virtualized workloads in Red Hat Virtualization Value Proposition and Differentiation of NetApp HCI with Red Hat Virtualization NetApp HCI provides the following advantages with this virtual infrastructure solution: • A disaggregated architecture that allows for independent scaling of compute and storage. • The elimination of virtualization licensing costs and a performance tax on independent NetApp HCI storage nodes.
    [Show full text]
  • Increase Nfvi Performance and Flexibility
    SOLUTION BRIEF Telecommunications Server Performance Increase NFVi Performance and Flexibility Offload processing from software to hardware to create efficiency with HCL’s 50G Open vSwitch acceleration solution on the Intel® FPGA Programmable Acceleration Card (PAC) N3000. Eliminating the Performance Bottleneck In order to survive in a wildly competitive and ever-evolving industry, communications service providers (CoSPs) need to achieve the best performance possible, overcoming the bottlenecks that slow down their servers. With consistently growing numbers of subscribers, numbers of competitors, and advances in technology, the need for a CoSP to differentiate itself grows concurrently. The need for power efficiency is ever-present, as is the pressure to manage total cost of ownership (TCO) with cost-effective solutions. Intel and HCL had these challenges in mind when they collaborated on a joint solution that features Intel hardware and HCL software. Using the Intel FPGA Programmable Acceleration Card (Intel FPGA PAC) N3000, HCL has created a solution that can dramatically increase performance and preserve flexibility for network functions virtualization infrastructure (NFVi) routing and switching. Open vSwitch (OvS) is a production-quality, multilayer virtual switch that can also implement a software-defined networking (SDN)-based What Is the Intel FPGA approach that is crucial to creating a closed-loop, fully automated solution in NFVi. PAC N3000? With aggressive software optimization to offload NFVi forwarding functionalities The Intel FPGA Programmable to the Intel FPGA PAC N3000, Intel and HCL have created a system that can provide Acceleration Card (Intel FPGA the Intel FPGA–based solution, supported by selected NFVi suppliers. PAC) N3000 is a PAC that has OvS can either forward packets through a kernel-based datapath or by using the the right memory mixture for Linux Data Plane Development Kit (DPDK).
    [Show full text]
  • Linux Networking 101
    The Gorilla ® Guide to… Linux Networking 101 Inside this Guide: • Discover how Linux continues its march toward world domination • Learn basic Linux administration tips • See how easy it can be to build your entire network on a Linux foundation • Find out how Cumulus Linux is your ticket to networking freedom David M. Davis ActualTech Media Helping You Navigate The Technology Jungle! In Partnership With www.actualtechmedia.com The Gorilla Guide To… Linux Networking 101 Author David M. Davis, ActualTech Media Editors Hilary Kirchner, Dream Write Creative, LLC Christina Guthrie, Guthrie Writing & Editorial, LLC Madison Emery, Cumulus Networks Layout and Design Scott D. Lowe, ActualTech Media Copyright © 2017 by ActualTech Media. All rights reserved. No portion of this book may be reproduced or used in any manner without the express written permission of the publisher except for the use of brief quotations. The information provided within this eBook is for general informational purposes only. While we try to keep the information up- to-date and correct, there are no representations or warranties, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the information, products, services, or related graphics contained in this book for any purpose. Any use of this information is at your own risk. ActualTech Media Okatie Village Ste 103-157 Bluffton, SC 29909 www.actualtechmedia.com Entering the Jungle Introduction: Six Reasons You Need to Learn Linux ....................................................... 7 1. Linux is the future ........................................................................ 9 2. Linux is on everything .................................................................. 9 3. Linux is adaptable ....................................................................... 10 4. Linux has a strong community and ecosystem ........................... 10 5.
    [Show full text]
  • Network Service in Openstack Cloud
    Network Service in OpenStack Cloud Yaohui Jin email: [email protected] Sina Weibo: @bright_jin (The slides will be shared in Sina Weipan & Slideshare ) Network & Information Center © jinyh@sjtu Acknowledgement Team: Dr. Xuan Luo, Pengfei Zhang, Xiaosheng Zuo, Zhixing Xu, Xinyu Xu, Jianwen Wei, Baoqing Huang, etc. Prof. Hongfang Yu and team with UESTC Prof. Jianping Wang with CityU HK Engineers, discussion and slides from Intel, SINA, IBM, Cisco, Dell, VMware/EMC, H3C, Huawei, IXIA, … OpenStack Community China OpenStack User Group (COSUG) China OpenStack Cloud League (COSCL) Technical blogs such as blog.ioshints.info, ipspace.net, … © jinyh@sjtu 2 About me 上海交通大学 教授，以前做光通信的，现在改行 做云计算了。。。 上海交通大学 网络信息中心 副主任，其实就是 个苦逼的挨踢网管啊。。。 研究兴趣： 数据中心网络，海量流式数据分析， 云计算架构 © jinyh@sjtu 3 OpenStack in Academia for Research & Operation USC, Information Science Institute Purdue University University of Melbourne San Diego Supercomputer Center Brookhaven National Lab., DOE Argonne National Lab., DOE European Organization for Nuclear Research (CERN) Shanghai Jiao Tong University University of Science & Technology of China University of Electrical Science & Technology of China …… © jinyh@sjtu 4 Agenda Introduction SDN and OpenFlow Network Virtualization Network Virtualization in OpenStack Our Work © jinyh@sjtu 5 The Service Trend "Decoupling infrastructure management from service management can lead to innovation, new business models, and a reduction in the complexity of running services. It is happening in the world of computing, and is poised to happen in networking.“ Jennifer Rexford Professor, Princeton University Last month, VMware paid $1.2B to acquire Nicira for software defined networking (SDN). © jinyh@sjtu 6 Why is Nicira worth $1.2 billion? © jinyh@sjtu 7 SDN and OpenFlow © jinyh@sjtu Software Defined Network (SDN) A network architecture in which the network control plane (OS) is decoupled from the physical topology using open protocols such as OpenFlow.
    [Show full text]
  • A Performance Study of VM Live Migration Over the WAN
    Master Thesis Electrical Engineering April 2015 A Performance Study of VM Live Migration over the WAN TAHA MOHAMMAD CHANDRA SEKHAR EATI Department of Communication Systems Blekinge Institute of Technology SE-371 79 Karlskrona Sweden This thesis is submitted to the School of Computing at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering on Telecommunication Systems. The thesis is equivalent to 40 weeks of full time studies. Contact Information: Author(s): Taha Mohammad, Chandra Sekhar Eati. E-mail: [email protected], [email protected]. University advisor(s): Dr. Dragos Ilie, Department of Communication Systems. University Examiner(s): Prof. Kurt Tutschku, Department of Communication Systems. School of Computing Blekinge Institute of Technology Internet : www.bth.se SE-371 79 Karlskrona Phone : +46 455 38 50 00 Sweden Fax : +46 455 38 50 57 Abstract Virtualization is the key technology that has provided the Cloud computing platforms a new way for small and large enterprises to host their applications by renting the available resources. Live VM migration allows a Virtual Machine to be transferred form one host to another while the Virtual Machine is active and running. The main challenge in Live migration over WAN is maintaining the network connectivity during and after the migration. We have carried out live VM migration over the WAN migrating different sizes of VM memory states and presented our solutions based on Open vSwitch/VXLAN and Cisco GRE approaches. VXLAN provides the mobility support needed to maintain the network connectivity between the client and the Virtual machine.
    [Show full text]
  • Learn About VXLAN in Virtualized Data Center Networks
    Learn About VXLAN in Virtualized Data Center Networks Data centers have rapidly increased their server virtualization over the past decade, resulting in dramatic increases in agility. This, in turn, has created a demand for data center networks that are equally flexible and agile. Virtualization of the network is the next obvious step – decoupling the virtual network from the physical network makes it easier to manage, automate, and orchestrate. One common method being used today to virtualize data center networks is the use of overlay networks. An overlay network sits on top of the physical network, enabling Network overlays are the use of a virtual network of switches, routers, firewalls, load balancers, and so on. created by encapsulating This decoupling of the virtual from the physical enables fast programmatic provision- traffic and tunneling it ing of the network for any application. You no longer have to orchestrate changes over the physical network. Although relatively new to across a set of physical devices. data center networks, Creating a virtual overlay network also benefits the physical, or underlay, network, overlay networks have been used in campus which can now be a simple IP network that is concerned solely with delivering packets networks for years to carry to destinations. An overlay network adds simplicity, resiliency, and scale to the wireless LAN traffic over physical network, another reason overlay networks are gaining popularity. the wired network. Figure 1 illustrates an overlay network. From the perspectives of virtual machine 1 and virtual machine 2 (VM1 and VM2), traffic between them is taking the route shown by the dotted line, going through traditional networking devices such as switches, routers, and firewalls, which are instantiated in the hosts.
    [Show full text]
  • Contrail for the Enterprise | White Paper
    White Paper Contrail for the Enterprise Bringing Networks into the Cloud Era 1 Contrail for the Enterprise White Paper Table of Contents Executive Summary ........................................................................................................................................................................................................ 3 Introduction ........................................................................................................................................................................................................................ 3 Limitations of Today’s Network for Cloud Architectures .................................................................................................................................. 3 Scalability of the Network Edge ......................................................................................................................................................................... 3 Lack of Programmatic APIs ..................................................................................................................................................................................... 4 Inability to Orchestrate Multi-Cloud/Hybrid Cloud Environments ........................................................................................................4 Service Insertion Challenges ................................................................................................................................................................................4
    [Show full text]
  • Vmware Validated Design Reference Architecture Guide
    VMware Validated Design™ Reference Architecture Guide VMware Validated Design for Software- Defined Data Center 2.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-002167-00 VMware Validated Design Reference Architecture Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2016 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Avenue Palo Alto, CA 94304 www.vmware.com © 2016 VMware, Inc. All rights reserved. Page 2 of 208 VMware Validated Design Reference Architecture Guide Contents 1 Purpose and Intended Audience .................................................... 12 2 Architecture Overview .................................................................... 13 2.1 Physical Infrastructure Architecture ............................................................................
    [Show full text]