diff options
author | Sona Sarmadi <sona.sarmadi@enea.com> | 2019-03-06 12:59:30 +0100 |
---|---|---|
committer | Martin Borg <martin.borg@enea.com> | 2019-03-07 12:24:46 +0100 |
commit | 5888e17e6cb84449c8a54fd9f48c1714f4b75177 (patch) | |
tree | b5d26626d7cd7a016b0b13ad2d65d11d7002a7e4 | |
parent | e7057b8274dcf386b95a35db9828694037e0ce63 (diff) | |
download | el_releases-nfv-access-5888e17e6cb84449c8a54fd9f48c1714f4b75177.tar.gz |
AccessDocs: update RelInfo and GettingStarted
- add release content in the rel info
- remove the reference to step 7, it is not correct
- remove picturece from add a device (from Manual Configuration
and ZTP, Adding a Device)and explain the fiels only in one section
- add reference to the grub configuration file in the Reference Guide
- fix SSH Password/Private Key/Passphrase
Change-Id: I16a3880c899f53ae1d5412aa7445b36d656d92c0
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>
-rw-r--r-- | doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml | 236 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml | 3 | ||||
-rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/add_a_device.png | bin | 28786 -> 23178 bytes | |||
-rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/add_a_device_callhome.png | bin | 0 -> 23239 bytes | |||
-rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/managed_element.png | bin | 24677 -> 0 bytes | |||
-rwxr-xr-x | doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png | bin | 39569 -> 19864 bytes | |||
-rw-r--r-- | doc/book-enea-nfv-access-release-info/doc/about_release.xml | 79 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml | 23 | ||||
-rw-r--r-- | doc/book-enea-nfv-access-release-info/doc/main_changes.xml | 15 |
9 files changed, 154 insertions, 202 deletions
diff --git a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml index 89f6961..861c739 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml | |||
@@ -1,4 +1,4 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | <chapter id="configuration_provision"> | 2 | <chapter id="configuration_provision"> |
3 | <title>Device Configuration and Provisioning</title> | 3 | <title>Device Configuration and Provisioning</title> |
4 | 4 | ||
@@ -12,89 +12,73 @@ | |||
12 | <para><emphasis role="bold">How to add a board to the management system | 12 | <para><emphasis role="bold">How to add a board to the management system |
13 | </emphasis></para> | 13 | </emphasis></para> |
14 | 14 | ||
15 | <orderedlist> | 15 | <para>Add the boards running NFV Access to the management system. This is |
16 | <listitem> | 16 | done by using the <literal>Devices -> Manage -> Add</literal> menu. |
17 | <para>Add the boards running NFV Access to the management system | 17 | Supply information about the board running NFV Access, and set the |
18 | (Devices -> Manage-> Add):</para> | 18 | parameters that will be used to connect to the board. The relevant |
19 | 19 | parameters are described below:</para> | |
20 | <figure> | ||
21 | <title>Manage Devices</title> | ||
22 | 20 | ||
23 | <mediaobject> | 21 | <itemizedlist> |
24 | <imageobject> | 22 | <listitem> |
25 | <imagedata align="center" fileref="images/manage_devices.png" | 23 | <para>Type. The type of device to be added, i.e <literal>Enea |
26 | scale="70" /> | 24 | universal uCPE </literal>.</para> |
27 | </imageobject> | ||
28 | </mediaobject> | ||
29 | </figure> | ||
30 | </listitem> | 25 | </listitem> |
26 | </itemizedlist> | ||
31 | 27 | ||
28 | <itemizedlist> | ||
32 | <listitem> | 29 | <listitem> |
33 | <para>Supply information about the board running NFV Access, and set | 30 | <para>Name. The name by which the device is referred to in the uCPE |
34 | the parameters that will be used to connect to the board (port: 22; | 31 | Manager.</para> |
35 | SSH username/password: <emphasis | ||
36 | role="bold">root/root</emphasis>):</para> | ||
37 | |||
38 | <figure> | ||
39 | <title>Managed Element</title> | ||
40 | |||
41 | <mediaobject> | ||
42 | <imageobject> | ||
43 | <imagedata align="center" fileref="images/managed_element.png" | ||
44 | scale="80" /> | ||
45 | </imageobject> | ||
46 | </mediaobject> | ||
47 | </figure> | ||
48 | </listitem> | 32 | </listitem> |
33 | </itemizedlist> | ||
49 | 34 | ||
35 | <itemizedlist> | ||
50 | <listitem> | 36 | <listitem> |
51 | <para>In the main screen, check that the management system has | 37 | <para>IP Address. IP address of the device. If a device is installed |
52 | connected to the board (System -> Unplaced):</para> | 38 | under a local/private network and not directly visible to the uCPE |
53 | 39 | Manager machine, the Gateway IP of the private network must be | |
54 | <figure> | 40 | used.</para> |
55 | <title>Connecting the System</title> | ||
56 | |||
57 | <mediaobject> | ||
58 | <imageobject> | ||
59 | <imagedata align="center" fileref="images/unplaced.png" | ||
60 | scale="80" /> | ||
61 | </imageobject> | ||
62 | </mediaobject> | ||
63 | </figure> | ||
64 | </listitem> | 41 | </listitem> |
42 | </itemizedlist> | ||
65 | 43 | ||
44 | <itemizedlist> | ||
66 | <listitem> | 45 | <listitem> |
67 | <para>Place the new device on the map by right clicking on the map | 46 | <para>SSH Port. The NETCONF Port used for communications. This is a |
68 | tab:</para> | 47 | relevant parameter if the standard NETCONF SSH (i.e. not Call-Home) is |
69 | 48 | being used. Default is set to 22.</para> | |
70 | <figure> | 49 | </listitem> |
71 | <title>Placing the Device</title> | 50 | </itemizedlist> |
72 | 51 | ||
73 | <mediaobject> | 52 | <itemizedlist> |
74 | <imageobject> | 53 | <listitem> |
75 | <imagedata align="center" fileref="images/place_device.png" | 54 | <para>SSH User Name. The user name for SSH connectivity. Default user |
76 | scale="55" /> | 55 | is <literal>root</literal>.</para> |
77 | </imageobject> | ||
78 | </mediaobject> | ||
79 | </figure> | ||
80 | </listitem> | 56 | </listitem> |
57 | </itemizedlist> | ||
81 | 58 | ||
59 | <itemizedlist> | ||
82 | <listitem> | 60 | <listitem> |
83 | <para>Follow the same steps listed above, to add other boards to the | 61 | <para>SSH Password. Leave this blank.</para> |
84 | management system:</para> | 62 | </listitem> |
63 | </itemizedlist> | ||
85 | 64 | ||
86 | <figure> | 65 | <itemizedlist> |
87 | <title>Adding more boards</title> | 66 | <listitem> |
67 | <para>Device Calls Home. This checkbox indicates the direction of | ||
68 | device communications. In the Manual Configuration, leave this box | ||
69 | blank. For more info about how to add a device please refer to | ||
70 | <link linkend="adding_a_device">Zero Touch Provisioning, Adding a Device</link>.</para> | ||
71 | </listitem> | ||
72 | </itemizedlist> | ||
88 | 73 | ||
89 | <mediaobject> | 74 | <itemizedlist> |
90 | <imageobject> | 75 | <listitem> |
91 | <imagedata align="center" fileref="images/adding_boards.png" | 76 | <para>Device ID. The unique instance ID of the device. This is what |
92 | scale="55" /> | 77 | links a device to its day-0 configuration (stored in the offline |
93 | </imageobject> | 78 | configuration system). It is a required field if you want to perform |
94 | </mediaobject> | 79 | Zero-Touch Provisioning.</para> |
95 | </figure> | ||
96 | </listitem> | 80 | </listitem> |
97 | </orderedlist> | 81 | </itemizedlist> |
98 | </section> | 82 | </section> |
99 | 83 | ||
100 | <section id="host_int_net_config"> | 84 | <section id="host_int_net_config"> |
@@ -226,9 +210,9 @@ | |||
226 | <literal>Automatic install</literal> step is reached, enter the option | 210 | <literal>Automatic install</literal> step is reached, enter the option |
227 | menu <literal>Customize kernel parameters</literal> and set the | 211 | menu <literal>Customize kernel parameters</literal> and set the |
228 | <literal>uCPE Manager IP address</literal>. Please check <xref | 212 | <literal>uCPE Manager IP address</literal>. Please check <xref |
229 | linkend="install_ena_stick" />, step 7 for how to set the uCPE Manager IP | 213 | linkend="install_ena_stick" />, for how to set the uCPE Manager IP address |
230 | address at boot time. The Device ID will be listed in the installer under | 214 | at boot time. The Device ID will be listed in the installer under the |
231 | the <literal>Customize kernel parameters</literal> menu.</para> | 215 | <literal>Customize kernel parameters</literal> menu.</para> |
232 | 216 | ||
233 | <para>With the address parameter set, run | 217 | <para>With the address parameter set, run |
234 | <literal>list_deviceID.sh</literal> after NFV Access is installed and | 218 | <literal>list_deviceID.sh</literal> after NFV Access is installed and |
@@ -238,7 +222,8 @@ | |||
238 | <para>It is possible to let NFV Access know the uCPE Manager IP address | 222 | <para>It is possible to let NFV Access know the uCPE Manager IP address |
239 | at run-time by setting <literal>vcpemgr=<IP></literal> as a kernel | 223 | at run-time by setting <literal>vcpemgr=<IP></literal> as a kernel |
240 | boot parameter in the grub configuration file. Reboot is required after | 224 | boot parameter in the grub configuration file. Reboot is required after |
241 | this update.</para> | 225 | this update. For additional information about grub configuration, please |
226 | refer to the Enea NFV Access Reference Guide provided with your release.</para> | ||
242 | 227 | ||
243 | <para>This step needs to be done each time the uCPE Manager host changes | 228 | <para>This step needs to be done each time the uCPE Manager host changes |
244 | the IP address.</para> | 229 | the IP address.</para> |
@@ -251,87 +236,14 @@ | |||
251 | <title>Adding a Device</title> | 236 | <title>Adding a Device</title> |
252 | 237 | ||
253 | <para>The uCPE Manager must be configured to bring the target device | 238 | <para>The uCPE Manager must be configured to bring the target device |
254 | under management. This is done by using the <literal>Devices -> | 239 | under management. This is done by selecting <literal>Device Calls |
255 | Manage -> Add</literal> menu:</para> | 240 | Home</literal> checkbox when adding a device. When Device Calls |
256 | 241 | Home checkbox is checked, the device will initiate a | |
257 | <figure> | 242 | connection by opening a socket to the uCPE Manager for NETCONF |
258 | <title>Adding a Device</title> | 243 | traffic (over SSH), while the uCPE Manager waits for device connection.</para> |
259 | 244 | ||
260 | <mediaobject> | 245 | <para>For more info about how to add a device please refer to |
261 | <imageobject> | 246 | <link linkend="man_config">Manual Configuration</link>.</para> |
262 | <imagedata align="center" fileref="images/add_a_device.png" | ||
263 | scale="50" /> | ||
264 | </imageobject> | ||
265 | </mediaobject> | ||
266 | </figure> | ||
267 | |||
268 | <para>The relevant parameters on this screen are described below:</para> | ||
269 | |||
270 | <itemizedlist> | ||
271 | <listitem> | ||
272 | <para>Type. The type of device to be added, i.e <literal>Enea | ||
273 | universal uCPE </literal>.</para> | ||
274 | </listitem> | ||
275 | </itemizedlist> | ||
276 | |||
277 | <itemizedlist> | ||
278 | <listitem> | ||
279 | <para>Name. The name by which the device is referred to in the uCPE | ||
280 | Manager.</para> | ||
281 | </listitem> | ||
282 | </itemizedlist> | ||
283 | |||
284 | <itemizedlist> | ||
285 | <listitem> | ||
286 | <para>IP Address. IP address of the device. If a device is installed | ||
287 | under a local/private network and not directly visible to the uCPE | ||
288 | Manager machine, the Gateway IP of the private network must be | ||
289 | used.</para> | ||
290 | </listitem> | ||
291 | </itemizedlist> | ||
292 | |||
293 | <itemizedlist> | ||
294 | <listitem> | ||
295 | <para>SSH Port. The NETCONF Port used for communications. This is a | ||
296 | relevant parameter if the standard NETCONF SSH (i.e. not Call-Home) | ||
297 | is being used. Default is set to 22.</para> | ||
298 | </listitem> | ||
299 | </itemizedlist> | ||
300 | |||
301 | <itemizedlist> | ||
302 | <listitem> | ||
303 | <para>SSH User Name. The user name for SSH connectivity. Default | ||
304 | user is <literal>root</literal>.</para> | ||
305 | </listitem> | ||
306 | </itemizedlist> | ||
307 | |||
308 | <itemizedlist> | ||
309 | <listitem> | ||
310 | <para>SSH Password/Private Key/Passphrase. The Authentication | ||
311 | Credentials, use one of the aforementioned as appropriate. Default | ||
312 | password is empty.</para> | ||
313 | </listitem> | ||
314 | </itemizedlist> | ||
315 | |||
316 | <itemizedlist> | ||
317 | <listitem> | ||
318 | <para>Device Calls Home. This checkbox indicates the direction of | ||
319 | device communications. When cleared, the uCPE Manager will initiate | ||
320 | a connection to the device. When checked, the device will initiate a | ||
321 | connection by opening a socket to the uCPE Manager for NETCONF | ||
322 | traffic (over SSH), while the uCPE Manager waits for device | ||
323 | connection.</para> | ||
324 | </listitem> | ||
325 | </itemizedlist> | ||
326 | |||
327 | <itemizedlist> | ||
328 | <listitem> | ||
329 | <para>Device ID. The unique instance ID of the device. This is what | ||
330 | links a device to its day-0 configuration (stored in the offline | ||
331 | configuration system). It is a required field if you want to perform | ||
332 | Zero-Touch Provisioning.</para> | ||
333 | </listitem> | ||
334 | </itemizedlist> | ||
335 | </section> | 247 | </section> |
336 | 248 | ||
337 | <section id="offline_configuration"> | 249 | <section id="offline_configuration"> |
@@ -545,6 +457,20 @@ | |||
545 | <section id="onboarding_a_bundled_vnf_wizard"> | 457 | <section id="onboarding_a_bundled_vnf_wizard"> |
546 | <title>Onboarding a VNF VM Image using the Onboarding Wizard</title> | 458 | <title>Onboarding a VNF VM Image using the Onboarding Wizard</title> |
547 | 459 | ||
460 | <para><emphasis role="bold">How to onboard a VNF onto the uCPE Manager | ||
461 | using the Onboarding Wizard</emphasis></para> | ||
462 | |||
463 | <orderedlist> | ||
464 | <listitem> | ||
465 | <para>Click the <literal>On-board</literal> button.</para> | ||
466 | </listitem> | ||
467 | |||
468 | <listitem> | ||
469 | <para>When prompted by the following UI, make sure the | ||
470 | <literal>VNF Image</literal> radio button is selected.</para> | ||
471 | </listitem> | ||
472 | </orderedlist> | ||
473 | |||
548 | <para>If you click the <literal>VM Image</literal> radio button at the | 474 | <para>If you click the <literal>VM Image</literal> radio button at the |
549 | top of the onboarding screen, you will get a pop-up containing fields | 475 | top of the onboarding screen, you will get a pop-up containing fields |
550 | which you can fill, suppling the necessary information about the VNF. | 476 | which you can fill, suppling the necessary information about the VNF. |
@@ -673,6 +599,12 @@ | |||
673 | <para><emphasis role="bold">NoCloud</emphasis>. This is a simpler | 599 | <para><emphasis role="bold">NoCloud</emphasis>. This is a simpler |
674 | method that uses only one cloud init file (User-Data).</para> | 600 | method that uses only one cloud init file (User-Data).</para> |
675 | </listitem> | 601 | </listitem> |
602 | |||
603 | <listitem> | ||
604 | <para><emphasis role="bold">ISO</emphasis>. Pre-cooked cloud-init | ||
605 | image. This image must be created by user according to VNF | ||
606 | requirements.</para> | ||
607 | </listitem> | ||
676 | </itemizedlist> | 608 | </itemizedlist> |
677 | 609 | ||
678 | <para>The Cloud-Init Disk Type field must be set to either | 610 | <para>The Cloud-Init Disk Type field must be set to either |
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml index 22ee80e..661b951 100644 --- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml +++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml | |||
@@ -226,7 +226,8 @@ sdb 8:0 0 111.8G 0 disk | |||
226 | </listitem> | 226 | </listitem> |
227 | 227 | ||
228 | <listitem> | 228 | <listitem> |
229 | <para>Copy the HDDIMG image to the USB stick, e.g:<programlisting>sudo dd if=./enea-nfv-access-edgelink-netconf-<target>.hddimg of=/dev/sdb bs=4M conv=fsync</programlisting></para> | 229 | <para>Copy the HDDIMG image to the USB stick, e.g:<programlisting>sudo dd if=./enea-nfv-access-edgelink-netconf-<target>.hddimg \ |
230 | of=/dev/sdb bs=4M conv=fsync</programlisting></para> | ||
230 | </listitem> | 231 | </listitem> |
231 | </orderedlist> | 232 | </orderedlist> |
232 | 233 | ||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device.png b/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device.png index 8368e61..5d52334 100755 --- a/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device.png +++ b/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device.png | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device_callhome.png b/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device_callhome.png new file mode 100755 index 0000000..eaf224b --- /dev/null +++ b/doc/book-enea-nfv-access-getting-started/doc/images/add_a_device_callhome.png | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/managed_element.png b/doc/book-enea-nfv-access-getting-started/doc/images/managed_element.png deleted file mode 100755 index 9ab7284..0000000 --- a/doc/book-enea-nfv-access-getting-started/doc/images/managed_element.png +++ /dev/null | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png index 8df385e..da52202 100755 --- a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png +++ b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png | |||
Binary files differ | |||
diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml index d63c171..f4f30b5 100644 --- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml +++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml | |||
@@ -1,4 +1,4 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> |
4 | <chapter id="relinfo-about-release"> | 4 | <chapter id="relinfo-about-release"> |
@@ -26,16 +26,58 @@ | |||
26 | <section id="release-content"> | 26 | <section id="release-content"> |
27 | <title>Enea NFV Access Release Content</title> | 27 | <title>Enea NFV Access Release Content</title> |
28 | 28 | ||
29 | <para>The release directory structure is detailed below:</para> | 29 | <para>The release contents is detailed below:</para> |
30 | 30 | ||
31 | <programlisting>-- Documentation. Enea NFV Access documentation | 31 | <itemizedlist> |
32 | -- x86-64 | 32 | <listitem> |
33 | -- atom-c3000 | 33 | <para>Enea_NFV_Access_XeonD_2.2.zip</para> |
34 | enea-nfv-access-edgelink-netconf-atom-c3000.hddimg | 34 | </listitem> |
35 | HDD image for bootable USB stick installer | 35 | |
36 | -- xeon-d | 36 | <listitem> |
37 | enea-nfv-access-edgelink-netconf-xeon-d.hddimg | 37 | <para>Enea_NFV_Access_C3000_2.2.zip</para> |
38 | HDD image for bootable USB stick installer</programlisting> | 38 | </listitem> |
39 | |||
40 | <listitem> | ||
41 | <para>uCPEManager-1.0-Windows.zip</para> | ||
42 | </listitem> | ||
43 | |||
44 | <listitem> | ||
45 | <para>uCPEManager-1.0-CentOS.zip</para> | ||
46 | </listitem> | ||
47 | |||
48 | <listitem> | ||
49 | <para>ena22_automation_and_systemtest.zip</para> | ||
50 | </listitem> | ||
51 | |||
52 | <listitem> | ||
53 | <para>IPerf VNF Bundle (Iperf.zip)</para> | ||
54 | </listitem> | ||
55 | |||
56 | <listitem> | ||
57 | <para>Fortigate VNF Bundle (fortigate-vnf.rar)</para> | ||
58 | </listitem> | ||
59 | |||
60 | <listitem> | ||
61 | <para>Fortigate VNF Example Configurations | ||
62 | (FortigateVNF_example_configuration.tar.gz)</para> | ||
63 | </listitem> | ||
64 | |||
65 | <listitem> | ||
66 | <para>Packet Generator VNF Bundle (PacketGenerator.zip)</para> | ||
67 | </listitem> | ||
68 | |||
69 | <listitem> | ||
70 | <para>TestPmdForwarder VNF Bundle (TestPmdForwarder.zip)</para> | ||
71 | </listitem> | ||
72 | |||
73 | <listitem> | ||
74 | <para>TestPmdTerminator VNF Bundle (TestPmdTerminator.zip)</para> | ||
75 | </listitem> | ||
76 | |||
77 | <listitem> | ||
78 | <para>ClavisterCosStream VNF Bundle (ClavisterCosStream.zip)</para> | ||
79 | </listitem> | ||
80 | </itemizedlist> | ||
39 | 81 | ||
40 | <programlisting condition="arm">-- documentation/ | 82 | <programlisting condition="arm">-- documentation/ |
41 | /* Enea NFV Access documentation */ | 83 | /* Enea NFV Access documentation */ |
@@ -110,7 +152,7 @@ | |||
110 | use-cases.</para> | 152 | use-cases.</para> |
111 | </listitem> | 153 | </listitem> |
112 | 154 | ||
113 | <!-- <listitem> | 155 | <!-- <listitem> |
114 | <para>Enea NFV Access VNF Onboarding Guide. Describes the process | 156 | <para>Enea NFV Access VNF Onboarding Guide. Describes the process |
115 | of onboarding a new VNF onto the uCPE Manager.</para> | 157 | of onboarding a new VNF onto the uCPE Manager.</para> |
116 | </listitem>--> | 158 | </listitem>--> |
@@ -123,15 +165,18 @@ | |||
123 | with Enea NFV Access.</para> | 165 | with Enea NFV Access.</para> |
124 | </listitem> | 166 | </listitem> |
125 | 167 | ||
126 | <listitem condition="hidden"> | 168 | <listitem> |
127 | <para>Enea NFV Access Test Report. Summarizes the test results for the | 169 | <para>Enea NFV Access uCPE Manager Open-Source Report</para> |
128 | Enea NFV Access release.</para> | 170 | </listitem> |
171 | |||
172 | <listitem> | ||
173 | <para>Enea NFV Access Automation Framework and Test Harness User | ||
174 | Guide</para> | ||
129 | </listitem> | 175 | </listitem> |
130 | 176 | ||
131 | <listitem condition="hidden"> | 177 | <listitem condition="hidden"> |
132 | <para>Enea NFV Access Security Report. Lists all security fixes | 178 | <para>Enea NFV Access System Test Specification</para> |
133 | included in this release of Enea NFV Access.</para> | ||
134 | </listitem> | 179 | </listitem> |
135 | </itemizedlist> | 180 | </itemizedlist> |
136 | </section> | 181 | </section> |
137 | </chapter> | 182 | </chapter> \ No newline at end of file |
diff --git a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml index 8202d78..4975ca3 100644 --- a/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml +++ b/doc/book-enea-nfv-access-release-info/doc/getting_enea_nfv_access.xml | |||
@@ -18,28 +18,7 @@ | |||
18 | 18 | ||
19 | <listitem> | 19 | <listitem> |
20 | <para>From the right corner of the top main menu, choose the | 20 | <para>From the right corner of the top main menu, choose the |
21 | <literal>Access</literal> section and download the needed artifacts: | 21 | <literal>Access</literal> section.</para> |
22 | </para> | ||
23 | |||
24 | <itemizedlist spacing="compact"> | ||
25 | <listitem> | ||
26 | <para>uCPEManager-<version>-Centos.tar.gz (ElementCenter for | ||
27 | CentOS).</para> | ||
28 | </listitem> | ||
29 | |||
30 | <listitem> | ||
31 | <para>uCPEManager-<version>-Windows.zip (ElementCenter for | ||
32 | Windows).</para> | ||
33 | </listitem> | ||
34 | |||
35 | <listitem> | ||
36 | <para>Enea_NFV_Access_XeonD_2.2.</para> | ||
37 | </listitem> | ||
38 | |||
39 | <listitem> | ||
40 | <para>Enea_NFV_Access_IntelC3000_2.2.</para> | ||
41 | </listitem> | ||
42 | </itemizedlist> | ||
43 | </listitem> | 22 | </listitem> |
44 | 23 | ||
45 | <listitem> | 24 | <listitem> |
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml index 3b44d5a..86244f6 100644 --- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml +++ b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml | |||
@@ -14,26 +14,21 @@ | |||
14 | 14 | ||
15 | <itemizedlist> | 15 | <itemizedlist> |
16 | <listitem> | 16 | <listitem> |
17 | <para>Integrated Element ODM 4.0.3: FCAPS framework with NETCONF and | 17 | <para>uCPE Manager 1.0.</para> |
18 | Yang</para> | ||
19 | </listitem> | ||
20 | |||
21 | <listitem condition="hidden"> | ||
22 | <para>EdgeLink Netconf : NETCONF based VNF lifecycle Management | ||
23 | Tool</para> | ||
24 | </listitem> | 18 | </listitem> |
25 | 19 | ||
26 | <listitem> | 20 | <listitem> |
27 | <para>OSTree</para> | 21 | <para>OSTree-based upgrade system support.</para> |
28 | </listitem> | 22 | </listitem> |
29 | 23 | ||
30 | <listitem> | 24 | <listitem> |
31 | <para>In-band Managemnt</para> | 25 | <para>In-band management of uCPEs.</para> |
32 | </listitem> | 26 | </listitem> |
33 | 27 | ||
34 | <listitem> | 28 | <listitem> |
35 | <para>Updated documentation</para> | 29 | <para>Automation Framework and Test Harness.</para> |
36 | </listitem> | 30 | </listitem> |
31 | |||
37 | </itemizedlist> | 32 | </itemizedlist> |
38 | </section> | 33 | </section> |
39 | 34 | ||