This is the tentative schedule for the 1.1 release.
The issue list for the 1.1 release is here http://code.google.com/p/eas/issues/list?can=2&q=Milestone%3DRelease1.1
Based on our rate of progress over the last few weeks of work on production
readiness, it seems to me that it is reasonable to pick a release date of Sept 19.
Given that release date I'd like to propose the plan as follows.
Aug 29 - Sept 2
Integration Testing
Complete Monitoring Setup
Sept 6 - Sept 9
Parallel testing
Spet 12 - Sept 16
Parallel testing
Sept 19 - Sept 23
Failover testing
Sept 26
go live
Monitoring Setup
...
Completed
The best way to see what we are monitoring is to llok at the nagios web page http://10.1.3.155/nagios/ (auth required)
Integration Testing
...
Completed
See this page for details. http://sfgovdt.jira.com/wiki/display/MAD/EAS-AVS+Integration+Testing
We put the nagios configurations into a jira project which is here http://sfgovdt.jira.com/wiki/display/NAGIOS/Home
Parallel testing
...
Scheduling in Progress
The plan is here http://sfgovdt.jira.com/wiki/display/MAD/EAS-AVS+Parallel+Testing
Switchover testing
...
I'd like to do this after parallel but that is negotiable.
The plan is here http://sfgovdt.jira.com/wiki/display/MAD/Business+Continuation+Plan
Go Live
...
The day we've all been waiting for!
1) run the avs load one last time (PROD to PROD)
2) All the jobs on this page with a "2" in the notes column must be turned off. http://sfgovdt.jira.com/wiki/display/MAD/scheduled+jobs
3) add PROD configurations to the DBI web server for the change notifcations.
Right now we use dbiweb.sfgov.org/dbiws_eas_qa/eas_to_dbi.asmx/postAddressXMLtoDBI.
I think we need to an additional URL, something like dbiws_eas_prod.
4) Whatever the path is in the item above, we need to add that to this line of EAS code http://sfgovdt.jira.com/source/browse/MAD/trunk/web/settings_env/live/environments.py?r=3114#to67