Alex Huang created CLOUDSTACK-6208:
--------------------------------------
Summary: Enhance ConfigKey to include per management server
configurations
Key: CLOUDSTACK-6208
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6208
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.3.0
Reporter: Alex Huang
There are a number of parameters in the global config parameters that should
not be in a database table. Most of them have to do with management server
configurations. For example, workers=500. By having this in the database, it
forces all nodes of the management server cluster to use 500 worker threads.
However, what if the management server nodes are not homogeneous. Someone
should go through the global parameters and identify the ones that should be
per management server and move those into a properties file.
The new configuration mechanism already presents a ConfigDepot which can high
this implementation. It already has a scope for management server but the
implementation to read it from a properties file is missing. The work to
identify the parameters that should be per management server also needs to be
done.
See
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Configuration
--
This message was sent by Atlassian JIRA
(v6.2#6252)
