eliezio / opendaylight

Blue-ONAP OpenDaylight

1   Overview

This project generates a docker image of the OpenDaylight Controller, and publishes it at Docker Hub.

This distribution provides the following enhancements:

• The fabric8-karaf-checks feature is pre-installed and exposes the /readiness-check and /health-check endpoints. See Fabric8 Karaf Health Checks for more information;
• You can add more feature repositories and features by defining two environment variables:

Environment Variable	Purpose
KARAF_FEATURES_REPOSITORIES	Configure additional feature repositories.
KARAF_FEATURES_BOOT	Use to specify additional features to be installed and activated at start-up.

2   Usage Examples

2.1   Run OpenDaylight ready to connect to Netopeer2-based servers

2.1.1   Step 1: Launches OpenDaylight

Two additional features are required: odl-restconf-all and odl-netconf-connector-all.

$ docker run -d -p 8181:8181 \
  -e KARAF_FEATURES_BOOT=odl-restconf-all,odl-netconf-connector-all \
  quay.io/blue-onap/opendaylight:v0.12.0-2

Or using Docker Compose:

version: '3'

services:
  opendaylight:
    image: quay.io/blue-onap/opendaylight:v0.12.0-2
    container_name: opendaylight
    ports:
      - "8101:8101"
      - "8181:8181"
      - "6666:6666"
    environment:
      - KARAF_FEATURES_BOOT=odl-restconf-all,odl-netconf-connector-all
    volumes:
      - ./config:/config

2.1.2   Step 2: Configure TLS to connect to Netopeer2

You need to provide the following PEM files under ./config/tls:

File	Contents
client_key.pem	The client's private key in plain (not protected by a passphrase).
client_cert.pem	The corresponding client X.509v3 certificate.
ca.pem	The Certificate Authority (CA) certificate.

You can apply this configuration at runtime by running:

$ docker exec <CONTAINER NAME or ID> /opt/bin/configure-tls.sh