616344 - static web hosting for slave allocator

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

We need a stable place for the slave allocator.  The allocator fills in a placeholder with the slave name, so almost any URL is possible.  I'm using
  http://people.mozilla.com/~dmitchell/allocator/SLAVE
right now, but this isn't particularly scalable, and doesn't allow .tac files to be edited by other members of the team.

Long-term, I'd like to use a vhost like
  http://{production,staging}-slave-allocator.build.mozilla.org/tac?n=SLAVE

But I don't want to write the DB backend just yet - I'd prefer to have a directory where we drop appropriately-named .tac files.  The dir should be accessible to other releng people.  The URL should only be accessible from the build network, since it includes low-security buildslave passwords.

Where should this be?

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

The default allocator is
  http://cruncher.build.mozilla.org/~dustin/allocator/tac/SLAVE
in the current runslave.py's, so cruncher it is.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Well, for linux slaves it's still pointing to people, but all the same, I've verified that the slave side of the allocator works with moz2-linux64-slave07.

I don't think there's much use in a static allocator (meaning putting a bunch of tac files in a directory).  It will buy us nothing, and only confuse things when other releng folks are trying to move slaves around.  Given the time constraint, I should just go for it with the db-backed version (bug 618369).