1283209 - Deploy go-syncstorage server into stage for testing

Status: VERIFIED FIXED

(Cloud Services :: QA: General, defect)

Description

[Benson Wong [:mostlygeek]]

A go-syncstorage has been deployed to stage (sync-6). This is a new generation sync storage server, written in go with a new data storage model [1]. 

It has been deployed to stage. It needs to be tested more before a server is rolled out to prod. 

Tests:

- passes the python load test [passes]
- passes the python functional tests [passes]
- Firefox Desktop can sync to it [passes]
- Firefox Android can sync to it [tbd]
- Firefox IOS can sync to it [tbd]


[1] https://github.com/mozilla-services/go-syncstorage

Comment 1

[Benson Wong [:mostlygeek]]

:rnewman

Are there instructions for testing sync on iOS with a stage server?

Comment 2

[Richard Newman [:rnewman]]

I don't believe there are any instructions; we test against prod.

The easiest thing to do is to get set up to build — you'll need this if you find a bug, anyway!

Instructions at:

https://github.com/mozilla/firefox-ios

Run in a simulator or on device, after changing Profile.swift:

    var accountConfiguration: FirefoxAccountConfiguration {
        if isChinaEdition {
            return ChinaEditionFirefoxAccountConfiguration()
        }
        return ProductionFirefoxAccountConfiguration()
    }


to make that last clause `LatestDevFirefoxAccountConfiguration()`. That'll give you latest.dev.lcip.org as your FxA, and token.stage.mozaws.net as your Sync token server. You'll need to make sure the token server points you to the right Sync server, of course.

Nick, am I missing another way? Loading the stage accounts.* page in the browser itself isn't enough.

Comment 3

[Nick Alexander :nalexander [he/him]]

> Nick, am I missing another way? Loading the stage accounts.* page in the
> browser itself isn't enough.

Not that I'm aware of.  I vaguely recall that we built a 5-tap-and-Debug-options-appear on iOS, but now I don't see it.

On Android, you can set Gecko prefs to let you test against a non-production FxA endpoint; see https://dxr.mozilla.org/mozilla-central/source/mobile/android/app/mobile.js?q=path%3Amobile%2F%2A%2A%2Fmobile.js&redirect_type=single#904.  IIRC, setting the token server to a non-production endpoint that then points against a non-production Sync endpoint should just work, but if not, you can also  "dangerously" choose to use stage (with the endpoints from https://dxr.mozilla.org/mozilla-central/source/mobile/android/services/src/main/java/org/mozilla/gecko/fxa/FxAccountConstants.java#21) in Nightly.  If that's necessary, I can help arrange it.

Comment 4

[Benson Wong [:mostlygeek]]

closing this in favor of bug 1296030. The stage box was tested and passed QA. Moving work to the prototype production box.

Comment 5

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

Marking as VERIFIED -- Ben is correct, the stage box passed QA.