Closed Bug 797468 Opened 12 years ago Closed 11 years ago

badgus stage environments

Categories

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

All
Other

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jsocol, Unassigned)

References

Details

(Whiteboard: [triaged 20121003][tracker])

This is a tracker for whatever work needs to be done to get the current badges-dev.allizom.org up to snuff and create a stage instance. Corey says -dev is already on generic, so I think all we need to do there is get the code updating.

Hopefully Corey or someone else from webops can help flesh out the details here.
I'm fairly sure that -dev is already good, since I think it was set up and was auto-updating from github very shortly before I stopped doing major development for awhile. (ie. around june)
As far as I can tell badgus-dev.allizom.org (not the name diff) is already alive and running on generic, and auto-updates every 15 minutes from here:

	url = https://github.com/lmorchard/badg.us.git

I don't see a stage or prod instance, though... just dev.
(In reply to Jake Maul [:jakem] from comment #2)

> I don't see a stage or prod instance, though... just dev.

Yeah, I think that's the main ask here: a stage instance, ideally with chief for pushes.

prod needs a sec-review first, but I haven't had a chance to file that bug yet
I am working on setting up a stage environment, which will include Chief(In reply to Les Orchard [:lorchard] from comment #3)
> (In reply to Jake Maul [:jakem] from comment #2)
> 
> > I don't see a stage or prod instance, though... just dev.
> 
> Yeah, I think that's the main ask here: a stage instance, ideally with chief
> for pushes.
> 
> prod needs a sec-review first, but I haven't had a chance to file that bug
> yet
Assignee: server-ops-webops → bburton
Severity: minor → normal
Priority: -- → P4
Whiteboard: [triaged 20121003]
I am working on setting up a stage environment, which will include Chief(In reply to Les Orchard [:lorchard] from comment #3)
> (In reply to Jake Maul [:jakem] from comment #2)
> 
> > I don't see a stage or prod instance, though... just dev.
> 
> Yeah, I think that's the main ask here: a stage instance, ideally with chief
> for pushes.
> 
> prod needs a sec-review first, but I haven't had a chance to file that bug
> yet
Summary: Badges dev/stage environments → badgus stage environments
This should be working now.

I copied the -dev directory and edited the configs and update script, I initialized a new database, let me know if I should bring over the data from dev.

I setup my profile and made and issued a couple badges, https://badgus.allizom.org/en-US/badges/badge/did-it-gangnam-style and https://badgus.allizom.org/en-US/badges/badge/you-did-something-solarce-disapproves-of

One thing that didn't seem to happen was the django_site table getting set properly.

I had to manually edit it via the mysql shell

mysql> select * from django_site
    -> ;
+----+-------------+-------------+
| id | domain      | name        |
+----+-------------+-------------+
|  1 | example.com | example.com |
+----+-------------+-------------+
1 row in set (0.00 sec)

mysql> update django_site set domain = 'badgus.allizom.org' where id = 1;
Query OK, 1 row affected (0.05 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> update django_site set name = 'badgus.allizom.org' where id = 1;
Query OK, 1 row affected (0.05 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> select * from django_site;
+----+--------------------+--------------------+
| id | domain             | name               |
+----+--------------------+--------------------+
|  1 | badgus.allizom.org | badgus.allizom.org |
+----+--------------------+--------------------+
1 row in set (0.00 sec)

mysql> select * from django_site;
+----+--------------------+--------------------+
| id | domain             | name               |
+----+--------------------+--------------------+
|  1 | badgus.allizom.org | badgus.allizom.org |
+----+--------------------+--------------------+
1 row in set (0.00 sec)
Status: NEW → ASSIGNED
I'll be setting up Chief this morning
Assignee: bburton → server-ops-webops
Whiteboard: [triaged 20121003] → [waiting][webops][triaged 20121003]
(In reply to Brandon Burton [:solarce] from comment #7)
> I'll be setting up Chief this morning

Was chief ever set up? If so, where & can I have the password pretty please?
(In reply to Les Orchard [:lorchard] from comment #8)
> (In reply to Brandon Burton [:solarce] from comment #7)
> > I'll be setting up Chief this morning
> 
> Was chief ever set up? If so, where & can I have the password pretty please?

Ping? There've been some updates to the code, but I have no way to update staging
Blocks: 797857
This never got setup.

I pushed stage for you

[bburton@genericadm.private.phx1 ~]$ sudo /data/genericrhel6-stage/src/badgus.allizom.org/update 
Updating code...
Updating vendor submodules...
Cleaning gitignore and pyc files...
Running migrate...
/data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/nose/plugins/manager.py:405: UserWarning: Module south was already imported from /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor-local/src/django-south/south/__init__.py, but /usr/lib/python2.6/site-packages is being added to sys.path
  import pkg_resources
/data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/nose/plugins/manager.py:405: UserWarning: Module djcelery was already imported from /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/djcelery/__init__.py, but /usr/lib/python2.6/site-packages is being added to sys.path
  import pkg_resources
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
No fixtures found.

Synced:
 > badgus.base
 > funfactory
 > django.contrib.auth
 > django_sha2
 > django.contrib.contenttypes
 > django.contrib.sessions
 > commonware.response.cookies
 > djcelery
 > session_csrf
 > django.contrib.sites
 > django.contrib.messages
 > django.contrib.admin
 > taggit
 > badgus.profiles
 > notification
 > south

Not synced (use migrations):
 - badger
 - badger_multiplayer
(use ./manage.py migrate to migrate these)
/data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/nose/plugins/manager.py:405: UserWarning: Module south was already imported from /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor-local/src/django-south/south/__init__.pyc, but /usr/lib/python2.6/site-packages is being added to sys.path
  import pkg_resources
/data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/nose/plugins/manager.py:405: UserWarning: Module djcelery was already imported from /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/djcelery/__init__.pyc, but /usr/lib/python2.6/site-packages is being added to sys.path
  import pkg_resources
Running migrations for badger:
- Nothing to migrate.
 - Loading initial data for badger.
No fixtures found.
Running migrations for badger_multiplayer:
- Nothing to migrate.
 - Loading initial data for badger_multiplayer.
No fixtures found.
Storing revision information...
Compressing assets...
/data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor/lib/python/nose/plugins/manager.py:405: UserWarning: Module south was already imported from /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/vendor-local/src/django-south/south/__init__.pyc, but /usr/lib/python2.6/site-packages is being added to sys.path
  import pkg_resources
To turn on cache busting, use settings.CACHEBUST_IMGS
Minifying /data/genericrhel6-stage/src/badgus.allizom.org/badg.us/media/js/base-all.js (using YUI Compressor)
Unchanged files skipped for minification: 6
Deploying code...
[2012-12-20 12:31:47] Running rsync_project
[2012-12-20 12:31:47] [localhost] running: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --delete /data/genericrhel6-stage/src/badgus.allizom.org/ /data/genericrhel6-stage/www/badgus.allizom.org/
[2012-12-20 12:31:50] [localhost] finished: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --delete /data/genericrhel6-stage/src/badgus.allizom.org/ /data/genericrhel6-stage/www/badgus.allizom.org/ (2.914s)
[2012-12-20 12:31:50] Finished rsync_project (2.915s)
[2012-12-20 12:31:50] Running commit_www
[2012-12-20 12:31:50] [localhost] running: cd /data/genericrhel6-stage/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['badgus.allizom.org']'
[2012-12-20 12:32:27] [localhost] finished: cd /data/genericrhel6-stage/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['badgus.allizom.org']' (36.794s)
[localhost] out: [master c665ccb] deploy [badgus.allizom.org]
[localhost] out: 13 files changed, 85 insertions(+), 44 deletions(-)
[2012-12-20 12:32:27] Finished commit_www (36.794s)
[2012-12-20 12:32:27] Running push_www
[2012-12-20 12:32:27] [generic1.stage.webapp.phx1.mozilla.com] running: /data/bin/update-www.sh badgus.allizom.org
[2012-12-20 12:32:27] [generic2.stage.webapp.phx1.mozilla.com] running: /data/bin/update-www.sh badgus.allizom.org
[2012-12-20 12:32:36] [generic2.stage.webapp.phx1.mozilla.com] finished: /data/bin/update-www.sh badgus.allizom.org (9.020s)
[2012-12-20 12:32:36] [generic1.stage.webapp.phx1.mozilla.com] finished: /data/bin/update-www.sh badgus.allizom.org (9.141s)
[generic1.stage.webapp.phx1.mozilla.com] out: Not removing air.allizom.org/air/vendor-local/lib/python/PIL/
[2012-12-20 12:32:36] Finished push_www (9.141s)
[2012-12-20 12:32:36] [generic1.stage.webapp.phx1.mozilla.com] running: touch /data/www/badgus.allizom.org/badg.us/wsgi/playdoh.wsgi
[2012-12-20 12:32:36] [generic2.stage.webapp.phx1.mozilla.com] running: touch /data/www/badgus.allizom.org/badg.us/wsgi/playdoh.wsgi
[2012-12-20 12:32:37] [generic1.stage.webapp.phx1.mozilla.com] finished: touch /data/www/badgus.allizom.org/badg.us/wsgi/playdoh.wsgi (0.652s)
[2012-12-20 12:32:37] [generic2.stage.webapp.phx1.mozilla.com] finished: touch /data/www/badgus.allizom.org/badg.us/wsgi/playdoh.wsgi (0.654s)
[bburton@genericadm.private.phx1 ~]$ 


I'll see if I can get Chief setup the first week in Jan. It's still a kind of involved manual process, which we're working to streamline in the new year
Whiteboard: [waiting][webops][triaged 20121003] → [triaged 20121003][tracker]
Depends on: 823672
Blocks: 835934
Blocks: 835941
I don't think there's anything more to do here, other than Chief... and there's a separate bug for that, which already directly blocks the main tracker (bug 835934). Closing this one... please re-open if I'm wrong. :)
Status: ASSIGNED → RESOLVED
Closed: 11 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.