1137912 - Please deploy pushgo 1.5rc4 to Loop-Push Stage

Status: VERIFIED FIXED

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

Description

[Ben Bangert [:benbangert]]

1.5rc4 has been verified under my load-testing and is ready to go to staging.

Comment 1

[Jeremy Orem [:oremj]]

Deployed to stage.

Comment 2

[Ben Bangert [:benbangert]]

Richard, this is ready for QA verification before production deploy.

Comment 3

[Ben Bangert [:benbangert]]

I should note, any ticket for production deploy opened by QA, will need some config changes first. Should these config changes be made first to stage? (I'm guessing probably so)

Comment 4

[Richard Pappalardo [:rpapa][:rpappalardo]]

(In reply to Ben Bangert [:benbangert] from comment #3)
> I should note, any ticket for production deploy opened by QA, will need some
> config changes first. Should these config changes be made first to stage?
> (I'm guessing probably so)

Hi Ben, if they're changes that could impact deployment or application behavior then ideally yes. 
What config changes are these?

Comment 5

[Ben Bangert [:benbangert]]

The bucket size needs to be increased to match the amount of servers in the cluster, and always route needs to be enabled.

:oremj, the changes to be made:

- Under [router]
  - bucket_size should match the size of the cluster (in production as well as staging)
- Under [endpoint]
  - always_router should be set to true

That should be it.

Comment 6

[Ben Bangert [:benbangert]]

Sorry, always_route, not always_router

Comment 7

[Jeremy Orem [:oremj]]

I've deployed the config changes. In the future, it would be nice if bucket_size were dynamically configured via etcd, so if the cluster size changes, the bucket size also follows.

Comment 8

[Ben Bangert [:benbangert]]

Ok, :rpapa, config changes are out. Ready for verification.

Comment 9

[Richard Pappalardo [:rpapa][:rpappalardo]]

------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/pushgo/releases

COMPARISONS
https://github.com/mozilla-services/pushgo/compare/1.4.2...1.5rc1
https://github.com/mozilla-services/pushgo/compare/1.5rc1...1.5rc4

TAGS
https://github.com/mozilla-services/pushgo/releases/tag/1.5rc4
https://github.com/mozilla-services/pushgo/commit/ca7b9bf49e3cd77929562b442a6225018e406bd0

Comment 10

[Richard Pappalardo [:rpapa][:rpappalardo]]

(In reply to Ben Bangert [:benbangert] from comment #3)
> I should note, any ticket for production deploy opened by QA, will need some
> config changes first. Should these config changes be made first to stage?
> (I'm guessing probably so)

Thanks, Ben.  Normally, I would create a prod ticket and assign to oremj once stage is verified.  It sounds like these config changes have already been applied on stage and we don't need any further changes there prior to deploying to prod (pls let me know if otherwise).  If so, will we be doing it that way going forward as well? Just want to make sure the deployment process is clear. 

Also, I assume 1.5rc4 will be deployed to prod as 'Loop-push 1.5'?


------------------
TEST SUMMARY
------------------

make test against tag - OK
(https://pastebin.mozilla.org/8824047)

loadtesting (per :benbangert) - OK

end-2-end loop call verification - OK
Placed several calls back and forth between Nightly and DevEd(Aurora).
exercising video/audio mute, join/leave call, window-sharing, etc. functions.

https://loop.stage.mozaws.net/push-server-config & stage load-balancing - OK


Once above is clarified, I'll verify stage.

Comment 11

[Ben Bangert [:benbangert]]

Yep, that is correct, this will be Loop-push 1.5.

Comment 12

[Richard Pappalardo [:rpapa][:rpappalardo]]

Thanks, Ben. I'll create a prod deployment ticket early next week right after loop-client is out the door.

Comment 13

[Richard Pappalardo [:rpapa][:rpappalardo]]

Hey Jeremy, I'd like to coordinate a loop-push prod deployment tomorrow if you're available.  Would you be free in the late morning around 10:30?  If possible, I'd like to do it before noon in case we run into any issues.  If you're busy, we could plan on Thurs. morning instead.  Let me know what works for you.

Comment 14

[Jeremy Orem [:oremj]]

Yes, 10:30 works for me.

Comment 15

[Richard Pappalardo [:rpapa][:rpappalardo]]

OK, great.  I'll ping you then.
Thanks!

ticket here:
Bug 1141860 - Please deploy pushgo 1.5 to Loop-Push Production