Bug 1377179 - [RFE] Improve Configuration management
Summary: [RFE] Improve Configuration management
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 05:59 UTC by Aravinda VK
Modified: 2018-03-13 08:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-13 08:06:47 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Aravinda VK 2016-09-19 05:59:39 UTC
Description of problem:
List of issues with the existing configuration management in Geo-replication.

- On every Glusterd restart, it generates new gsyncd_template.conf. This should be avoided by generating template conf file only once during installation/upgrade
- Session configuration file is copy of template conf file, This is not required. Only modified config items should be saved in session config.
- Config set should set only if previous value is different than current value. This causes Geo-rep session restarts even though no changes in config.
- All config change causes session restart, We should have separate groups of configs - restart_configs, reload_configs
- No way to get list of default configurations, unless we look in the code.
- Clear distinction for info configs and modifiable config options is not available.
- Some config default values are added in code and for some deafault values added in template conf. Every default conf should be moved to template/default config.

Comment 1 Aravinda VK 2018-03-13 08:06:47 UTC
This is addressed with the Github issue https://github.com/gluster/glusterfs/issues/73


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