1039637 - Create mozbench Datazilla Project

Status: RESOLVED FIXED

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

Description

[Jonathan Eads ( :jeads )]

We need to create a new datazilla project called "mozbench" to support development of some specialized benchmarking test automation.

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 mozbench --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 "mozbench" project.

2.) Update the following line in datazilla/datazilla/settings/local.py on stage and production.

ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS", "b2g|b2gtw|jetperf|pushlog|stoneridge|talos|test|microperf|marketapps|mozbench")

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.) Run `apache graceful` on the web service on stage and production to load the new modifications in local.py.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

this will be replacing the 'games' project- we should either rename games or delete it :)

Comment 2

[Jonathan Eads ( :jeads )]

Can we use the games project for this? No data has been submitted to games and this would spare us another moz* whatever name.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

I don't see a reason whynot.  If there is a specific need for using mozbench as a name, I will let dminor comment.

Comment 4

[Dan Minor [:dminor]]

(In reply to Joel Maher (:jmaher) from comment #3)
> I don't see a reason whynot.  If there is a specific need for using mozbench
> as a name, I will let dminor comment.

I'd prefer to use the mozbench name for two reasons:
1) It matches the project name
2) We're not planning on only running games benchmarks (the current benchmark is for webaudio)

'Mozbench' is non-descriptive, but I think non-descriptive is better than misleading :)
We should just delete or rename 'games'.

Comment 5

[Jonathan Eads ( :jeads )]

We need to go ahead and carry out the tasks described in the description as soon as possible.

Comment 6

[Chris Turra [:cturra]]

grabbing this bug.

Comment 7

[Chris Turra [:cturra]]

(In reply to Jonathan Eads ( :jeads ) from comment #0)
> 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 mozbench --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: mozbench

*to get this to run, i had to grant additional permissions to the datazilla_stage user on the database. once it was complete, returned the permissions to where they were before.


> 2.) Update the following line in datazilla/datazilla/settings/local.py on
> stage and production.
> 
> ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS",
> "b2g|b2gtw|jetperf|pushlog|stoneridge|talos|test|microperf|marketapps|mozbenc
> h")

updated on stage and prod.


> 3.) Update the crontab to include the new changes in crontab.txt
> (https://github.com/mozilla/datazilla/blob/master/crontab.txt)

added through puppet.


> 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

done on stage and prod.


> 5.) Run `apache graceful` on the web service on stage and production to load
> the new modifications in local.py.

done on stage and prod.