1147278 - please deploy fxa-{content,auth,oauth,profile} train-33 to production

Status: RESOLVED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[John Morrison [:jrgm]]

Hi Chris,

Please build production stacks for fxa-{content,auth,oauth,profile} train-33

- this will be using nodejs-svcops 0.10.37
- added stored procedures for fxa train-33, and 2 new tables in https://bugzilla.mozilla.org/show_bug.cgi?id=1145474
- Other info: https://mail.mozilla.org/pipermail/dev-fxacct/2015-March/001400.html

In stage, the stacks for content, profile, oauth are: 
  fxa-c-s-train-33-45
  fxa-p-s-train-33-22
  fxa-o-s-train-33-49

For fx-auth, built with ansible-playbook, the command was:

ansible-playbook 
  -e '@default.yml' 
  -e '@fxa-auth/envs/stage.yml' 
  -e 'stack_name=fxa-s-a-33' 
  -e 'auth_app_version=1.33.1-1' 
  -e 'auth_db_version=0.33.0-1' 
  -e 'auth_customs_server_version=0.33.0-1' 
  -e 'auth_puppet_config_version=20150323171006' 
  -i localhost, fxa-auth/playbooks/app.yml

with rpms:

  fxa-customs-server-svcops-0.33.0-1.x86_64.rpm
  fxa-auth-db-server-svcops-0.33.0-1.x86_64.rpm
  fxa-auth-server-svcops-1.33.1-1.x86_64.rpm

Let me know if I've missed something in the details above.

--

$ curl https://accounts.stage.mozaws.net/ver.json; echo; \
  curl https://api-accounts.stage.mozaws.net/; echo; \
  curl https://oauth.stage.mozaws.net/; echo; \
  curl https://profile.stage.mozaws.net/; echo;

{"version":"0.33.0","commit":"32df114a01763943e2d89d8b1d52a250c5aeef49","l10n":"fb2c5223cb","tosPp":"dd16fd3dbe"}
{"version":"1.33.1","commit":"fe580970bc103a6ea37ae8ea3b62a4b7781ab7a0"}
{
  "version": "0.33.0",
  "commit": "2703c2508238f8943b79ec1e5336529b687476f2"
}
{
  "version": "0.33.0",
  "commit": "5cd913646aaf9c96ba39d1487de08c708293d25b"
}

--

Re: rollback: there is no impediment to rolling this release back, and if there are issues/concerns post-release, it can be reverted by switching back DNS to the previous stack.

Comment 1

[John Morrison [:jrgm]]

There was a minor inconsistency in the client yaml config for oauth, and fxa-oauth is now strict to avoid a repeat of the problems we had with mispeled keynames. The upshot is we had to pick up a puppet change. 

Stage stack is rebuilt now. -> fxa-o-s-train-33-51

Pipeline #51
fxa_oauth_serverGitRef:	refs/tags/0.33.0
fxaTrain:	train-33
SvcopRef:	origin/master
PuppetGitRef:	refs/tags/20150325185714-1


Tests pass, so deploy that to production for oauth. Thanks.

Comment 2

[John Morrison [:jrgm]]

:ckolos cut over to the new stacks about 13:50 PDT. Marking fixed.