That is true, but it does not seem to change once a zone is deployed. So if that 'undocumented' step is missed, the user needs to start redeploy the db with 'cloud-setup-databases cloud:password@127.0.0.1" (no deploy-as) and then reconfigure db.properties, and re-run "cloud-setup-management" .
Kinda crazy and lengthy method. (Undocumented) -----Original Message----- From: Frank Zhang [mailto:frank.zh...@citrix.com] Sent: Thursday, October 18, 2012 2:35 PM To: CloudStack dev list Subject: RE: cloud-setup-databases build 756 You can change the ip after running the script Go got /etc/cloud/management/db.properties, see cluster.node.IP field. Tough, having a CLI option would be a nice to have feature From: Kelcey Damage (BBITS) [mailto:kel...@bbits.ca] Sent: Thursday, October 18, 2012 2:19 PM To: CloudStack dev list Subject: cloud-setup-databases build 756 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? [cid:image001.png@01CDAD39.F8411B90]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
