Closed Bug 888420 Opened 12 years ago Closed 12 years ago

Create webpagetest Datazilla Project

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jeads, Assigned: cturra)

Details

(Whiteboard: [push interrupt])

We need to create a new datazilla project called "webpagetest" to support development of test automation. I'm including Bug 871738 for reference, that was the last time a new datazilla project was created, in-case any problems arise again. Also, there is another bug filed to create a new datazilla project, Bug 888386, so it might make sense to consolidate the steps. Please carry out steps 1-5 listed below to create the new project. 1.) To create the required project databases run the following manage command as the datazilla_stage user on the admin node: manage.py create_perftest_project --project webpagetest --perftest_host datazilla-rw-vip.db.scl3.mozilla.com --objectstore_host datazilla-rw-vip.db.scl3.mozilla.com --perftest_type MySQL-TokuDB --objectstore_type MySQL-Aria --cron_batch small This command will create two new databases for the "webpagetest" project. 2.) Update the following line in datazilla/datazilla/settings/local.py on stage and production. ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS", "b2g|jetperf|pushlog|stoneridge|talos|test|microperf|marketapps|games|webpagetest") 3.) Update the crontab to include the new changes in crontab.txt (https://github.com/mozilla/datazilla/blob/master/crontab.txt) 4.) To get the new project into the memcache, the following manage.py command should be run on stage and production: ./manage.py reset_cached_datasources 5.) touch the wsgi file or execute an `apache graceful` to load the new changes in the stage and production environments
(In reply to Jonathan Eads ( :jeads ) from comment #0) > > 1.) To create the required project databases run the following manage > command as the datazilla_stage user on the admin node: [root@datazillaadm.private.scl3 datazilla]# ./manage.py create_perftest_project --project webpagetest --perftest_host datazilla-rw-vip.db.scl3.mozilla.com --objectstore_host datazilla-rw-vip.db.scl3.mozilla.com --perftest_type MySQL-TokuDB --objectstore_type MySQL-Aria --cron_batch small Perftest project created: webpagetest [root@datazillaadm.private.scl3 datazilla]# echo $? 0 > This command will create two new databases for the "webpagetest" project. > > 2.) Update the following line in datazilla/datazilla/settings/local.py on > stage and production. > > ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS", > "b2g|jetperf|pushlog|stoneridge|talos|test|microperf|marketapps|games|webpage > test") done. > 3.) Update the crontab to include the new changes in crontab.txt > (https://github.com/mozilla/datazilla/blob/master/crontab.txt) committed. > 4.) To get the new project into the memcache, the following manage.py > command should be run on stage and production: [root@datazillaadm.private.scl3 datazilla]# ./manage.py reset_cached_datasources [root@datazillaadm.private.scl3 datazilla]# echo $? 0 > 5.) touch the wsgi file or execute an `apache graceful` to load the new > changes in the stage and production environments $ curl -I https://datazilla.mozilla.org/webpagetest HTTP/1.1 200 OK Server: Apache X-Backend-Server: datazilla1.webapp.scl3.mozilla.com Vary: Accept-Encoding Content-Type: text/html; charset=utf-8 Date: Sat, 29 Jun 2013 00:57:57 GMT Accept-Ranges: bytes X-Cache-Info: caching Content-Length: 17511
Assignee: server-ops-webops → cturra
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [push interrupt]
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.