Change has been made to the dockerfile inside sdnc/oam to enable ODL Features: 

• odl-netconf-connector-all

• odl-netconf-clustered-topology

Change can be reviewed here:

  https://gerrit.onap.org/r/#/c/82913/

Here's an item to add to your list:

Ssince the netconf connector is very "burst-like", consuming large amounts of Heap and then going quiet, it is prone to creating disruptive Java Garbage Collection pauses when connecting to devices with large amounts of yang.

The simple/standard solution is to tell Java to use G1GC with short pauses rather than the defaults.  This can be enabled in the ./bin/setenv script, which is a good place for setting any Java options.

Here is a snippet of the Fluorine-SR2 setenv:

...

#

1. general settings which should be applied for all scripts go here; please keep

2. in mind that it is possible that scripts might be executed more than once, e.g.

3. in example of the start script where the start script is executed first and the

4. karaf script afterwards.
   #

#

1. The following section shows the possible configuration options for the default

2. karaf scripts
   #

3. export JAVA_HOME # Location of Java installation

4. export JAVA_MIN_MEM # Minimum memory for the JVM

5. export JAVA_MAX_MEM # Maximum memory for the JVM

6. export JAVA_PERM_MEM # Minimum perm memory for the JVM

7. export JAVA_MAX_PERM_MEM # Maximum perm memory for the JVM

8. export EXTRA_JAVA_OPTS # Additional JVM options

...

Thus inserting the following options will enable G1GC garbage collection:

export EXTRA_JAVA_OPTS="-XX:+UseG1GC -XX:MaxGCPauseMillis=200"

Since these options are only made effective at startup, a good choice would be to edit the setenv file (or replace it) during the dockerfile steps.

Increasing JAVA_MAX_MEM is optional but recommended; this is subjective based on how much netconf will be used in a user's own installation.  A general guideline is to start with 8GB and increase based on your monitored Java Heap usage trends.

-Jeff Hartley

Lumina Networks