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