[jira] [Commented] (ATLAS-72) Use atlas.rest.address on server
[ https://issues.apache.org/jira/browse/ATLAS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628062#comment-14628062 ] Jonathan Maron commented on ATLAS-72: - I disagree with this approach since it is simply confusing from a management perspective (i.e. a user on Ambari). What would it mean to set enableTLS to true, while specifying a http URI for this setting? I imagine you'll say that we now eliminate the enableTLS flag, but I would venture to say that, from a management interface, the ability to enable or disable SSL with a switch is preferable and much clearer. I imagine we could play some games with configuration property dependencies (setting SSL to true on an interface would automatically change the rest address' transport scheme) but I believe that's somewhat confusing as well and runs contrary to the management experience with other services. > Use atlas.rest.address on server > > > Key: ATLAS-72 > URL: https://issues.apache.org/jira/browse/ATLAS-72 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S > > On server, there are separate configs for should enable ssl, and port. > Instead, it can use the client side config atlas.rest.address to derive ssl, > port and host to bind to -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-72) Use atlas.rest.address on server
[ https://issues.apache.org/jira/browse/ATLAS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629737#comment-14629737 ] Erik Bergenholtz commented on ATLAS-72: --- There are [at least] 3 factors that should be considered: 1. User Experience 2. Consistency with other components to eliminate/reduce confusion (related to #1) 3. Manageability > Use atlas.rest.address on server > > > Key: ATLAS-72 > URL: https://issues.apache.org/jira/browse/ATLAS-72 > Project: Atlas > Issue Type: Improvement >Reporter: Shwetha G S > > On server, there are separate configs for should enable ssl, and port. > Instead, it can use the client side config atlas.rest.address to derive ssl, > port and host to bind to -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-72) Use atlas.rest.address on server
[
https://issues.apache.org/jira/browse/ATLAS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633439#comment-14633439
]
Shwetha G S commented on ATLAS-72:
--
{quote}
from a management interface, the ability to enable or disable SSL with a switch
is preferable and much clearer
{quote}
Ambari is just one way of deploying atlas. Atlas can be deployed directly
using atlas_start.py. In this case, user has to hand-code the configs and
lesser configs the better, less prone to error.
On ambari UI, you can always expose different controls to enable ssl, set host
and port. But all of them can map to single config in the backend
> Use atlas.rest.address on server
>
>
> Key: ATLAS-72
> URL: https://issues.apache.org/jira/browse/ATLAS-72
> Project: Atlas
> Issue Type: Improvement
>Reporter: Shwetha G S
>
> On server, there are separate configs for should enable ssl, and port.
> Instead, it can use the client side config atlas.rest.address to derive ssl,
> port and host to bind to
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
