1226453 - Change Syncto server URL to production one (1.4.0) for v2.5

Status: RESOLVED FIXED

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

Description

[Sean Lee [:seanlee][:weilonge]]

After deploying the syncto server to 1.4.0 for stage, it's the time to change Syncto server URL from dev one (https://syncto.dev.mozaws.net/v1/) to stage one (https://syncto.stage.mozaws.net/v1/), and the changes has to be done in common-settings.json.

I am going to check the kinto library probably has to be updated to the correspond version.


==========
diff --git a/build/config/common-settings.json b/build/config/common-settings.json
index 2bfffae..e269ddb 100644
--- a/build/config/common-settings.json
+++ b/build/config/common-settings.json
@@ -244,7 +244,7 @@
    "sync.fxa.audience": "https://token.services.mozilla.com/",
    "sync.scheduler.interval": 3600,
    "sync.scheduler.wifionly": false,
-   "sync.server.url": "https://syncto.dev.mozaws.net/v1/",
+   "sync.server.url": "https://syncto.stage.mozaws.net/v1/",
    "telephony.speaker.enabled": false,
    "tethering.usb.enabled": false,
    "tethering.usb.ip": "192.168.0.1",

Comment 1

[Rémy Hubscher (:natim)]

You shouldn't do that. Because Syncto stage is plugged on the Firefox Sync stage infrastructure.
You should keep on using syncto.dev.mozaws.net until production is deployed.

The stage environment is there for QA and loadtest validation not for production users.
Please do not change that.

Comment 2

[Sean Lee [:seanlee][:weilonge]]

Hey Natim,
I just create this bug to record the task that we have to do once the stage server is online.
Before confirming any status, this won't be changed.

Comment 3

[Rémy Hubscher (:natim)]

Ok as soon as the production server is live you would be able to update to its URL.

It shouldn't be the stage URL but the production one: https://syncto.services.mozilla.com/v1/

Comment 4

[Sean Lee [:seanlee][:weilonge]]

I correct the word from 'stage' to 'production'. sorry for the misunderstanding.

Comment 5

[Rémy Hubscher (:natim)]

No worries, we are apparently on the same page :)

Comment 6

[Michiel de Jong [:michielbdejong]]

Just discussed with Fernando and Rémy, for Foxfooder launch, it's fine to still use the dev server in the beginning.

Comment 7

[Sean Lee [:seanlee][:weilonge]]

Hi Remy, Do you think that we still use "https://syncto.dev.mozaws.net/v1/" if there is a real product to use Syncto?

Comment 8

[Rémy Hubscher (:natim)]

I know that QA are working on it.

Karl do you have a ETA of when this will be in production so that we can use the production server rather than the dev one?

Comment 9

[Karl Thiessen [:kthiessen, he/him]]

As in bug 1221204, I will check in with :bobm and report back.  Leaving the needinfo here for me to remind me to do this quickly.

Comment 10

[Karl Thiessen [:kthiessen, he/him]]

We have an ongoing investigation of some FxA changes here: see bug 1265617.

Comment 11

[Ryan Kelly [:rfkelly]]

> We have an ongoing investigation of some FxA changes here:

We've made some additional fixes on the FxA side of things, is this still blocked on work form the FxA team?

Comment 12

[Karl Thiessen [:kthiessen, he/him]]

I do not believe so.  Thanks for checking in, Ryan.

Comment 13

[Aaron Wu]

Hi Travis,

As discussed. the production server will be deployed by May 20th. That will be good if we can have production URL first and prepare for testing.

Thank you!

Comment 14

[Aaron Wu]

Add JP Schneider in the loop, thanks to put an update corresponding to this bug.

Comment 15

[JP Schneider [:jp]]

Does anyone have any concerns with syncto.prod.mozaws.net being the prod url?  Is there any need or use case for a different name?  

Thanks!

Comment 16

[Rémy Hubscher (:natim)]

It works for me :+1:

Comment 17

[JP Schneider [:jp]]

Actually, Travis made a great suggestion to keep this on a services domain.

Any complaints about  syncto.services.mozilla.com  ?

Comment 18

[Rémy Hubscher (:natim)]

Yes even better. Thanks :)

Comment 19

[JP Schneider [:jp]]

I am running a carefully crafted artisinal Jenkins job to create the initial components, and after that we should be able to use the production push features in our Jenkins to get the rest of the infrastructure up.

https://deploy.mozaws.net/job/Syncto-PROD-Deploy-create-sns-once/configure

-------

cd "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}"
ansible-playbook -M "${WORKSPACE}/svcops/cloudformations/deployment/ansible-library" -v \
    -i "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/hosts" \
    -e "stack_name=${STACK_NAME}" \
    -e "@${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/envs/${ENV_NAME}.yml" \
    -e "stack_id=${BUILD_NUMBER}" \
    -e "repo_dir=${PipelineRepoDir}" \
    "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/playbooks/sns-topic.playbook"
    

cd "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}"
ansible-playbook -M "${WORKSPACE}/svcops/cloudformations/deployment/ansible-library" -v \
    -i "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/hosts" \
    -e "stack_name=${STACK_NAME}" \
    -e "@${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/envs/${ENV_NAME}.yml" \
    -e "stack_id=${BUILD_NUMBER}" \
    -e "repo_dir=${PipelineRepoDir}" \
    "${WORKSPACE}/svcops/cloudformations/${MOZ_JENKINS_APP_NAME}/playbooks/elasticache.playbook"


-------------------------

Comment 20

[JP Schneider [:jp]]

This has the few changes it looks like we'll need to move to prod:

https://github.com/mozilla-services/svcops/pull/1058

Comment 21

[JP Schneider [:jp]]

	
syncto1-prod-s-ELB-1BE6JFJ8KMO8M-1772949352.us-west-2.elb.amazonaws.com is the new elb, and syncto.services.mozilla.com is now pointed to this new elb/stack.

Comment 22

[Sean Lee [:seanlee][:weilonge]]

Hi JP,

Both dev and stage links will response a JSON object to show a server summary,
"https://syncto.dev.mozaws.net/v1/"
"https://syncto.stage.mozaws.net/v1/"

but I did not see the same result for https://syncto.services.mozilla.com/v1/. 

Could you help to check it? Thanks.

Comment 23

[Sean Lee [:seanlee][:weilonge]]

Here is the result when I try to ping the domain:

$ ping syncto.services.mozilla.com
ping: cannot resolve syncto.services.mozilla.com: Unknown host

Comment 24

[Daniel Maher [:phrawzty]]

Hello,

The portion of the deployment pipeline that handles DNS modifications had a bug, which I have just rectified.  End result:

;; ANSWER SECTION:
syncto.services.mozilla.com. 299 IN	CNAME	syncto.prod.mozaws.net.
syncto.prod.mozaws.net.	59	 IN	A	52.36.148.233


As an aside, your ping above would have failed in any case - while the DNS should resolve, AWS load balancers don't generally respond to ICMP. :)

Comment 25

[Rémy Hubscher (:natim)]

Appart from the DNS problem apparently https://syncto.services.mozilla.com/v1/ returns an Internal Error.
Do you want to pair to see what is wrong?

Comment 26

[Daniel Maher [:phrawzty]]

pairing now

Comment 27

[Rémy Hubscher (:natim)]

After investigation it appears that the cache configuration URL is not set to use Elasticache redis server, it uses the bogus one configured here: https://github.com/mozilla-services/puppet-config/blob/master/syncto/yaml/app/syncto.prod.yaml#L10 instead of the proper Elasticache one.