Thanks Rohit, this is an awesome fix, and will help in the setup of complex installs.
Sent from my iPhone On Oct 22, 2012, at 10:25 PM, Rohit Yadav <rohit.ya...@citrix.com> wrote: > Hi kdamage, I did not see this thread, just saw the bug ticket and went ahead > and fixed this in master: > https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=947d8cc6de6b69394457fd6f07d3bba82e14fd9f > > So, now you can do this: > cloud-setup-database user:passwd@dbhost -i 192.168.1.10, or > cloud-setup-database user:passwd@dbhost --mshost 192.168.1.10 > > -i thinking ip, -h is already help; --host would be confusing (is it db host > or ms host), hence --mshost. > > Please cherry pick if we want this in 4.0. > > For others on the thread; > It was a simple fix, I went ahead and fixed it because the issue is how the > code detects host IP, it always takes the lower nic and I think a user should > be given power to explicitly set the host ip. > > Regards. > > On 19-Oct-2012, at 2:48 AM, Kelcey Damage (BBITS) > <kel...@bbits.ca<mailto:kel...@bbits.ca>> wrote: > > 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. > > Is this feasible? Or too much work? Should I submit it as a bug? > > KELCEY DAMAGE > Infrastructure Systems Architect > www.backbonetechnology.com<http://www.backbonetechnology.com/> > ------------------------------------------------------------------------- > kel...@bbits.ca<mailto:kel...@bbits.ca> > > address: 55 East 7th Ave, Vancouver, BC, V5T 1M4 > tel: +1 604 713 8560 ext:114 > fax: +1 604 605 0964 > skype: kelcey.damage > >
