Bug 1470734

Summary: ODL clustering uses bash script + default module/shard configuration
Product: Red Hat OpenStack Reporter: Tim Rozet <trozet>
Component: puppet-opendaylightAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: jjoyce, jschluet, nyechiel, slinaber, tvignaud
Target Milestone: Upstream M3Keywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-opendaylight-4.0.1-0.20170717191408.07a0b03.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-12-13 21:40:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1414313    

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:
puppet-opendaylight-4.1.0-0.20170825114651.3768d5e.el7ost.noarch
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.

https://access.redhat.com/errata/RHEA-2017:3462