aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/onap-user/connect.rst
diff options
context:
space:
mode:
authorAijana Schumann <aijana.schumann@highstreet-technologies.com>2020-02-11 15:44:17 +0100
committerAijana Schumann <aijana.schumann@highstreet-technologies.com>2020-02-11 15:47:12 +0100
commit06fb529a84d4e7d70b3aca68c33b2980049d5973 (patch)
tree843a61b2a980cfb486996c967b86da56863f27de /docs/guides/onap-user/connect.rst
parentf6f3b57be8e57ffc6790d139b0b7f168b8cc69e6 (diff)
Update documentation for odlux
Update help texts for all odlux apps to include new functionality Issue-ID: SDNC-1065 Signed-off-by: Aijana Schumann <aijana.schumann@highstreet-technologies.com> Change-Id: I35b60a950b758f3bc3c182a01646d6d746ed2240 Signed-off-by: Aijana Schumann <aijana.schumann@highstreet-technologies.com>
Diffstat (limited to 'docs/guides/onap-user/connect.rst')
-rw-r--r--docs/guides/onap-user/connect.rst46
1 files changed, 21 insertions, 25 deletions
diff --git a/docs/guides/onap-user/connect.rst b/docs/guides/onap-user/connect.rst
index 9678dd6ff..6da746953 100644
--- a/docs/guides/onap-user/connect.rst
+++ b/docs/guides/onap-user/connect.rst
@@ -7,39 +7,35 @@ Connect
The 'Connect' application on OpenDaylight provides up-to-date
connectivity information about the wireless devices in the network. It
-automatically displays new network elements and their connection status.
-Despite the network elements usually automatically mount themselves, an
-additional small window allows manually mounting devices/mediators. For
-better understanding alarms and status, a connection status log lists
-all the connection status changes of OpenDaylight mount points.
+automatically displays new Network Elements and their connection status.
+Usually, the Network Elements mount themselves. If necessary, they can
+be mounted manually by right-clicking on the element. For better
+understanding of alarms and status, a connection status log lists all
+the connection status changes of OpenDaylight mount points.
Views
-----
-The graphical user interfaces is divided in three sections.
+The graphical user interface is divided into two sections.
-Required Network Elements
-~~~~~~~~~~~~~~~~~~~~~~~~~
+Network Elements
+~~~~~~~~~~~~~~~~
-Required Network Elements are physical network functions, which are
-planned or expected in the network. This means the identifier, IP
-addresses and its required configuration is well-known and available in
-a planning database or in ONAP A&AI.
+Network Elements are physical network functions (PNFs). A table view
+shows all configured and connected NetConf Servers of the SDN-R cluster.
+This view also allows to manually configure/mount a device via the '+'
+button. The SDN controller will start connecting to the NetConf server.
-This view also offer to manually configure/mount the device with the '+'
-icon. The SDN controller will then start connecting the Netconf server.
+Network Elements can be marked as 'required'. If an element is required,
+it will stay available even if disconnected. If an element is not
+required, it will be deleted once disconnected.
-Unknown Network Elements
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-Most of the physical network function support an automatic registration
-procedure to the SDN controller. It may happen, that devices are
-connected to the SDN Controller but not available in planning data.
-
-It might be a normal occurrence for very cheap devices, where an entire
-planning process to too expensive. But is may also happen that the
-identifier used in planning process differ from the identifier currently
-configured in the device.
+By right-clicking on an element, an action menu opens. The menu allows
+to mount, unmount, view the details, edit and remove the element.
+Additionally, it links to several applications like
+`Fault <../pnfFault/README.md>`__ and
+`Configure <../pnfConfig/README.md>`__, which will be filtered to
+display information relevant to the selected element.
Connection Status Log
~~~~~~~~~~~~~~~~~~~~~