Thanks for the notes and sorry for missing the meeting (was actually around but thought it was a full-day event reminder that was firing rather than a real meeting, and didn't see the meeting in the daily google calendar email! sorry).
I'm fine with the plan, but it strikes me that we're considering Cambridge for this. Ok, we will eventually get a leased line but: * Cambridge is not a real DC * we're getting recommendations to use EC2 or other major cloud providers to run everything we're doing rather than trying to build our own infrastructure * the relatively large storage requirements would be more easily addressed with services like S3 than with the expensive RAID arrays we'd have to buy
It seems whatever the choice, this is blocked on sysadmin time.
On Tue, Jul 24, 2012, Joey STANFORD wrote:
Howdy,
Meeting notes from today's meeting...
https://wiki.linaro.org/MichaelHope/Sandbox/CBuildMove
Attendees: Michael Andy Joey
Everything is running on an atom server. Need a chunk of ram. Pulls gcc-linaro tip and fires off a build Keeps an eye on gcc-linaro changes all low tech scripts but very robust
Wants to move this over to the Lava Lab.
Andy needs to look at machines left over.
Michael wants to have some control changes as part of this to help unburden it.
- Create cbuild.linaro.org to replace ex.seabright.co.nz
- Add a real or virtual medium capacity machine in the LAVA farm
to run the web server, scheduler, snapshotter, storage, and other administrative stuff
- Add 500 GB+ of backup storage
- Add a reverse proxy to expose the server to the internet
- Delete orion that currently runs ex.seabright.co.nz
- Delete the EC2 micro instance that runs apus.seabright.co.nz
- Redirect and delete builds.linaro.org
Andy thinks the machine isn't a problem. Agrees with the control rework. Dave Piggot gets jerked around by various different activities so it'll be difficult to get the cycles.
Andy proposes:
- Dave can setup the bounce host since lava needs it. Mostly
contained in an existing 12.08 blueprint
- We give someone remote access and let that someone take it over.
Michael volunteered to do this if we go this route
We could spawn something off our openstack instance but Michael is quite concerned about contention. We're still waiting on the leased line to be installed so we don't have great bandwidth in Cambridge at this point.
IO is the killer for this according to Michael.
If we have enough memory it would be helpful to load everything into a tempfs which would increase performance.
Definitely need a dedicated sysadmin in Cambridge. It would be better to have a sysadmin set up the infrastructure as written up by Michael.
Andy would like a lab diagram. Michael will document his proposed layout and then hand that off to Andy and Dave.
Dave and Andy will talk tomorrow and Andy will setup a follow up with Michael.