Fix release schedule headers

[docs.git] / docs / getting-started-guide / concepts_and_tools.rst

diff --git a/docs/getting-started-guide/concepts_and_tools.rst b/docs/getting-started-guide/concepts_and_tools.rst
index f0db2cd4f2cb79be19a9b8fea18c20fd6262eebe..e5ccc15e78c9dbd84fa146b260a0c7fa33a1313b 100644 (file)
--- a/docs/getting-started-guide/concepts_and_tools.rst
+++ b/docs/getting-started-guide/concepts_and_tools.rst
@@ -20,47 +20,10 @@ below.
 * **Apache Karaf** provides a lightweight runtime to install the Karaf features
   you want to implement and is included in the OpenDaylight platform software.
   By default, OpenDaylight has no pre-installed features.
-* After installing OpenDaylight, you install your selected features using the
-  Karaf console to expand networking capabilities. In the Karaf feature list
-  below are the ones you’re most likely to use when creating your network
-  environment.
 
-  As a short example of installing a Karaf feature, OpenDaylight
-  offers Application Layer Traffic Optimization (ALTO). The Karaf feature to
-  install ALTO is odl-alto-all. On the Karaf console, the command to install it
-  is:
-
-  feature:install odl-alto-all
-
-* **DLUX** is a web-based interface that OpenDaylight provides for you to manage
-  your network. Its Karaf feature installation name is “odl-dlux-core”.
-
-  a. DLUX draws information from OpenDaylight’s topology and host databases to
-     display the following information:
-
-     i. The network
-     #. Flow statistics
-     #. Host locations
-
-  #. To enable the DLUX UI after installing OpenDaylight, run:
-
-     feature:install odl-dlux-core
-
-     on the Karaf console.
-
-* **Network embedded Experience (NeXt)** is a developer toolkit that provides
-  tools to draw network-centric topology UI elements that offer visualizations
-  of the following:
-
-  a. Large complex network topologies
-  #. Aggregated network nodes
-  #. Traffic/path/tunnel/group visualizations
-  #. Different layout algorithms
-  #. Map overlays
-  #. Preset user-friendly interactions
-
-  NeXt can work with DLUX to build OpenDaylight applications. Check out the
-  NeXt_demo_ for more information on the interface.
+  Features and feature repositories can be managed in the Karaf configuration
+  file  ``etc/org.apache.karaf.features.cfg`` using the ``featuresRepositories``
+  and ``featuresBoot`` variables.
 
 * Model-Driven Service Abstraction Layer (MD-SAL) is the OpenDaylight framework
   that allows developers to create new Karaf features in the form of services
@@ -69,16 +32,14 @@ below.
 
   a. A shared datastore that maintains the following tree-based structures:
 
-    i. The Config Datastore, which maintains a representation of the desired
-       network state.
-    #. The Operational Datastore, which is a representation of the actual
-       network state based on data from the managed network elements.
+     i. The Config Datastore, which maintains a representation of the desired
+        network state.
+     #. The Operational Datastore, which is a representation of the actual
+        network state based on data from the managed network elements.
 
   b. A message bus that provides a way for the various services and protocol
      drivers to notify and communicate with one another.
 
-* If you’re interacting with OpenDaylight through DLUX or the REST APIs while
-  using the the OpenDaylight interfaces, the microservices architecture allows
+* If you’re interacting with OpenDaylight through the REST APIs while
+  using the OpenDaylight interfaces, the microservices architecture allows
   you to select available services, protocols, and REST APIs.
-
-.. _NeXt_demo: https://www.youtube.com/watch?v=gBsUDu8aucs