Closed Bug 871738 Opened 12 years ago Closed 12 years ago

Create marketapps 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 "marketapps" to support development of test automation for third party Firefox OS applications. I'm including Bug 860472 for reference, that was the last time a new datazilla project was created, in-case any datazilla_stage user permission problems arise again. Please carry out steps 1-4 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 marketapps --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 "marketapps" 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") 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
(In reply to Jonathan Eads ( :jeads ) from comment #0) > > Please carry out steps 1-4 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: [root@datazillaadm.private.scl3 datazilla]# ./manage.py create_perftest_project --project marketapps --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: marketapps > 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") done. > 3.) Update the crontab to include the new changes in crontab.txt > (https://github.com/mozilla/datazilla/blob/master/crontab.txt) committed and active on datazilladm. > 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
Assignee: server-ops-webops → cturra
Status: NEW → RESOLVED
Closed: 12 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Whiteboard: [push interrupt]
Thanks for the quick turn around! It looks like the web servers on stage and production are returning 404's for marketapps but the newly created databases are present and their schema's look good. I think the changes made in datazilla/datazilla/settings/local.py have not been loaded into the webserver. Could you try restarting the webserver on stage and production? If that works I will make sure to add that to the steps to create a new project in the future.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
i should have known better - for these changes to take place, we have to update the wsgi file for mod_wsgi. either touch(ing) the wsgi file or an `apache graceful` does the trick. sorry for not testing this better! https://datazilla.mozilla.org/marketapps
Status: REOPENED → RESOLVED
Closed: 12 years ago12 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.