[
https://issues.apache.org/jira/browse/AMBARI-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747595#comment-13747595
]
Antonenko Alexander commented on AMBARI-2991:
---------------------------------------------
+1 for the patch
> NameNode HA Wizard: Prompt for Nameservice ID in Get Started page
> -----------------------------------------------------------------
>
> Key: AMBARI-2991
> URL: https://issues.apache.org/jira/browse/AMBARI-2991
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.4.1
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 1.4.1
>
> Attachments: AMBARI-2991.patch
>
>
> Create a text field with the label "Nameservice ID".
> The tooltip for this field should be "This will be the ID for the NameNode HA
> cluster. For example, if you set Nameservice ID to *mycluster*, the logical
> URI for HDFS will be *hdfs://mycluster*."
> We'll do a round of text clean up later. Let's get this in first so that we
> can integrate end to end with this change.
> So far, we have been hardcoding "mycluster". Based on the value of this, we
> should set the affected property keys and values appropriately when we
> reconfigure HDFS in the Deploy step.
> Let's make the validation for the Nameservice ID to be the same rule as the
> hostname (not FQDN, but the first component of it). This should be flexible
> enough and also avoids potential problems (doesn't seem like we should allow
> dots as the Nameservice ID is used as the name of keys whose components are
> dot-delimited, like dfs.namenode.http-address.mycluster.nn1)
> {noformat}
> ^([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])$
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
