[jira] [Resolved] (CLOUDSTACK-374) When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0)

["Rohit Yadav (JIRA)" <ji...@apache.org>]

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

Rohit Yadav resolved CLOUDSTACK-374.
------------------------------------

    Resolution: Fixed
      Assignee: Rohit Yadav

Fixed in master:
commit 947d8cc6de6b69394457fd6f07d3bba82e14fd9f
Author: Rohit Yadav <bh...@apache.org>
Date:   Mon Oct 22 16:46:57 2012 +0530
                
> When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-374
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-374
>             Project: CloudStack
>          Issue Type: Improvement
>          Components: Install and Setup
>    Affects Versions: 4.0.0
>         Environment: centos 6.3 x64 management server with 3 active network interfaces
>            Reporter: kelcey damage
>            Assignee: Rohit Yadav
>             Fix For: 4.1.0
>
>
> When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0) for:
> "Detected local IP address as 192.168.1.187, will use as cluster management server node IP[ OK ]”
> Would it be possible to provide a new command line argument for establishing host? Such as: –host {ipaddr}
> This would make complex deployment architectures easier to implement. It is also quite common to have multiple nics on the management server.

--
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