This bug will track progress of creating the ops assets (jenkins, cloudformation, puppet, etc) and deployment of the stage/prod environments for TestPilot.
Stage has been created / deployed. - stage deploys successfully - jenkins, cloudformation and puppet code has been created - secrets stored encrypted at rest with SOPs It is available at https://testpilot.stage.mozaws.net. Still need to verify that all configurations are set correctly.
Testpilot fixed in stage. - uses production FxA (accounts.firefox.com) for OAuth - fixed configuration issues I was able to sign in. \o/
Summary: Deploy TestPilot to Stage/Dev → Deploy TestPilot to Stage/Prod
Production deployed. Was able to log in.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Les, could you test out production and mark this bug as verified if it is ok.
Okay, my FxA login works, and the admin password works. But, I get Secure Connection Failed errors on these admin pages when I try to create a new experiment: https://testpilot.stage.mozaws.net/admin/experiments/experiment/add/ https://testpilot.firefox.com/admin/experiments/experiment/add/ Both of those pages involve multipart/form-data file uploads for images needed in experiment content. Other admin pages with form posts work, so I suspect the image submissions are the problem
Looks like it was blowing up the max body size that nginx allowed. I've increased this to 256MB. Stage and prod are both updated.
Okay, now I can get past the form submission on stage. But, the images 404 on S3: http://testpilot-stage.s3-website-us-east-1.amazonaws.com/experiments_experiment/2/6/26faa091bc6f0767d90031ebb3898d6c_thumbnail_1457394529_0974.gif Code: NoSuchWebsiteConfiguration Message: The specified bucket does not have a website configuration BucketName: testpilot-stage
Did you want these S3 buckets to also serve HTTP? That is no problem, in prod we prefer to put a CDN in front so the URL will have to be https://testpilot.cdn.mozilla.net
Though, FWIW, it does look like the image made it to S3: http://s3.amazonaws.com/testpilot-stage/experiments_experiment/2/6/26faa091bc6f0767d90031ebb3898d6c_thumbnail_1457394529_0974.gif
> Did you want these S3 buckets to also serve HTTP? Yes, these are image uploads for Experiment site content
Alright, buckets have webhosting enabled.
Thanks Ben and Les. This is looking great.
Images on staging are working, but the URLs for prod images respond with 400 Bad Request: http://testpilot-prod.s3-website-us-east-1.amazonaws.com/experiments_experiment/2/6/26faa091bc6f0767d90031ebb3898d6c_thumbnail_1457455911_0008.JPG Code: IncorrectEndpoint Message: The specified bucket exists in another region. Please direct requests to the specified endpoint. Endpoint: testpilot-prod.s3-website-us-west-2.amazonaws.com I can confirm that the image made it up to S3, though, with a direct bucket URL: http://testpilot-prod.s3.amazonaws.com/experiments_experiment/2/6/26faa091bc6f0767d90031ebb3898d6c_thumbnail_1457455911_0008.JPG
Oh yeah, and this URL works: http://testpilot-prod.s3-website-us-west-2.amazonaws.com/experiments_experiment/2/6/26faa091bc6f0767d90031ebb3898d6c_thumbnail_1457455911_0008.JPG So, maybe just a matter of changing the configured base URL? Though, we probably want an HTTPS CDN in front of that so we don't have mixed content issues on prod
You need to log in before you can comment on or make changes to this bug.