* On the control host, `Download
the latest OpenDaylight release <ODL_Downloads_>`_ (at the time of writing,
- this is Beryllium-SR2)
+ this is Boron)
* Uncompress it as root, and start OpenDaylight (you can start OpenDaylight
by running karaf directly, but exiting from the shell will shut it down):
.. code-block:: bash
- tar xvfz distribution-karaf-0.4.2-Beryllium-SR2.tar.gz
- cd distribution-karaf-0.4.2-Beryllium-SR2
+ tar xvfz distribution-karaf-0.5.0-Boron.tar.gz
+ cd distribution-karaf-0.5.0-Boron
./bin/start # Start OpenDaylight as a server process
* Connect to the Karaf shell, and install the odl-ovsdb-openstack bundle,
.. image:: images/dlux-with-switches.png
-* If something has gone wrong, check <code>data/log/karaf.log</code> under
+* If something has gone wrong, check ``data/log/karaf.log`` under
the OpenDaylight distribution directory. If you do not see any interesting
log entries, set logging for OVSDB to TRACE level inside Karaf and try again:
for REST calls) is available. By default, swift-proxy-service listens on the
same port, and you may need to move it (to another port or another host), or
disable that service. I moved it to port 8081 by editing
-<code>/etc/swift/proxy-server.conf</code> and
-<code>/etc/cinder/cinder.conf</code>, modifying iptables appropriately, and
+``/etc/swift/proxy-server.conf`` and
+``/etc/cinder/cinder.conf``, modifying iptables appropriately, and
restarting swift-proxy-service and OpenDaylight.
* Configure Neutron to use OpenDaylight's ML2 driver:
}
If this does not work or gives an error, check Neutron's log file in
-<code>/var/log/neutron/server.log</code>. Error messages here should give
+``/var/log/neutron/server.log``. Error messages here should give
some clue as to what the problem is in the connection with OpenDaylight
* Create a net, subnet, router, connect ports, and start an instance using