This will be the dev environment for the balrog app, which will be deployed in staging (bug 832460) and production (bug 832461) environments. So, it must be compatible with those environments in terms of OS and software versions. As noted in emails and meetings, this is a blocker for the cross group Q3 goal "start using new update server in production", and is needed no later than Aug 13 to meet that goal.

:jakem just pointed me to a dev environment that he setup for this a couple months ago. you can find it at: https://aus4-dev.allizom.org/ and the admin interface at: https://aus4-admin-dev.allizom.org is there something outstanding here that i have missed?

(In reply to Chris Turra [:cturra] from comment #1) > :jakem just pointed me to a dev environment that he setup for this a couple > months ago. ... > is there something outstanding here that i have missed? Yes -- IT had requested/suggested that the dev environment be replaced in the past. (And we were told hardware had been allocated - hence our expectation for a new system.) If you're saying the existing dev environment has the identical OS & software stack versions as the staging and production systems will, that is welcome news. Prior information was that there would be OS and software stack differences between the old dev (on seamicro atom?) and the new production (vms?). Our interest for the dev box is identical software versions. Please confirm those match precisely with the spec for staging & production.

:cturra - looking for agreement or further discussion on comment 2 -- I forgot to set needinfo yesterday

i just had a look and the dev environment i pointed out to you is running on seamicro atoms. this is not identical hardware to what we will be moving you to, but does share the same operating system and software, so should be sufficient to get you started. i will work on moving these over to seamicro xeons and track when that is complete in this bug. this work can also be done in parallel to any work you need to do.

i have /mostly/ finished up with the work for the dev environment. everything is now running through the new xeon node. during the deployment, i made a pull request to move the conf files into a relative path to the application. it can be found at: https://github.com/mozilla/balrog/pull/15 once that is merged, i can setup up the auto updates for this environment.

Change merged -- thanks much!

:hwine - thnx for merging my pull request :) i have completed the auto update scripts so the dev environment checks for updates every 15 minutes. everything should now be good to go for your new dev environment :)

I think things are looking good. I can login to aus1.dev.webapp.phx1 successfully. And AFAICT, https://aus4-dev.allizom.org and https://aus4-admin-dev.allizom.org are both pointing at the new node, rather than the old ones. Thanks Chris.