diff options
Diffstat (limited to 'doc/book-enea-nfv-access-reference-guide-intel/doc/overview.xml')
| -rw-r--r-- | doc/book-enea-nfv-access-reference-guide-intel/doc/overview.xml | 153 |
1 files changed, 0 insertions, 153 deletions
diff --git a/doc/book-enea-nfv-access-reference-guide-intel/doc/overview.xml b/doc/book-enea-nfv-access-reference-guide-intel/doc/overview.xml deleted file mode 100644 index 3439937..0000000 --- a/doc/book-enea-nfv-access-reference-guide-intel/doc/overview.xml +++ /dev/null | |||
| @@ -1,153 +0,0 @@ | |||
| 1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
| 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | ||
| 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | ||
| 4 | <chapter id="overview"> | ||
| 5 | <title>Overview</title> | ||
| 6 | |||
| 7 | <para>The Enea NFV Access Reference Guide seeks to provide further | ||
| 8 | information that will help users understand the high-level architecture | ||
| 9 | and features of the Enea NFV Access Platform. Focus is placed | ||
| 10 | on data-path and virtualization components.</para> | ||
| 11 | |||
| 12 | <section id="description"> | ||
| 13 | <title>Enea NFV Access Description</title> | ||
| 14 | |||
| 15 | <para>Enea NFV Access is a lightweight virtualization software designed | ||
| 16 | for deployment on edge devices at customer premises. Streamlined for high | ||
| 17 | networking performance and minimal footprints for both host platform and | ||
| 18 | VNFs, it enables very high compute density.</para> | ||
| 19 | |||
| 20 | <para>Enea NFV Access also provides a foundation for vCPE agility and | ||
| 21 | innovation, reducing cost and complexity for computing at the network | ||
| 22 | edge. It supports multiple architectures and scales from small white box | ||
| 23 | edge devices up to high-end network servers. Thanks to the streamlined | ||
| 24 | footprint, Enea NFV Access can be deployed on systems as small as single | ||
| 25 | 2-core ARM devices. It scales up to clustered 24 core x86 Xeon servers and | ||
| 26 | beyond, allowing multiple VNFs on the same machine, and eliminating the | ||
| 27 | need to use different virtualization software for different hardware | ||
| 28 | platforms, saving costs through single source provisioning.</para> | ||
| 29 | |||
| 30 | <para>Optimized virtual networking performance provides low virtualized | ||
| 31 | networking latency, high virtualized networking throughput (10 Gb wire | ||
| 32 | speed), and low processing overhead. It allows high compute density on | ||
| 33 | white box hardware, maintaining performance when moving functionality from | ||
| 34 | application specific appliances to software on standard hardware. The | ||
| 35 | optimized boot speed minimizes the time from reboot to active services, | ||
| 36 | improving availability.</para> | ||
| 37 | |||
| 38 | <para>Enea NFV Access provides virtualization using both containers and | ||
| 39 | virtual machines. Containers provide lightweight virtualization for a | ||
| 40 | smaller VNF footprint and a very short time interval from start to enabled | ||
| 41 | network services. VMs provide virtualization with secure VNF sandboxing | ||
| 42 | and is the preferred virtualization method for OPNFV compliance. Enea NFV | ||
| 43 | Access allows combinations of containers and VMs for highest possible user | ||
| 44 | adaptability.</para> | ||
| 45 | |||
| 46 | <para>Flexible interfaces for VNF lifecycle management and service | ||
| 47 | function chaining, are important to allow a smooth transition from | ||
| 48 | traditional network appliances to virtualized network functions in | ||
| 49 | existing networks, as they plug into a variety of interfaces. Enea NFV | ||
| 50 | Access supports VNF lifecycle management and service function chaining | ||
| 51 | through OpenStack, NETCONF, REST, CLI and Docker. It integrates a powerful | ||
| 52 | device management framework that enables full FCAPS functionality for | ||
| 53 | powerful management of the platform.</para> | ||
| 54 | |||
| 55 | <para>Building on open source, Enea NFV Access prevents vendor lock-in | ||
| 56 | thanks to its completely open standards and interfaces. Unlike proprietary | ||
| 57 | platforms that either do not allow decoupling of software from hardware, | ||
| 58 | or prevent NVF portability, Enea NFV Access includes optimized components | ||
| 59 | with open interfaces to allow full portability and | ||
| 60 | interoperability.</para> | ||
| 61 | </section> | ||
| 62 | |||
| 63 | <section id="components"> | ||
| 64 | <title>Components</title> | ||
| 65 | |||
| 66 | <para>Enea NFV Access is built on highly optimized open source and | ||
| 67 | value-adding components that provide standard interfaces but with boosted | ||
| 68 | performance.</para> | ||
| 69 | |||
| 70 | <mediaobject> | ||
| 71 | <imageobject role="fo"> | ||
| 72 | <imagedata align="center" | ||
| 73 | fileref="images/virtual_network_functions.svg" /> | ||
| 74 | </imageobject> | ||
| 75 | |||
| 76 | <imageobject role="html"> | ||
| 77 | <imagedata align="center" | ||
| 78 | fileref="images/virtual_network_functions.png" /> | ||
| 79 | </imageobject> | ||
| 80 | </mediaobject> | ||
| 81 | |||
| 82 | <para>The Access Platform includes the following key components:</para> | ||
| 83 | |||
| 84 | <itemizedlist> | ||
| 85 | <listitem> | ||
| 86 | <para>Linux Kernel - Optimized Linux kernel with the focus on vCPE | ||
| 87 | systems characteristics.</para> | ||
| 88 | </listitem> | ||
| 89 | |||
| 90 | <listitem> | ||
| 91 | <para>KVM - Virtualization with virtual machines. KVM is the standard | ||
| 92 | virtualization engine for Linux based systems.</para> | ||
| 93 | </listitem> | ||
| 94 | |||
| 95 | <listitem> | ||
| 96 | <para>Docker - Docker provides a lightweight configuration using | ||
| 97 | containers. Docker is the standard platform for container | ||
| 98 | virtualization.</para> | ||
| 99 | </listitem> | ||
| 100 | |||
| 101 | <listitem> | ||
| 102 | <para>Virtual switching - Optimized OVS-DPDK provides high throughput | ||
| 103 | and low latency.</para> | ||
| 104 | </listitem> | ||
| 105 | |||
| 106 | <listitem> | ||
| 107 | <para>Edge Link - Edge Link provides interfaces to orchestration for | ||
| 108 | centralized VNF lifecycle management and service function | ||
| 109 | chaining:</para> | ||
| 110 | |||
| 111 | <orderedlist> | ||
| 112 | <listitem> | ||
| 113 | <para>NETCONF</para> | ||
| 114 | </listitem> | ||
| 115 | |||
| 116 | <listitem> | ||
| 117 | <para>Docker</para> | ||
| 118 | </listitem> | ||
| 119 | |||
| 120 | <listitem> | ||
| 121 | <para>REST</para> | ||
| 122 | </listitem> | ||
| 123 | |||
| 124 | <listitem> | ||
| 125 | <para>CLI</para> | ||
| 126 | </listitem> | ||
| 127 | </orderedlist> | ||
| 128 | </listitem> | ||
| 129 | |||
| 130 | <listitem> | ||
| 131 | <para>APT packet management - Feature rich repository of prebuilt open | ||
| 132 | source packages for extending and adapting the platform using APT | ||
| 133 | Package Management.</para> | ||
| 134 | </listitem> | ||
| 135 | |||
| 136 | <listitem> | ||
| 137 | <para>CLI based VNF management - CLI access over virsh and | ||
| 138 | libvirt.</para> | ||
| 139 | </listitem> | ||
| 140 | |||
| 141 | <listitem> | ||
| 142 | <para>FCAPS framework - The device management framework for managing | ||
| 143 | the platform is capable of providing full FCAPS functionality to | ||
| 144 | orchestration or network management systems.</para> | ||
| 145 | </listitem> | ||
| 146 | |||
| 147 | <listitem> | ||
| 148 | <para>Data plane - High performance data plane that includes the DPDK | ||
| 149 | optimized data plane driver.</para> | ||
| 150 | </listitem> | ||
| 151 | </itemizedlist> | ||
| 152 | </section> | ||
| 153 | </chapter> | ||