-------------------------
DLUX provides a number of different Karaf features, which you can enable
-and disable separately. In Beryllum they are: . odl-dlux-core .
-odl-dlux-node . odl-dlux-yangui . odl-dlux-yangvisualizer
+and disable separately. They are:
+
+ - odl-dlux-core
+ - odl-dluxapps-nodes
+ - odl-dluxapps-topology
+ - odl-dluxapps-yangui
+ - odl-dluxapps-yangvisualizer
+ - odl-dluxapps-yangman
Logging In
----------
To log in to DLUX, after installing the application:
1. Open a browser and enter the login URL
- `http://<your-karaf-ip>:8181/index.html <http://<your-karaf-ip>:8181/index.html>`__
+ http://<your-karaf-ip>:8181/index.html
in your browser (Chrome is recommended).
2. Login to the application with your username and password credentials.
- **Note**
+.. note::
OpenDaylight’s default credentials are *admin* for both the username
and password.
After you login to DLUX, if you enable only odl-dlux-core feature, you
will see only topology application available in the left pane.
- **Note**
+.. note::
To make sure topology displays all the details, enable the
odl-l2switch-switch feature in Karaf.
DLUX has other applications such as node, yang UI and those apps won’t
-show up, until you enable their features odl-dlux-node and
-odl-dlux-yangui respectively in the Karaf distribution.
+show up, until you enable their features odl-dluxapps-nodes and
+odl-dluxapps-yangui respectively in the Karaf distribution.
.. figure:: ./images/dlux-login.png
:alt: DLUX Modules
DLUX Modules
- **Note**
+.. note::
If you install your application in dlux, they will also show up on
the left hand navigation after browser page refresh.
The Topology tab displays a graphical representation of network topology
created.
- **Note**
+.. note::
DLUX does not allow for editing or adding topology information. The
topology is generated and edited in other modules, e.g., the
2. The top part displays a tree of APIs, subAPIs, and buttons to call
possible functions (GET, POST, PUT, and DELETE).
- **Note**
+ .. note::
-.. note:: every subAPI can call every function. For example, subAPIs in
+ every subAPI can call every function. For example, subAPIs in
the *operational* store have GET functionality only.
Inputs can be filled from OpenDaylight when existing data from