summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
blob: 6719a36143bde1e88f6e09b4ce06f250ab287034 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="relinfo-changes">
  <title>Main Changes</title>

  <para>Below you'll find information about the new features and updates made
  in this release, as well as details on the provided packages and the
  backwards compatibility with previous versions of Enea NFV Access if
  applicable.</para>

  <section id="relinfo-changes-other">
    <title>New Features</title>

    <itemizedlist>
      <listitem>
        <para>uCPE Manager 1.0.1</para>
      </listitem>

      <listitem>
        <para>Support for standard (non-DPDK) interfaces on the virtualized
        networking infrastructure.</para>
      </listitem>

      <listitem>
        <para>Support for OpenvSwitch using kernel datapath.</para>
      </listitem>

      <listitem>
        <para>In-band management extension for VNFs' management plane.</para>
      </listitem>

      <listitem>
        <para>UEFI Secure Boot.</para>
      </listitem>

      <listitem>
        <para>Bare Metal Provisioning.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="open_source">
    <title>Open Source</title>

    <para>For more information about the Open Source packages included, please
    refer to the Enea NFV Access Open Source Reports provided with this
    release.</para>
  </section>

  <section condition="hidden" id="relinfo-backward-compat">
    <title>Compatibility</title>

    <para>In the development of any complex software platform, there is a need
    to strike a balance between backwards compatibility and new development.
    In most cases, compatibility will be maintained as long as reasonably
    possible. Necessary compatibility breaks will be done only as needed and
    in major releases.</para>
  </section>
</chapter>