Changing configuration of Cloned VMS
- These changes common to all:
- Power on Prod DB Server VM: (which has cloned VM's IP).
- Log into machine using putty session.
- su - root
- Go to and edit /etc/sysconfig/network-scripts/ifcfg-eth0
- replace with correct IP address
- save file
- restart machine with shutdown -r now
- Clone putty session to reflect new IP
- sudo -u postgres -i #logging in as dev in an interactive session
- verify/data/9.0/data/pg_hba.conf contains proper ip values at bottom of file for Web and Geo in SF and SD environments.
- restart DB server (pg_ctl ...) as necessary
- modify the following files under the /etc directory (see svn\eas\configuration\etc)
- hosts
- resolv.conf
- sysconfg/network
Stop db and restart server
- Power on Prod Geo Server
- Change IP address of the VM itself as above
- Change the database connection parameters in geoserver and enable to connection through GeoServer admin console in a browser
- Power on Prod Web Server
- Change the IP addres of the VM as above
- Go to /var/www/html/eas/mad.htconf and go to bottom of file and replace IPs with production IPs of GeoServer and DB Server.
- Make changes to settings_deploy.py file in live directory.
- restart httpd