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