[CONTROLLER-1750] FileModuleShardConfigProvider should not use hard-coded paths Created: 15/Aug/17  Updated: 25/Jul/23  Resolved: 30/Aug/17

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Juraj Veverka Assignee: Jakub Toth
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 8994

 Description   

tech.pantheon.lodl.controller.initializers.controller.sal.distributed.datastore.DistributedDataStoreFactoryLodlImpl - in the createInstance method, the org.opendaylight.controller.cluster.datastore.config.ConfigurationImpl has hard-coded file names for module-shards.conf and modules.conf and also relative paths to those files is hard-coded in class org.opendaylight.controller.cluster.datastore.config.FileModuleShardConfigProvider

instead it would be better if path to those configuration files is provided in blueprint of org.opendaylight.controller:sal-distributed-datastore bundle as init parameter of DistributedDataStoreFactoryLodlImpl and passed down into FileModuleShardConfigProvider.



 Comments   
Comment by Jakub Toth [ 22/Aug/17 ]

https://git.opendaylight.org/gerrit/#/c/62141/

Generated at Wed Feb 07 19:56:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.