You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/06/12 20:47:00 UTC

[jira] [Assigned] (AMBARI-13450) Bootstrap Cluster via different SSH Port Number

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

Yusaku Sako reassigned AMBARI-13450:
------------------------------------

    Assignee: Selim Ozcan

> 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
>            Assignee: Selim Ozcan
>              Labels: features, patch
>             Fix For: 2.3.0
>
>         Attachments: 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.4.14#64029)