summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormrpa <miruna.paun@enea.com>2021-11-09 14:55:08 +0100
committerMiruna Paun <mrpa@enea.se>2021-11-09 15:46:32 +0100
commit58e910fadfef17c37d2f59c90dac678cf7be3ac5 (patch)
tree3abaffaa8f05bc8238509303898e24ff24192a02
parentd01178f02fb4532498b9a15ae9bd1d1a0a6ea6ee (diff)
downloadnfv-access-documentation-58e910fadfef17c37d2f59c90dac678cf7be3ac5.tar.gz
Added a new item to the modules enea Dir,feature_CPDX-3263
Added a new section Automated Deployment Reporting. Change-Id: I64f2437118526457b2925e397430594c21ee23c9 Signed-off-by: mrpa <miruna.paun@enea.com>
-rw-r--r--doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml113
1 files changed, 113 insertions, 0 deletions
diff --git a/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
index 6111f20..5cc879d 100644
--- a/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
+++ b/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
@@ -150,6 +150,12 @@
150 <para><literal>VNF_images</literal> - contains the VNF images that 150 <para><literal>VNF_images</literal> - contains the VNF images that
151 are used in test scenarios.</para> 151 are used in test scenarios.</para>
152 </listitem> 152 </listitem>
153
154 <listitem>
155 <para><literal>utils</literal> - contains configurable solutions for
156 different features. For example, the solution for automated
157 deployment reporting can be found under this directory.</para>
158 </listitem>
153 </itemizedlist> 159 </itemizedlist>
154 </section> 160 </section>
155 161
@@ -1587,4 +1593,111 @@ vnfi_name: "fortigateFWInstance"</programlisting>
1587 Management application are provided in the <literal>README</literal> file 1593 Management application are provided in the <literal>README</literal> file
1588 from scenario in use.</para> 1594 from scenario in use.</para>
1589 </section> 1595 </section>
1596
1597 <section id="auto_deploy_reporting">
1598 <title>Automated Deployment Reporting</title>
1599
1600 <para>The Deployment Reporting functionality will generate a CSV file
1601 containing information about all uCPE Devices deployed with Enea Edge and
1602 enrolled into the Enea Edge Management application.</para>
1603
1604 <para>The Python script for this solution is available in
1605 <filename>modules/enea/utils/reporting/generate_deployment_report.py</filename>.</para>
1606
1607 <para>The information about uCPE Devices that will be found in the CSV
1608 file is following:</para>
1609
1610 <itemizedlist>
1611 <listitem>
1612 <para>Device Name</para>
1613 </listitem>
1614
1615 <listitem>
1616 <para>Device ID</para>
1617 </listitem>
1618
1619 <listitem>
1620 <para>Enea Edge Runtime version</para>
1621 </listitem>
1622
1623 <listitem>
1624 <para>Number of CPU cores - If the device is disconnected, a warning
1625 message appears in this field.</para>
1626 </listitem>
1627
1628 <listitem>
1629 <para>Timestamp when the device was added in the Enea Edge Management
1630 application - If the device was never connected, a warning message
1631 appears in this file.</para>
1632 </listitem>
1633
1634 <listitem>
1635 <para>The Enea Edge Management application IP or FQDN.</para>
1636 </listitem>
1637 </itemizedlist>
1638
1639 <para>Prerequisities:</para>
1640
1641 <orderedlist>
1642 <listitem>
1643 <para>Modify the Enea Edge Management configuration file, see "4.2.1
1644 Configuration Files for the Enea Edge Management application" from
1645 "Enea® Edge Automation User Guide" for more details.<remark>Add Olink
1646 here</remark></para>
1647 </listitem>
1648
1649 <listitem>
1650 <para>For reporting devices connected to one Enea Edge Management
1651 application instance, update the
1652 <filename>modules/enea/config/Management/management01.json</filename>
1653 file.</para>
1654 </listitem>
1655
1656 <listitem>
1657 <para>For reporting devices connected to multiple Enea Edge Management
1658 application instances, a new JSON file will be created for
1659 each.</para>
1660
1661 <para>The JSON file must have the following structure:</para>
1662
1663 <programlisting>{
1664 "ucpe_usr":"&lt;Management Username&gt;",
1665 "ucpe_pass":"&lt;Management Password&gt;",
1666 "ucpe_host":"&lt;Management IP or FQDN&gt;"
1667}</programlisting>
1668
1669 <para>All JSON files should be saved in the same directory and the
1670 path to the directory will be a parameter of the script
1671 (<literal>-m/--managements_directory</literal>).</para>
1672 </listitem>
1673
1674 <listitem>
1675 <para>Run the Python script to generate the CSV reporting:</para>
1676
1677 <programlisting>&gt; python modules/enea/utils/reporting/generate_deployment_report.py --help
1678Usage: generate_deployment_report.py [OPTIONS]
1679
1680Options:
1681 -r, --report_directory TEXT The directory where the report will be
1682 saved. Default: the current directory
1683
1684 -f, --filename TEXT The name of the CSV report. Default:
1685 Devices.csv
1686
1687 -t, --timestamp Append the timestamp to the filename.
1688 Default: False
1689
1690 -m, --managements_directory TEXT
1691 The directory where the JSON config files
1692 for the Edge Management applications are
1693 saved. Default:
1694 ./modules/enea/config/Management/
1695
1696 -v, --version Display the version of the Edge Automation
1697 and exit
1698
1699 --help Show this message and exit.</programlisting>
1700 </listitem>
1701 </orderedlist>
1702 </section>
1590</chapter> \ No newline at end of file 1703</chapter> \ No newline at end of file