summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml14
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml33
-rw-r--r--doc/book-enea-nfv-access-getting-started/doc/introduction.xml8
3 files changed, 40 insertions, 15 deletions
diff --git a/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml b/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
index 8851aed..e5f81fc 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/definitions_and_acronyms.xml
@@ -78,6 +78,13 @@
78 </row> 78 </row>
79 79
80 <row> 80 <row>
81 <entry>FCAPS</entry>
82
83 <entry>Fault-management, Configuration, Accounting, Performance
84 and Security.</entry>
85 </row>
86
87 <row>
81 <entry>NETCONF</entry> 88 <entry>NETCONF</entry>
82 89
83 <entry>Network Configuration Protocol.</entry> 90 <entry>Network Configuration Protocol.</entry>
@@ -116,10 +123,9 @@
116 <row> 123 <row>
117 <entry>PCI Passthrough</entry> 124 <entry>PCI Passthrough</entry>
118 125
119 <entry>PCI Passthrough allows for use of a physical PCI device, 126 <entry>PCI Passthrough allows for use of a physical PCI device,
120 e.g. a network card inside a VM. 127 e.g. a network card inside a VM. If you "PCI passthrough" a
121 If you "PCI passthrough" a device, the device is not available to 128 device, the device is not available to the host anymore.</entry>
122 the host anymore.</entry>
123 </row> 129 </row>
124 130
125 <row> 131 <row>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index 85ee5a3..818bd52 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -117,8 +117,7 @@ OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7-LTS, mixed mode, sharing)</program
117 117
118 <programlisting>export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which javac))))) 118 <programlisting>export JAVA_HOME=$(dirname $(dirname $(readlink $(readlink $(which javac)))))
119export PATH=$PATH:$JAVA_HOME/bin 119export PATH=$PATH:$JAVA_HOME/bin
120export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar 120export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar</programlisting>
121</programlisting>
122 </listitem> 121 </listitem>
123 </orderedlist> 122 </orderedlist>
124 123
@@ -137,6 +136,26 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
137 </listitem> 136 </listitem>
138 137
139 <listitem> 138 <listitem>
139 <para>If you plan to use the PostgreSQL server bundled with the
140 uCPE Manager, verify that there is no existing installation of the
141 Postgres database. Execute the following command to check if you
142 have a currently running PostgreSQL database server:</para>
143
144 <programlisting>ps -ef | grep post</programlisting>
145
146 <para>To remove a currently installed PostgreSQL server (including the
147 existing postgres user), run the following commands:</para>
148
149 <programlisting>yum remove postgres\*
150rm -f /var/lib/pgsql
151rm -f /etc/postgres-reg.ini
152userdel postgres</programlisting>
153
154 <note><para>This step is not necessary if the uCPE Manager
155 will be using an external database (like MariaDB).</para></note>
156 </listitem>
157
158 <listitem>
140 <para>Choose the target installation folder, e.g. 159 <para>Choose the target installation folder, e.g.
141 <literal>/opt/ems</literal>. Everything will be installed under a 160 <literal>/opt/ems</literal>. Everything will be installed under a
142 folder called <literal>ucpemanager</literal> within the target 161 folder called <literal>ucpemanager</literal> within the target
@@ -607,13 +626,13 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
607 626
608 <para>Configuring a physical interface in DPDK mode will require a 627 <para>Configuring a physical interface in DPDK mode will require a
609 DPDK-based application (e.g. OVS-DPDK) in order to access and use the 628 DPDK-based application (e.g. OVS-DPDK) in order to access and use the
610 interface. An interface set as the DPDK can be attached to an OVS-DPDK 629 interface. An interface set as DPDK can be attached to an OVS-DPDK
611 bridge.</para> 630 bridge.</para>
612 631
613 <note> 632 <note>
614 <para>Make sure the <literal>Enable DPDK</literal> checkbox is 633 <para>Make sure the <literal>Enable DPDK</literal> checkbox is
615 selected in <literal>Device -&gt; Configuration -&gt; 634 selected in <literal>Device -&gt; Configuration -&gt;
616 DPDK</literal>, otherwise no interface can be assigned to the 635 DPDK</literal>, otherwise no interface can be assigned as
617 DPDK.</para> 636 DPDK.</para>
618 </note> 637 </note>
619 638
@@ -635,8 +654,8 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
635 654
636 <listitem> 655 <listitem>
637 <para>Dpdk-type: the kernel module that allows user space access 656 <para>Dpdk-type: the kernel module that allows user space access
638 to the physical interface. The <literal>vfio-pci</literal> driver 657 to the physical interface. Either the <literal>vfio-pci</literal>
639 is used.</para> 658 or the <literal>igb_uio</literal> driver can be used.</para>
640 </listitem> 659 </listitem>
641 </itemizedlist> 660 </itemizedlist>
642 </section> 661 </section>
@@ -2013,4 +2032,4 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
2013 </orderedlist> 2032 </orderedlist>
2014 </section> 2033 </section>
2015 </section> 2034 </section>
2016</chapter> \ No newline at end of file 2035</chapter>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
index c6a4f04..96c3172 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -64,9 +64,9 @@
64 64
65 <para>Enea uCPE Manager is a control center application providing a full 65 <para>Enea uCPE Manager is a control center application providing a full
66 FCAPS and VNF management experience through a GUI and REST API. It can be 66 FCAPS and VNF management experience through a GUI and REST API. It can be
67 deployed on a host or a virtual machine. CentOS and Windows are supported 67 deployed on a host or a virtual machine running 64-bit CentOS on an x86
68 host platforms by default. The uCPE Manager uses a southbound EdgeLink 68 platform. The uCPE Manager uses a southbound EdgeLink NETCONF protocol to
69 NETCONF protocol to connect and manage uCPE devices.</para> 69 connect and manage uCPE devices.</para>
70 70
71 <para>Enea uCPE Manager provides the following key features:</para> 71 <para>Enea uCPE Manager provides the following key features:</para>
72 72
@@ -92,4 +92,4 @@
92 </listitem> 92 </listitem>
93 </itemizedlist> 93 </itemizedlist>
94 </section> 94 </section>
95</chapter> \ No newline at end of file 95</chapter>