[jira] [Updated] (HDDS-1596) Create service endpoint to download configuration from SCM

["Ethan Rose (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose updated HDDS-1596:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> Create service endpoint to download configuration from SCM
> ----------------------------------------------------------
>
>                 Key: HDDS-1596
>                 URL: https://issues.apache.org/jira/browse/HDDS-1596
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Marton Elek
>            Assignee: Marton Elek
>            Priority: Major
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> As written in the design doc (see the parent issue) it was proposed to download the configuration from the scm by the other services.
> I propose to create a separated endpoint to provide the ozone configuration. /conf can't be used as it contains *all* the configuration and we need only the modified configuration.
> The easiest way to implement this feature is:
>  * Create a simple rest endpoint which publishes all the configuration
>  * Download the configurations to $HADOOP_CONF_DIR/ozone-global.xml during the service startup.
>  * Add ozone-global.xml as an additional config source (before ozone-site.xml but after ozone-default.xml)
>  * The download can be optional
> With this approach we keep the support of the existing manual configuration (ozone-site.xml has higher priority) but we can download the configuration to a separated file during the startup, which will be loaded.
> There is no magic: the configuration file is saved and it's easy to debug what's going on as the OzoneConfiguration is loaded from the $HADOOP_CONF_DIR as before.
> Possible follow-up steps:
>  * Migrate all the other services (recon, s3g) to the new approach. (possible newbie jiras)
>  * Improve the CLI to define the SCM address. (As of now we use ozone.scm.names)
>  * Create a service/hostname registration mechanism and autofill some of the configuration based on the topology information.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org