ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13450) Bootstrap Cluster via different SSH Port Number
Date Tue, 20 Oct 2015 23:32:28 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965976#comment-14965976
] 

Hadoop QA commented on AMBARI-13450:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12767586/diff_patch2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server ambari-web.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4016//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4016//console

This message is automatically generated.

> Bootstrap Cluster via different SSH Port Number
> -----------------------------------------------
>
>                 Key: AMBARI-13450
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13450
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Selim Ozcan
>              Labels: features, patch
>         Attachments: BootStrap_via_different_SSH_port_number1.patch, diff_patch.patch,
diff_patch2.patch
>
>
> For the time being, bootstrapping cluster is done via default port number 22 for SSH
and SCP protocols without an option to specify the port number. 
> There was a need to bootstrap cluster via different port number at the laboratory which
I work at but Apache Ambari didn't have that option so we add that functionality. It still
uses the default port number 22 unless you change it at Installer Wizard Step 2. 
> A Textfieldview (default written value '22' SSH Port number ) added to installer wizard
step 2, same as specifying ssh user field which is default to 'root' user, to take the SSH
port input from user. After that, Port number is transferred to bootstrapping functions along
with sshUser value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message