In some embodiments, the template-switching system of this disclosure abridges the runtime change in configuration. When a user wants to make a change in any parameter, the user simply fills another profile template and creates a new data center template. Further, the next time the user wants to create a cluster, the user simply selects the new data center template the user created earlier. There is no manual changing of source code or even a need to inform a source code development team.

In some embodiments, predefined and pre-created templates are based off of the existing templates created for the first use of the cluster. Once another template is created in the reconfiguration process, this template is stored for possible future use. Making selection of reconfiguration templates efficient. Whenever a cluster of multiple servers is reconfigured the reconfiguration is performed by selecting a similar template to the preconfigured template currently usable, taking user inputs, changing parameters from configuration profile references in selected template, creating a new template based on the user's changes, and storing the new template for future use. The new template is then usable to create a new inventory file and reconfigure the cluster during runtime using the newly created inventory file.

In some embodiments, real-time reconfiguration of parameters use parallel instances of processes. Thus, when parameters need to be updated in three reference profiles, then parallel instances will be initiated to update the values parallel and create a final template which provides reconfiguration in real-time (e.g., a faster response, instead of waiting for each reference profile to be updated one by one).