summaryrefslogtreecommitdiffstats
path: root/book-enea-nfv-core-release-info/doc/main_changes.xml
blob: b79237d37ce7a24a9e9c8037a86b45e6a7fc0dde (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
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="main_changes">
  <title>Main Changes in this Release</title>

  <section id="sw_comps_upd">
    <title>Software Components Updates</title>

    <itemizedlist>
      <listitem>
        <para>Migrated from Openstack Newton to OpenStack Ocata.</para>
      </listitem>

      <listitem>
        <para>Installer has been upgraded from Fuel 10 to Fuel 11.</para>
      </listitem>

      <listitem>
        <para>Upgraded OpenVSwitch from 2.7 to 2.9</para>
      </listitem>

      <listitem>
        <para>Upgraded DPDK from 16.11 to 17.11.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="mixed_arch">
    <title>Mixed Arch Deployment</title>

    <para>Enea NFV Core 1.1 can be installed on a cluster consisting of
    servers with mixed CPU architectures. The user can deploy x86 controllers
    and a combination of x86 and aarch64 compute nodes.</para>
  </section>

  <section id="dvr">
    <title>Distributed Virtual Routing</title>

    <para>DVR support was validated, as it provides more efficient routing and
    floating IP assignment directly at Compute node level.</para>
  </section>

  <section id="lacp">
    <title>Link Aggregation with LACP</title>

    <para>Enea NFV Core 1.1 includes support for Link Aggregation Control
    Protocol (LACP) (802.3ad) on data and control plane interfaces. I..e. -
    specific Compute and Controller roles can now be assigned to network bonds
    as well.</para>
  </section>

  <section id="post_dep">
    <title>Post-Deploy Scripts for Provider Networks</title>

    <para>This is a collection of scripts allowing the user to configure
    OpenStack Provider Networks, which offer Layer-2 connectivity to instances
    with optional support for DHCP and metadata services.</para>
  </section>
</chapter>