[MCOL-594] support external management / push of configuration files Created: 2017-02-27  Updated: 2023-10-26  Resolved: 2020-04-02

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.0.7
Fix Version/s: N/A

Type: New Feature Priority: Major
Reporter: David Thompson (Inactive) Assignee: Todd Stoffel (Inactive)
Resolution: Won't Do Votes: 0
Labels: None

Sprint: 2017-16, 2017-17, 2017-18

 Description   

To better support container systems, we should allow optional disabling of the pm1 node automatically synchronizing configuration files to the other nodes. This would allow an external orchestration engine to perform this management instead. This should definitely not be done by default but it should be easy to disable via a config setting.

Note that distribution of dbrm metadata is not in scope, this is purely focussed on enabling an external system to setup and scale out nodes.

 Comments   
Comment by David Hill (Inactive) [ 2017-08-31 ]

code changes planned:

1. postConfigure - new command line argument called -nc (for non-distribute config feature)
2. mcsadmin
a. getsysteminfo will show if the feature is enabled/disabled
b. add new commands - enableDistributeConfig and disableDistributeConfig
3. Columnstore.xml - new setting Installation / DistributeConfigFiles
4. ProcMon/ProcMgr/oam api - check config setting DistributeConfigFiles, skip config file distrubute when
enabled

coding done in MCOL-594 engine repo, testing next

Comment by David Hill (Inactive) [ 2017-09-01 ]

question..

does this also apply during install time? At this time for s distributed install, the packages and config files are pushed.
If they enable this new feature NOT to distribute the config files, does this also apply during the initial install time? The system will not start up without updated config files.
It is currently setup that procmon/procmgr will not distribute the config files around, just just now thought out the initial install.

Comment by David Thompson (Inactive) [ 2017-09-01 ]

i think it would be ok at install time.
the idea would to be allow someone to use another devops tool like chef, etc to manage ColumnStore.xml and use that to push to the nodes
so if we did that at install it'd be ok because get a working one and then you can use that as your baseline.
Just that now you use your devops tool to manage the master and updates to cs.xml rather than having to maintain this on pm1.

Comment by David Hill (Inactive) [ 2017-09-05 ]

Im not sure how the system will function when this feature is enabled... There are a number of times when the Columnstore.xml is distributed automatically by ProcMgr. So its not just at system startup time, but also distributed when a module goes offline, a module is added or removed, switch Parent OAM module. If we total disable the distributing of the config files, excluding install time, this will break a lot of the current functionality.

So Im just not sure how this is suppose to work..

Comment by Todd Stoffel (Inactive) [ 2020-04-02 ]

This will be resolved with the removal of OAM and the new API / MaxScale project.

Generated at Thu Feb 08 02:22:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.