Diff for "QA/OopsToolsSetup"

Not logged in - Log In / Register

Differences between revisions 3 and 4
Revision 3 as of 2011-01-18 15:05:22
Size: 713
Editor: matsubara
Comment: page was renamed from Foundations/QA/OopsToolsDeployment
Revision 4 as of 2011-01-18 15:08:26
Size: 978
Editor: matsubara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= Launchpad oops-tools deployment = = Launchpad oops-tools setup =

==
oops-tools deployment ==
Line 21: Line 23:

== cronjobs ==

XXX: describe update_db script
dir finder
update infestation

== Loading new prefixes ==

* https://lp-oops.canonical.com/prefixloader/

== Creating new reports ==

https://lp-oops.canonical.com/admin/report

Launchpad oops-tools setup

oops-tools deployment

To deploy a new version of LP's oops-tools instance:

ssh devpad
sudo su - lpqateam
cd /srv/lp-oops.canonical.com/cgi-bin/lpoops
bzr up

If there are changes to the models and/or you need to do data migration (a new migration has been created) then run:

bin/django migrate

Usually there's no need to restart the service after an update. Oops tools has a monitor.py script (see src/oopstools/monitor.py) which monitors changes to .py files and when there are changes to them, it kills the process and starts a new one.

cronjobs

XXX: describe update_db script dir finder update infestation

Loading new prefixes

* https://lp-oops.canonical.com/prefixloader/

Creating new reports

https://lp-oops.canonical.com/admin/report

QA/OopsToolsSetup (last edited 2012-09-21 00:14:34 by lifeless)