The following roles may need to be present to help complete all activities.
The following activities may need to be completed to get things working.
sudo vi /etc/sysconfig/iptables |
Make sure the network services are properly configured, setting the ip and gateway.
/sbin/ifconfig sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0 sudo /etc/init.d/network restart |
Make sure we are using the right nameservers...
sudo vi /etc/resolve.conf |
confirm ntp setup (how?)
sudo vi /etc/hosts |
The linux VMs send emails each day regarding their own general health and status.
Depending on where they are, an email admin may need to adjust the access settings that allow these emails to be sent.
See this file for guidance: https://sfgovdt.jira.com/svn/MAD/trunk/web/settings_env/live/environments.py
Here are the mail servers we us
- ompmta01.sfgov.org
- ironport.sfgov.org
Our email admins are Wayne Curtis or Marco Magellon.
Application Level Activities
The following activities may need to be completed to get the application running properly.
The application keeps addresses and credentials in several places.
The DB configuration files and scripts can be found here
https://sfgovdt.jira.com/svn/DBA/eas/
and include the following
Deploy these manually to master and slave.
The web tier has one configuration file...
https://sfgovdt.jira.com/svn/MAD/branches/1.1/web/settings_env/live/environments.py
Deploy environments.py by using the automated deploy processes.
$ cd /var/www/html $ sudo ./deploy_eas_init.sh |
Geoserver has one configration file...
https://sfgovdt.jira.com/svn/MAD/branches/1.1/geoserver/configuration/live/environments.py
NOte this issue - http://code.google.com/p/eas/issues/detail?id=322
Deploy environments.py by using the automated deploy processes.
$ cd /usr/share/tomcat/webapps/ $ sudo ./deploy_geoserver.sh |
We will also need to update the nagios configurations.
The ETL connections are defined here:
https://sfgovdt.jira.com/svn/MAD/trunk/etl/src/config/live/config_connections.py
In some cases you may need to make changes the connection definitions.
In other cases you'll need to change the ssh configs of putty sessions.