Bug 1470734 - ODL clustering uses bash script + default module/shard configuration
Summary: ODL clustering uses bash script + default module/shard configuration
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-opendaylight
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: Tim Rozet
QA Contact: Itzik Brown
Depends On:
Blocks: 1414313
TreeView+ depends on / blocked
Reported: 2017-07-13 14:25 UTC by Tim Rozet
Modified: 2018-10-18 07:20 UTC (History)
5 users (show)

Fixed In Version: puppet-opendaylight-4.0.1-0.20170717191408.07a0b03.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:40:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenDaylight gerrit 59493 0 None None None 2017-07-13 14:27:45 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Tim Rozet 2017-07-13 14:25:21 UTC
Description of problem:
Currently in puppet-odl we are using an exec for a bash script to configure clustering which generates the the clustering config files for ODL (akka.conf, modules.conf, module-shards.conf).  We need to migrate away from a bash script and in doing so also provide a proper default configuration.  The bash script creates a default configuration with several modules/shards, including a dummy example module which should not be in production.

The new method will use erb templates to create the files, and by default place the entire datastore under just the default module.  Meaning the entire datastore will be led by a single ODL instance.  Optionally a user can use a new parameter to puppet-odl 'ha_db_modules' in order to break up the datastore into multiple modules/shards.

Comment 3 Itzik Brown 2017-09-19 07:14:04 UTC
Checked with:

Comment 6 errata-xmlrpc 2017-12-13 21:40:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.