On 11/09/14 23:17, Rohit Yadav wrote:
After you install CloudStack and run cloudstack-setup-databases this tool will
pick IP from the first valid nic it finds (cloud0 being the first one
alphabetically, do a ifconfig to list nics and ips).
To override, give a -i <ipt to this tool>, example:
cloudstack-setup-database -i <IP you> <other params from docs>
Thanks for your help Rohit,
I have been running these commands from a batch file and still I get
404. (I put them into a batch file because I ran into other problems *)
# Stop everything so 8080 is not used
/etc/init.d/cloudstack-management stop
/etc/init.d/cloudstack-agent stop
/etc/init.d/tomcat6 stop
# get rid of the databases
mysqladmin -uroot -ppwd drop cloud
mysqladmin -uroot -ppwd drop cloudbridge
mysqladmin -uroot -ppwd drop cloud_usage
# purge cloudstack from the system and remove all traces of installation
yum -y remove cloudstack-* tomcat*
rm -fR /usr/share/cloudstack-*
rm -fR /etc/cloudstack/
# install management & usage
yum -y install cloudstack-management cloudstack-usage
# configure with IP thanks to Rohit
cloudstack-setup-databases cloud:xxxx@localhost --deploy-as=root:xxxxxx
-i 192.168.5.1
cloudstack-setup-management
I can't get my head around why a purging followed by a clean install
will not eventuate in a web UI and not a 404
Any help appreciated.
Cheers
Piers
* As per my other list posts:
- Getting the networking suiting my set up from the guided install was
working not desired
I have eth0-eth03 with the secondary storage server on 192.168.5.2 /
eth2[IP 192.168.5.1] and a public IP on eth0. Ideally I would like to
create instances on 192.168.5.0 (eth2) and allocate them Public IP's
from the subnet on eth0
eth0 is bridged to cloudbr0
- Deleting the install via the GUI kept on complaining about things in
use that I could not turn off
- Not being a production set up it is easier to wipe than
break-it-until-its-fixed / fix-it-until-its-broken
