incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-374) When running cloud-setup-databases, it auto chooses the highest priority nic(lowest number ie: eth0)
Date Mon, 07 Jan 2013 21:50:13 GMT

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

Chip Childers updated CLOUDSTACK-374:
-------------------------------------

    Fix Version/s:     (was: 4.1.0)
    
> 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
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          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
>
>
> 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

Mime
View raw message