• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Launchpad oops-tools setup

This page describes how to deploy new code to Launchpad's oops-tools instance, how and which cronjobs are configured, how to make the tool aware of new prefixes when those are added to Launchpad's config files and how to create new reports to be sent to the list.

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

There are some cronjobs setup in the lpqateam crontab.

• update_db
• dir finder

XXX maybe update infestation is unecessary now that we reorganized the team.

• update infestation

Loading new prefixes

Once new prefixes are added to lp:lp-production-configs, they need to be added to oops-tools. Go to:

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

Creating new reports

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