[
https://issues.apache.org/jira/browse/HDDS-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862240#comment-16862240
]
Eric Yang commented on HDDS-1567:
---------------------------------
{quote}Do you suggest to create a patch or just collect settings in the comment
of the jira?{quote}
I prefer to create a patch to implement the defined settings. This ensures
that we capture all suggested settings. If there is too much difference in
opinions, then I am open to complete the discussion, and implement the spec in
a separate issue.
{quote}Do you suggest to create more documentation page?{quote}
If the spec requires much code change, and having a separate documentation task
may help to prioritize work.
{quote}Do you suggest to add additional TAGs in to the ozone-default.xml for
each of these use cases?{quote}
I am not sure I understand TAGs usage in ozone-default.xml completely. You may
need to explain further, if ozone-default.xml is more than default values for
configuration. My current impression is no, we don't need to add more tags.
For example, exposing /opt/hadoop/bin/ozone path in docker compose and
Kubernetes yaml file, makes Ozone docker image layout not flexible to change.
The binary can only be placed in /opt/hadoop. It maybe useful to have
environment variable that define the role of the image. e.g ROLE=om or
ROLE=scm. The environment variable is representing the alias to launch Ozone
commands in start up script, and we have more freedom to change the inner
layout of the docker image between releases.
{quote}What is the "definition of done" of this jira?{quote}
When we agree on the essential set of environment variable to operate Ozone
without leaking internal implementation of the docker image. We can be
consider this as done. If it is low hanging fruit changes, then having a patch
to would preferred.
I am most interested in:
# having a variable that allow toggle between om, scm or datanode.
# define HA quorum.
# Kerberos settings, pass as environment variables or bind mount krb5.conf +
jaas.conf.
# User database type: pam, ldap, sssd
> Define a set of environment variables to configure Ozone docker image
> ---------------------------------------------------------------------
>
> Key: HDDS-1567
> URL: https://issues.apache.org/jira/browse/HDDS-1567
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Eric Yang
> Priority: Major
>
> For developer that tries to setup docker image by end for testing purpose, it
> would be nice to predefine a set of environment variables that can be passed
> to Ozone docker image to configure the minimum set of configuration to start
> Ozone containers. There is a python script that converts environment
> variables to config, but documentation does not show what setting can be
> passed to configure the system. This task would be a good starting point to
> document the available configuration knobs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
