Firefox/Input/Crons: Difference between revisions

no edit summary
No edit summary
 
Line 9: Line 9:
==== Themes ====
==== Themes ====
==== Sites ====
==== Sites ====
Sites Processing
* Updates sites clusters used for the "Broken Sites" (release) and the "Sites" (beta) dashboard.
# The backup drop job puts a dump of the input.mozilla.com production DB onto the host cm-metricsetl02 (/data/backup-drop/a01/mysql/input_mozilla_com/ as of 2010-09-15)
0315 PST daily on cm-metricsetl02
# At midnight, sites clusters will be generated by a cronjob running on cm-metricsetl02, first for stage, a few minutes later for production (the responsible scripts are located in the directory /home/mkurze)/jobs/input_mozilla_com_metrics
; <tt>/home/mkurze/jobs/input/update.sh production</tt>:
# For production, those generated sites-clusters are pushed into the database "mozilla_input_metrics" (user "metricswriter"), that is 10.2.70.90 (tp-a01-master01) as of 2010-09-15.
<pre>
# For staging, the host is tm-stage01-master01, the db name is input_metrics_stage_mozilla_com (user is metricswriter as well)
# branch: prod
./manage.py update_product_details
wget -O media/data/opinions.tsv.bz2 http://input.mozilla.com/data/opinions.tsv.bz2
./manage.py generate_sites
</pre>
: configured sites db <tt>mysql://metricswriter@10.2.70.90:/mozilla_input_metrics</tt>


=== Staging ===
=== Staging ===
Line 28: Line 33:
==== Themes ====
==== Themes ====
==== Sites ====
==== Sites ====
Sites Processing
0415 PST daily on cm-metricsetl02
# The backup drop job puts a dump of the input.mozilla.com production DB onto the host cm-metricsetl02 (/data/backup-drop/a01/mysql/input_mozilla_com/ as of 2010-09-15)
* Updates sites clusters used for the "Broken Sites" (release) and the "Sites" (beta) dashboard.
# At midnight, sites clusters will be generated by a cronjob running on cm-metricsetl02, first for stage, a few minutes later for production (the responsible scripts are located in the directory /home/mkurze)/jobs/input_mozilla_com_metrics
; <tt>/home/mkurze/jobs/input/update.sh stage</tt>:
# For production, those generated sites-clusters are pushed into the database "mozilla_input_metrics" (user "metricswriter"), that is 10.2.70.90 (tp-a01-master01) as of 2010-09-15.
<pre>
# For staging, the host is tm-stage01-master01, the db name is input_metrics_stage_mozilla_com (user is metricswriter as well)
# branch: master
./manage.py update_product_details
wget -O media/data/opinions.tsv.bz2 http://input.mozilla.com/data/opinions.tsv.bz2
./manage.py generate_sites
</pre>
: configured sites db <tt>mysql://metricswriter@tm-stage01-master01:/input_metrics_stage_mozilla_com</tt>


When testing on stage, keep in mind that the underlying feedback objects won’t be available in the database. So when viewing a cluster, you will like see an empty page.
When testing on stage, keep in mind that the underlying feedback objects won’t be available in the database. So when viewing a cluster, you will like see an empty page.
48

edits