[
https://issues.apache.org/jira/browse/CLOUDSTACK-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503605#comment-13503605
]
Eric Dey commented on CLOUDSTACK-374:
-------------------------------------
I am currently out of the office and will return on November 26th. If you
require immediate support on a Caringo product, please use our help web site
at: [1]https://support.caringo.com/
-Eric
----------------------------------
Eric Dey [2]<eric....@caringo.com>
Caringo, Inc. (512)782-9902
----------------------------------------------------------------------------------------
[1] https://support.caringo.com/
[2] mailto:eric....@caringo.com
> 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.0.1, 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
