Rollout Plan For 1.1 Release

Owned by Paul McCullough (Unlicensed)
Last updated: Feb 14, 2012Version comment
2 min read

Issue List

The open issue list for the 1.1 release is here

http://code.google.com/p/eas/issues/list?can=2&q=Milestone%3DRelease1.1

Monitoring Setup

COMPLETED
The best way to see what we are monitoring is to look at the nagios web page

http://10.1.3.155/nagios/ (auth required - contact Paul)

We put the nagios configurations into a jira project which is here

http://sfgovdt.jira.com/wiki/display/NAGIOS/Home

Integration Testing

COMPLETED
See this page for details.

http://sfgovdt.jira.com/wiki/display/MAD/EAS-AVS+Integration+Testing

Parallel Testing

COMPLETED
The parallel testing plan is here

http://sfgovdt.jira.com/wiki/display/MAD/EAS-AVS+Parallel+Testing

Business Continuation Testing

COMPLETED

The business continuation plan is here

http://sfgovdt.jira.com/wiki/display/MAD/Business+Continuation+Plan

Go Live

PENDING

The day we've all been waiting for!

Tuesday Feb 14

0800

Email Announcement

1500

DT shall Insure that all jobs on the scheduled jobs page
/wiki/spaces/MAD/pages/5308417

  • with a "2" in the notes column must be turned off permanently
  • all other jobs shall be disabled over night

Then

  • EAS into Maint Mode
  • turn off replication
  • halt SD DB
  • halt geoservers
  • halt change notification

  • base line DBs

  • Run ETLs
    • ETL 1.1-migrate_from_beta INIT

    • ETL 1.1-avs_load INIT

    • ETL 1.1-set_privileges INIT

    • ETL parcels STAGE

    • ETL parcels COMMIT

    • ETL streets STAGE

    • ETL streets COMMIT

1700 hours

1) Confirm that we have the latest AVS dump on the FTP site.

  • Run ETLs

    • ETL 1.1-avs_load EXECUTE

    • ETL 1.1-qa_parallel EXECUTE

2.0) After the ETLs have successfuly completed DT does the following
2.1) set mode SF WEB LIVE
2.2) set mode SD WEB STANDBY
2.3) turn on DB replication (SF > SD)
2.4) on SF Web run python restore_users.py
2.5) on SF WEB start change notfication
2.4) run map cache reseed

3) DBI shall modify portions of their ETL from the Assessor into the AVS.
3.1) stop loading addresses into AVS
3.2) continue to load ownership information

4) DBI shall disable the AVS address editing form
4.1) should an "orphaned" address need to be retired, counter staff shall contact MIS.

Feb 15

0730 hours

6) DBI DBA/developer shall do the following
6.1) backup the AVS addresses table
6.2) add the eas_id column to the addresses table
6.3) download the "AVS To EAS Load" results file from the FTP server (ftp://esfftp.sfgov.org/dbi-external/avsEasLoadResults.csv)
6.4) use the avs load results data to update the eas_id column

7) DT shall enable the /wiki/spaces/MAD/pages/5308417 that are not marked with a "2" in the notes column

0800 hours

7) DBI and DT shall test the integration to make sure it is working.