summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authormrpa <mrpa@enea.se>2020-02-20 16:30:43 +0100
committermrpa <mrpa@enea.se>2020-02-20 16:33:20 +0100
commit2f3895595ef6b37ac4cc011773fd39f0d087ea24 (patch)
tree7d53964cb85570060e866b7e00764894043a56c1 /doc
parent6121bf9e357791eb63c411faf94de3e1f114d2d2 (diff)
downloadel_releases-nfv-access-2f3895595ef6b37ac4cc011773fd39f0d087ea24.tar.gz
Updated rel notes for v2.2.2
Known issues and limitations chapter is updated. Change-Id: Idc3fa545673d1f1356d2feb7892119440b67b53d
Diffstat (limited to 'doc')
-rw-r--r--doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml2
-rw-r--r--doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml186
2 files changed, 165 insertions, 23 deletions
diff --git a/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
index 1a640a3..df317aa 100644
--- a/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/eltf_params_updated.xml
@@ -42,7 +42,7 @@ export PATH=~/bin:$PATH</programlisting></para>
42 correct also compared to the "previous" REL VER in pardoc-distro.xml 42 correct also compared to the "previous" REL VER in pardoc-distro.xml
43 "prev_baseline".</bridgehead> 43 "prev_baseline".</bridgehead>
44 44
45 <para id="EneaLinux_REL_VER"><phrase>2.2.1</phrase></para> 45 <para id="EneaLinux_REL_VER"><phrase>2.2.2</phrase></para>
46 46
47 <para id="Yocto_VER"><phrase>2.4</phrase></para> 47 <para id="Yocto_VER"><phrase>2.4</phrase></para>
48 48
diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
index e2d338e..a218432 100644
--- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
@@ -10,7 +10,8 @@
10 <para><remark>The section further down is generated from JIRA with 10 <para><remark>The section further down is generated from JIRA with
11 gen_known_issues.py, but that script is HARDCODED with affectedversion 11 gen_known_issues.py, but that script is HARDCODED with affectedversion
12 "EL7_3-virtualization" and needs to be adapted when a release info for 12 "EL7_3-virtualization" and needs to be adapted when a release info for
13 another ENFV Access version changes.</remark></para> 13 another ENFV Access version changes.</remark><emphasis
14 role="bold">Product-specific Issues and Limitations</emphasis></para>
14 15
15 <itemizedlist> 16 <itemizedlist>
16 <para><emphasis role="bold">Enea uCPE Manager</emphasis></para> 17 <para><emphasis role="bold">Enea uCPE Manager</emphasis></para>
@@ -27,36 +28,60 @@
27 </listitem> 28 </listitem>
28 29
29 <listitem> 30 <listitem>
30 <para><remark>ELEMCR-1690</remark>There is no keep-alive mechanism in 31 <para><remark>ELCCR-319</remark>After a successful installation or
31 place for the Device Call Home Connection.</para> 32 upgrade, it takes about 2 minutes until the device is accessible from
33 the browser.</para>
32 </listitem> 34 </listitem>
33 35
34 <listitem> 36 <listitem>
35 <para><remark>LXCR-9274</remark>The Call Home functionality does not support 37 <para><remark>ELCCR-349</remark>After uninstalling the uCPE manager
36 having multiple interfaces/routes that go from the device to the 38 using the <filename>uninstall.sh</filename> script, the
37 uCPE Manager. The IP/DNS address might need to be changed to the 39 <literal>ec_postgres</literal> service remains in an abnormal state. If
38 established socket IP.</para> 40 a product has not been successfully installed originally or if the
41 installed resources (files, users, services, databases, environment
42 variables, etc.) have been manually changed/removed, the uninstall may
43 fail and some resources will not be removed from the machine. Reverting
44 resources in the case of a failed uninstall is not implemented.</para>
39 </listitem> 45 </listitem>
40 46
41 <listitem> 47 <listitem>
42 <para><remark>ELCCR-256</remark>The uCPE Manager cannot manage VNFs which 48 <para><remark>ELCCR-371</remark>A software image for NFV Access runs
43 contain special characters in their name.</para> 49 only upon the hardware platform it is built for. Currently, NFV Access
50 supports two separate platforms: Intel atom-c and Intel xeon-d. The user
51 uploading a software image to the uCPE Manager can specify which
52 platform the image belongs to. When upgrading devices that have older
53 versions of NFV Access (2.2.1 and earlier), the device does not provide
54 information about its platform. In such cases, it is not possible to
55 validate if it is acceptable to use a given software image for an
56 upgrade. In more recent versions of NFV Access (2.2.2 onwards), the
57 device supplies its platform and while upgrading a device, the system
58 will validate that the software image being upgraded to is of the same
59 platform type as the device.</para>
44 </listitem> 60 </listitem>
45 61
46 <listitem> 62 <listitem>
47 <para><remark>LXCR-9513</remark>When using In-Band Management on standard 63 <para><remark>LXCR-9088</remark>Automation Framework and Test Harness
48 interfaces (DPDK disabled), stopping and restarting a VNF is not supported. 64 tests require python version 2.7.X. Please make sure it is installed
49 To perform a VNF restart, it has to be deleted and reinstantiated.</para> 65 before using the framework.</para>
50 </listitem> 66 </listitem>
51 67
52 <listitem> 68 <listitem>
53 <para><remark>ELCCR-276</remark>The uCPE Manager does not prevent a user 69 <para><remark>LXCR-????</remark>The Call Home functionality does not
54 from creating multiple <literal>communication</literal> bridges assigned 70 support having multiple interfaces/routes that go from the device to the
55 to the same physical port. Although this is an invalid configuration and 71 uCPE Manager. The IP/DNS address might need to be changed to the
56 OVS itself will not accept it, the configuration screens will incorrectly 72 established socket IP.</para>
57 show that such a configuration is in effect. The user should take care 73 </listitem>
58 while assigning a physical port to a communications bridge to ensure that 74
59 the port being assigned has not already been assigned to another bridge.</para> 75 <listitem>
76 <para><remark>LXCR-9703</remark>Cannot delete a VNF using a bridge with
77 flows defined.</para>
78 </listitem>
79
80 <listitem>
81 <para><remark>LXCR-9799</remark>In case two HDDs installed with NFV
82 Access are attached to the same device, it is possible that NFV Access
83 will boot from the wrong partition. Please avoid having two NFV Access
84 images installed on two HDDs on the same device.</para>
60 </listitem> 85 </listitem>
61 </itemizedlist> 86 </itemizedlist>
62 87
@@ -65,8 +90,10 @@
65 "EL7_3-virtualization" and needs to be adapted when a release info for 90 "EL7_3-virtualization" and needs to be adapted when a release info for
66 another ENFV Access version changes.</remark></para> 91 another ENFV Access version changes.</remark></para>
67 92
68 <itemizedlist condition="hidden"> 93 <para><emphasis role="bold">General Issues and Limitations</emphasis></para>
69 <listitem> 94
95 <itemizedlist>
96 <listitem condition="hidden">
70 <para><emphasis role="bold">PDF navigation</emphasis>: When using links 97 <para><emphasis role="bold">PDF navigation</emphasis>: When using links
71 to open other PDFs, or jump to another place in the same PDF, jumping 98 to open other PDFs, or jump to another place in the same PDF, jumping
72 back sometimes fails. This has been observed when opening a PDF in Adobe 99 back sometimes fails. This has been observed when opening a PDF in Adobe
@@ -74,10 +101,125 @@
74 configured to open PDF files in an external PDF reader. As a workaround, 101 configured to open PDF files in an external PDF reader. As a workaround,
75 open the HTML version of the document.<remark>LXCR-3283</remark></para> 102 open the HTML version of the document.<remark>LXCR-3283</remark></para>
76 </listitem> 103 </listitem>
104
105 <listitem>
106 <para><remark>LXCR-9773</remark>REST API changes for specified modules
107 that might cause backward compatibility issues, are listed below:</para>
108
109 <itemizedlist>
110 <listitem>
111 <para>CustomScripts:</para>
112
113 <para>The <literal>uploadCustomScript()</literal> method takes in an
114 additional argument (device module name). This should not affect
115 current REST clients, since CustomScript functionality is available
116 only for NFV Access 2.2.2.</para>
117 </listitem>
118
119 <listitem>
120 <para>Device Upgrade:</para>
121
122 <para>A new method <literal>-- upload() --</literal> has been added
123 to allow uploads of NFV Access software images to the uCPE Manager.
124 This should not affect current REST clients, since it is a new
125 method.</para>
126 </listitem>
127
128 <listitem>
129 <para>VnfManager:</para>
130
131 <para>A new method <literal>-- upload() --</literal> has been added
132 to allow uploads of VNF images to the uCPE Manager as part of the
133 onboarding process. This should not affect current REST clients,
134 since it is a new method.</para>
135 </listitem>
136
137 <listitem>
138 <para>VcpeAgent (i.e. NFV Access device module):<itemizedlist>
139 <listitem>
140 <para>The system-attributes config table was split into
141 system-attributes-state (operational data) and
142 system-attributes (configuration data).<itemizedlist>
143 <listitem>
144 <para>The configuration data still contains the
145 attributes: device-name, device-description and
146 initial-configuration-complete.</para>
147 </listitem>
148
149 <listitem>
150 <para>The fields device-type, device-version, device-id,
151 device-latitude, and device-longitude are now
152 operational data. device-ip-address has been added as
153 oper data.</para>
154 </listitem>
155
156 <listitem>
157 <para>customer-tag in release version 2.2.1 was a config
158 leaf-list, it is now a leaf called device-customer-tags
159 (comma-separated).</para>
160 </listitem>
161
162 <listitem>
163 <para>mgmt-ip-address has been added as oper data. This
164 attribute was configured within an ovs-bridge of type
165 inband-mgmt.</para>
166 </listitem>
167 </itemizedlist></para>
168 </listitem>
169
170 <listitem>
171 <para>The external-interface-capabilities operational table
172 now has "wan" and "mgmt" Booleans.</para>
173 </listitem>
174
175 <listitem>
176 <para>The external-interface configuration table now has a
177 choice of "wan".</para>
178
179 <para>New fields for this type are mgmt-interface,
180 address-assignment , ip-address, gateway, netmask (only
181 considered if static).</para>
182 </listitem>
183
184 <listitem>
185 <para>In ovs-bridge, for the choice of inband-mgmt, the
186 mgmt-address and mgmt-port fields have been removed (there are
187 no fields left in this choice).</para>
188 </listitem>
189
190 <listitem>
191 <para>In the Host operational table, there are a couple of
192 changes:<itemizedlist>
193 <listitem>
194 <para>The "name" field has been removed, there is still
195 a "host-name" field.</para>
196 </listitem>
197
198 <listitem>
199 <para>A "machine-type" field has been added.</para>
200 </listitem>
201 </itemizedlist></para>
202 </listitem>
203 </itemizedlist></para>
204 </listitem>
205 </itemizedlist>
206 </listitem>
207
208 <listitem>
209 <para>REST clients should see some minor changes depending upon whether
210 they are dealing with version 2.2.1 or 2.2.2 of the device. Code that
211 deals with the system-attributes table, in-band management OVS bridges,
212 or the host operational data might need to be modified.</para>
213
214 <para>The new wan interface type only matters in that you need a
215 wan-mgmt interface configured to create the in-band mgmt. bridge. This
216 should typically happen automatically as part of initial install or
217 upgrade and should not affect the REST clients</para>
218 </listitem>
77 </itemizedlist> 219 </itemizedlist>
78 220
79 <!-- The file with a section below is autocreated by make init --> 221 <!-- The file with a section below is autocreated by make init -->
80 222
81 <!-- <xi:include href="jiraissues_generated.xml" 223 <!-- <xi:include href="jiraissues_generated.xml"
82 xmlns:xi="http://www.w3.org/2001/XInclude" /> --> 224 xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
83</chapter> 225</chapter> \ No newline at end of file