Page Comparison

Issue List

The open issue list for the 1.1 release is here

...

The day we've all been waiting for!

1) DT will run the "AVS To EAS Load" one last time (PROD to PROD)
1.1) This job writes a file to ftp://esfftp.sfgov.org/dbi-external/avsEasLoadResults.csv

2) DBI DBA/developer shall do 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) backup the AVS addresses tableset mode SF WEB LIVE
2.2) add the eas_id column to the addresses tableset mode SD WEB STANDBY
2.3) download the "AVS To EAS Load" results file from the FTP server (ftp://esfftp.sfgov.org/dbi-external/avsEasLoadResults.csv)
2.4) use the avs load results data to update the eas_id columnturn 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.

5) All the jobs on this page

http://sfgovdt.jira.com/wiki/display/MAD/scheduled+jobs

with a "2" in the notes column must be turned off.

6) DT will run a specific set of jobs. These are listed here.

http://sfgovdt.jira.com/wiki/display/MAD/scheduled+jobs

For each job marked with an X in the "GO LIVE" column, you must do the following
Disable the job from being run automatically.
Starting at 1700, run the jobs manually, in the temporal order.
Check with Val early in the day - we need the AVS dump by about 1800 so we can run the AVS load.
Do not enable to automation of these jobs until the following day.

7) DBI shall add PROD configurations to their 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 different path, something like

dbiweb.sfgov.org/dbiws_eas_prod/eas_to_dbi.asmx/postAddressXMLtoDBI.

8) 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#to67Feb 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.