Harikrishna Patnala created CLOUDSTACK-10431:
------------------------------------------------

             Summary: Mapping existing configuration parameters to the APIs
                 Key: CLOUDSTACK-10431
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10431
             Project: CloudStack
          Issue Type: Improvement
          Components: API, Management Server
            Reporter: Harikrishna Patnala


Hello students,

The following improvement will be a good addition to CloudStack and helps you 
learning a good product on a broad view.

Background:

Cloudstack has global settings in which there are around 672 configuration 
parameters. Using these parameters one can adjust the values according to the 
need of the environment. For example "allow.duplicate.networkname" default 
value of this parameter is true, which means networks can be created with same 
name in an account. If the value is set to false then duplicate network names 
are not allowed. 


Problem statement:

When admin wants to change the API behaviour or during debugging an issue, 
admin has to search for the corresponding configuration parameter. The only way 
currently everyone is using is by using string search or looking into 
corresponding documentation. Searching over 672 configuration parameters which 
is a huge list is not straight forward or may lead to missing few parameters.

 

Solution:

To address this problem I would like to propose the solution which maps the 
configurations parameters to the corresponding APIs. One can know what are the 
configuration parameters involved for a specific API. For example 
"createNetwork" API will be mapped to "allow.duplicate.networkname". When admin 
wants to see what are the configuration parameters used for "createNetwork" API 
, this mapping will help. In the final result we will have a table with APIs in 
one column and configuration parameters in another column.

Skills Required:
 * Java
 * Python

More details at https://github.com/apache/cloudstack/issues/4825

 Good luck.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to