985124 - Chief deployment for Peekaboo

Status: RESOLVED FIXED

(Infrastructure & Operations :: IT-Managed Tools, task)

Description

[Peter Bengtsson [:peterbe]]

Can we set up Chief for Peekaboo. 

Feel free to take the code from airmozilla since that seems to work perfectly fine.

Comment 1

[Jason Crowe [:jd]]

So

http://peekaboo1.webapp.scl3.mozilla.com/chief/peekaboo.prod

is live. There is no deploy script yet so it does nothing as of this moment. I will start working on the dev environment in the morning. Once that is in place we can create and test a deploy script, then add it to prod.

Cheers

Comment 2

[Jason Crowe [:jd]]

I believe things are almost working now. The stuff on the server seems to be functioning and the deploy script makes it most of the way through. The current bug is about a define:

File "/data/www/peekaboo.allizom.org/peekaboo/bin/update/deploy.py", line 103, in update
    update_locales()
NameError: global name 'update_locales' is not defined


You can see this at the end of the log here:
http://peekaboo1.webapp.scl3.mozilla.com/chief/peekaboo.stage/logs/master.1397259909

If you make tat fix, you should be able to get the update by deploying, you will get the error on first deploy but if things are working correctly it should go away after that.

Please let me know if it works or is you have any errors or if you need my help.

Cheers

Comment 3

[Peter Bengtsson [:peterbe]]

Fixed in https://github.com/mozilla/peekaboo/commit/9571691a05a6dad475fccd46623fa8b735a1db02

Comment 4

[Jason Crowe [:jd]]

That issue is sorted, but now we are getting:

File "/data/www/peekaboo.allizom.org/peekaboo/bin/update/deploy.py", line 110, in deploy
    checkin_changes()
NameError: global name 'checkin_changes' is not defined

Also while we are at it I do not see update defined, from line 118. Unless I am not reading this correctly of course.

Let me know when you have these fixed and I will try again.

Comment 5

[Peter Bengtsson [:peterbe]]

Removed https://github.com/mozilla/peekaboo/commit/554d513caac6f26b769971f218919cd5086de834

Comment 6

[Jason Crowe [:jd]]

Success!

http://peekaboo1.webapp.scl3.mozilla.com/chief/peekaboo.stage/logs/master.1397513331

I am going to close this out now. Prod should work as soon as this most recent deploy script gets pushed there. You will need to file a bug for that prod push whenever you are ready but after that you should be able to use Chief full time.

Cheers

Comment 7

[Peter Bengtsson [:peterbe]]

Sorry. 

I did a push and it said it was successful:
http://peekaboo1.webapp.scl3.mozilla.com/chief/peekaboo.stage/logs/master.1397513983

I pushed master which I know has https://github.com/mozilla/peekaboo/commit/d012a875f73bba6202913de80a22f2bc2a0a4785 in it but the https://peekaboo.allizom.org/media/revision.txt revision is stuck on one commit behind.

Comment 8

[Jason Crowe [:jd]]

I think it is behind. if you see line 22 & 23 you do a git fetch and git checkout. You can see in the log file it says:
[localhost] out: Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.

You need to add a 'git pull origin' to fast forward or change your git methodology to avoid the need to fast forward.

Further, the log says:
[2014-04-14 15:19:45] Running update_info

and line 90 writes this information to the revision.txt file.

Further, from the server:
# git rev-parse HEAD
554d513caac6f26b769971f218919cd5086de834

Which aligns with the revision.txt file.

I hope this helps.