1021891 - get https://call.mozilla.com for Loop

Status: VERIFIED FIXED

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

Description

[Tarek Ziadé (:tarek)]

we need a certificate + a CNAME pointing to loop.services.mozilla.com

Comment 1

[Wesley Dawson [:whd]]

This is somewhat complicated by SSL certificates, since the certificate we're using for loop.services.mozilla.com won't match the one we have for call.mozilla.com. It may be possible to use two ELBs pointing at the same ASG to get around this (or we could just run a completely separate ELB/ASG for loop-client).

Comment 2

[Wesley Dawson [:whd]]

Ok, I've set up a separate ELB with the call.mozilla.com cert in production that points at the same instances as the current loop app. This means that once we've got DNS set up to point at this new ELB we can merge and deploy https://github.com/mozilla-services/puppet-config/pull/559 and use call.mozilla.com for the user-facing endpoint.

Of note, the ELB was created by hand and the loop ASG is not actually associated with it (only the specific instances are). This is brittle because once we start upgrading stacks the correct way instead of by hand this stuff will stop working. I'll work with :mostlygeek to make sure this is all sorted out next week. As I understand it this is all a temporary measure until we can move call.mozilla.com onto a CDN somewhere anyway.

Comment 3

[Wesley Dawson [:whd]]

The ELB is call-mozilla-com-lb-282870930.us-west-2.elb.amazonaws.com for anyone who wants to set their /etc/hosts to test against it, but the loop app itself is still configured to point at https://call.services.mozilla.com.

Comment 4

[James Bonacci [:jbonacci]]

:whd you are awesome! Thanks!

Comment 5

[Benson Wong [:mostlygeek]]

So: 

 - we have the SSL for call.mozilla.com now
 - we have call.mozilla.com delegated to route53 so we can do whatever we need for the DNS
 - we will need to deploy the new puppet-config code for loop-client to make this all happen
 - when bugs: 1022887 and 1022886 are verified I'll make a change window to set it all up in prod

Comment 6

[Benson Wong [:mostlygeek]]

Resolving this as we have the SSL and the DNS setup.

Comment 7

[James Bonacci [:jbonacci]]

Cool. Will take a look tomorrow...

Comment 8

[Benson Wong [:mostlygeek]]

it points to nothing right now.. when i deploy the loop-client to production as its own stack it should live at https://call.mozilla.com

Comment 9

[James Bonacci [:jbonacci]]

Yep. We can verify this once bug 1024180 is out there...

Comment 10

[James Bonacci [:jbonacci]]

Prod version 0.2.0 is out there and running.