Update:Remora Deployment: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Reverted edit of Re4O6e, changed back to last version by Morgamic) |
||
| Line 1: | Line 1: | ||
[[Remora:Update| | [[Remora:Update|« Back to Remora]] | ||
== Databases == | |||
=== Run Migration Script === | |||
'''Wil did this on a non-RHEL box''' | |||
'''You need at least python 2.4 to run this''' Run ''python -V'' to check your version. Lots of additional info and examples for the migration script [[Update:Remora_Database_Migration|is available ]] | |||
* Go to /services/bin/ | |||
* Create migration.conf and fill in values. For example, mine looks like: | |||
oldDatabaseName=c_amov2 | |||
oldPassword=******** | |||
oldServerName=localhost | |||
oldUserName=web | |||
newDatabaseName=c_remora | |||
newPassword=******** | |||
newServerName=localhost | |||
newUserName=web | |||
fileCachePath=files | |||
* The fileCachePath is a relative path that will hold a copy of all the versions of all the addons - you'll need to create this directory. In my example, I created a directory named "files" in /services/bin/. | |||
*(If you're thinking of moving the migration.py script out of /services/bin, that's fine, but take blank.png with it - they need to be in the same dir when the script runs) | |||
* Run ''./migration.py -MAv --recalculateHash >> migrate.out 2>&1'' - I'm redirecting the output here because there is a lot and we should look through it for errors. | |||
* When this is finished, check migrate.out to make sure it finished happily | |||
* Move the fileCachePath directory to /site/app/webroot/ '''VERIFY THIS''' | |||
=== Run SQL Patches === | |||
* Run SQL to modify migrated data for production | |||
== Web Server Config == | |||
=== Files === | |||
=== Service URLs === | |||
addons.mozilla.org/update/VersionCheck.php -> services/update.php | |||
pfs.mozilla.org/plugins/PluginFinderService.php -> services/pfs.php | |||
addons.mozilla.org/blocklist | |||
Rewrites | |||
# Rewrites to be compatible with older versions of addons. | |||
RewriteRule ^update/VersionCheck.php(.*)$ update.php$1 | |||
# Rewrite for client blocklist requests. | |||
# Example: | |||
# /blocklist/1/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/1.5 -> blocklist.php?reqVersion=1&appGuid={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=1.5 | |||
RewriteRule ^blocklist/(.+)/(.+)/(.+)[/]{0,1}$ blocklist.php?reqVersion=$1&appGuid=$2&appVersion=$3 | |||
# PFS | |||
# ? it is in production, but not known. | |||
== Post-deployment Checklist == | |||
The following should be checked: | |||
* <strike>Memcache server operational w/ stats on serverstatus page</strike> | |||
* <strike>Start page dictionary links (non en-US) work</strike> mm | |||
* Installation | |||
** <strike>Add-on installation works</strike> mm | |||
** <strike>Theme installation works</strike> mm | |||
** <strike>Search-engine installation works</strike> mm | |||
** <strike>Dictionary installation works</strike> mm | |||
** <strike>Add-on installation works w/ EULA</strike> mm | |||
* Services | |||
** <strike>Verify add-on and theme updates</strike> mm | |||
** <strike>Verify blocklist XML output</strike> mm | |||
** <strike>Verify PFS works for popular mime-types</strike> mm | |||
** Verify that download counts are being updated (set up cron job!) (see bug 375283) | |||
** <strike>Verify that the new add-on directory that gets pushed to releases gets scanned for viruses</strike> (justdave did this) | |||
* Client pages | |||
** <strike>Get more add-ons</strike> mm | |||
** <strike>Get more themes</strike> mm | |||
** <strike>Get more search-engines</strike> mm | |||
** <strike>Resulting pages show up in correct locale!</strike> mm | |||
* <strike>Top secret workarounds work!</strike> mm | |||
Revision as of 18:00, 10 April 2007
Databases
Run Migration Script
Wil did this on a non-RHEL box
You need at least python 2.4 to run this Run python -V to check your version. Lots of additional info and examples for the migration script is available
- Go to /services/bin/
- Create migration.conf and fill in values. For example, mine looks like:
oldDatabaseName=c_amov2 oldPassword=******** oldServerName=localhost oldUserName=web newDatabaseName=c_remora newPassword=******** newServerName=localhost newUserName=web fileCachePath=files
- The fileCachePath is a relative path that will hold a copy of all the versions of all the addons - you'll need to create this directory. In my example, I created a directory named "files" in /services/bin/.
- (If you're thinking of moving the migration.py script out of /services/bin, that's fine, but take blank.png with it - they need to be in the same dir when the script runs)
- Run ./migration.py -MAv --recalculateHash >> migrate.out 2>&1 - I'm redirecting the output here because there is a lot and we should look through it for errors.
- When this is finished, check migrate.out to make sure it finished happily
- Move the fileCachePath directory to /site/app/webroot/ VERIFY THIS
Run SQL Patches
- Run SQL to modify migrated data for production
Web Server Config
Files
Service URLs
addons.mozilla.org/update/VersionCheck.php -> services/update.php pfs.mozilla.org/plugins/PluginFinderService.php -> services/pfs.php addons.mozilla.org/blocklist
Rewrites
# Rewrites to be compatible with older versions of addons.
RewriteRule ^update/VersionCheck.php(.*)$ update.php$1
# Rewrite for client blocklist requests.
# Example:
# /blocklist/1/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/1.5 -> blocklist.php?reqVersion=1&appGuid={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=1.5
RewriteRule ^blocklist/(.+)/(.+)/(.+)[/]{0,1}$ blocklist.php?reqVersion=$1&appGuid=$2&appVersion=$3
# PFS
# ? it is in production, but not known.
Post-deployment Checklist
The following should be checked:
Memcache server operational w/ stats on serverstatus pageStart page dictionary links (non en-US) workmm- Installation
Add-on installation worksmmTheme installation worksmmSearch-engine installation worksmmDictionary installation worksmmAdd-on installation works w/ EULAmm
- Services
Verify add-on and theme updatesmmVerify blocklist XML outputmmVerify PFS works for popular mime-typesmm- Verify that download counts are being updated (set up cron job!) (see bug 375283)
Verify that the new add-on directory that gets pushed to releases gets scanned for viruses(justdave did this)
- Client pages
Get more add-onsmmGet more themesmmGet more search-enginesmmResulting pages show up in correct locale!mm
Top secret workarounds work!mm