Closed
Bug 735509
Opened 9 years ago
Closed 9 years ago
Push Affiliates to stage
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rik, Assigned: jason)
Details
Affiliates needs to be pushed to stage, as soon as possible so we can test before our production push on Wednesday. Thanks! Release notes at https://wiki.mozilla.org/Websites/Affiliates/Release/2012/3
Updated•9 years ago
|
Assignee: server-ops → bburton
Status: NEW → ASSIGNED
Comment 1•9 years ago
|
||
jason will have to set up stage to use our new commander script for deployment. In addition, after the code is updated, the following command needs to be run to set up the site for south: ./manage.py migrate --fake You can test if south is working properly by running ./manage.py syncdb ./manage.py migrate Both commands should report back no errors (or changes, for that matter).
Comment 2•9 years ago
|
||
I tried to give this a go, by copying /data/engagement-dev/src/affiliates.allizom.org/update to /data/engagement-stage/src/affiliates.allizom.org/update_commander , first I had to manually fix an indent issue, per https://github.com/mozilla/affiliates/commit/00e1bd82775656479f8f53f268f6753bd4bb29bf But now it can find a commander module [root@engagementadm.private.phx1 ~]# cat /data/engagement-stage/src/affiliates.allizom.org/affiliates-app/media/updater.output.txt Traceback (most recent call last): File "/usr/bin/commander", line 4, in <module> main() File "/usr/lib/python2.6/site-packages/commander/main.py", line 96, in main cmd_mod = import_cmdfile(cmdfile) File "/usr/lib/python2.6/site-packages/commander/main.py", line 81, in import_cmdfile return imp.load_source('cmdfile', cmdfile) File "/data/engagement-stage/src/affiliates.allizom.org/affiliates-app/scripts/update/deploy.py", line 15, in <module> import commander_settings as settings ImportError: No module named commander_settings Jason, can you check this out in the morning, since you setup dev, then let me know how you fixed it :)
Assignee: bburton → jthomas
Assignee | ||
Comment 3•9 years ago
|
||
We just needed to make sure commander_settings.py was in the correct location. We may want to update scripts/update/deploy.py update_info to output information about south migrations instead of schematic. https://affiliates.allizom.org/media/updater.output.txt [root@engagementadm.private.phx1 affiliates.allizom.org]# ./update_commander Running 'deploy_app' [engagement1.stage.seamicro.phx1.mozilla.com] running: /data/bin/update-www.sh affiliates.allizom.org [engagement2.stage.seamicro.phx1.mozilla.com] running: /data/bin/update-www.sh affiliates.allizom.org [engagement1.stage.seamicro.phx1.mozilla.com] finished: /data/bin/update-www.sh affiliates.allizom.org (14.236s) [engagement1.stage.seamicro.phx1.mozilla.com] running: /bin/touch /data/www/affiliates.allizom.org/affiliates-app/wsgi/playdoh.wsgi [engagement1.stage.seamicro.phx1.mozilla.com] finished: /bin/touch /data/www/affiliates.allizom.org/affiliates-app/wsgi/playdoh.wsgi (1.017s) [engagement2.stage.seamicro.phx1.mozilla.com] finished: /data/bin/update-www.sh affiliates.allizom.org (15.353s) [engagement2.stage.seamicro.phx1.mozilla.com] running: /bin/touch /data/www/affiliates.allizom.org/affiliates-app/wsgi/playdoh.wsgi [engagement2.stage.seamicro.phx1.mozilla.com] finished: /bin/touch /data/www/affiliates.allizom.org/affiliates-app/wsgi/playdoh.wsgi (1.267s) Running 'prime_app' [engagement1.stage.seamicro.phx1.mozilla.com] running: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:80/ & sleep 1; done [engagement2.stage.seamicro.phx1.mozilla.com] running: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:80/ & sleep 1; done [engagement1.stage.seamicro.phx1.mozilla.com] finished: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:80/ & sleep 1; done (11.026s) [engagement1.stage.seamicro.phx1.mozilla.com] running: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:81/ & sleep 1; done [engagement2.stage.seamicro.phx1.mozilla.com] finished: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:80/ & sleep 1; done (11.344s) [engagement2.stage.seamicro.phx1.mozilla.com] running: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:81/ & sleep 1; done [engagement1.stage.seamicro.phx1.mozilla.com] finished: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:81/ & sleep 1; done (19.888s) [engagement2.stage.seamicro.phx1.mozilla.com] finished: for i in {1..10}; do curl -so /dev/null -H 'Host: affiliates.allizom.org' -I http://localhost:81/ & sleep 1; done (24.355s)
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•