We spent some time talking about what the next milestone for Balrog should and decided that getting it used by some set of users in production is a good thing to shoot for. The main goal here is to get some real testing in production as early as possible in the hopes that it will help figure out what real-world load will look like, where we need caching, etc. Explicitly NOT a part of this is having people on channels other than "nightly" use Balrog. This means that we don't need to support release-only attributes or features.

Removing bugs that aren't actually blockers (just nice to haves).

Current status here, since there hasn't been an update for awhile: We're waiting for stage and production environments, which are actively being worked on by IT. I met with cturra today who told me that the stage one is close to being ready and that they're just sorting through some netflow issues at the moment. The production environment will be worked on afterwards, but it is also blocked on bug 909416 - which is about building a new database cluster for aus4 production. That bug currently says it will be worked on in October by the db folks, but they weren't informed that it blocks a Q3 goal when that information was added. I've added a comment to that effect and I'll do what I can to work with them on getting that bug or a workaround sooner.

(In reply to Ben Hearsum [:bhearsum] from comment #2) > Current status here, since there hasn't been an update for awhile: > We're waiting for stage and production environments, which are actively > being worked on by IT. I met with cturra today who told me that the stage > one is close to being ready and that they're just sorting through some > netflow issues at the moment. This is still being worked. > The production environment will be worked on afterwards, but it is also > blocked on bug 909416 - which is about building a new database cluster for > aus4 production. That bug currently says it will be worked on in October by > the db folks, but they weren't informed that it blocks a Q3 goal when that > information was added. I've added a comment to that effect and I'll do what > I can to work with them on getting that bug or a workaround sooner. The database work got reprioritized and we now have a production database hosted on dedicated hardware. bug 909416 is still open pending backups and monitoring, but the database is ready to use when the production webheads are ready to go.

(In reply to Ben Hearsum [:bhearsum] from comment #3) > (In reply to Ben Hearsum [:bhearsum] from comment #2) > > Current status here, since there hasn't been an update for awhile: > > We're waiting for stage and production environments, which are actively > > being worked on by IT. I met with cturra today who told me that the stage > > one is close to being ready and that they're just sorting through some > > netflow issues at the moment. > > This is still being worked. Tracked in bug 919641. Chris thinks they should be ready sometime tomorrow.

We're done here. bug 922264 is about Thunderbird and shouldn't have been set to blocking this (but is already landed and will take effect tomorrow anyways). bug 832460 is about the aus4 stage environment, which isn't a blocker here. bug 832461 is 95% done, just waiting on monitoring. We didn't halt the push to production on that, which happened yesterday/today and is looking fine. I blogged about this: http://hearsum.ca/blog/new-aus-is-live/