canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

Hi everyone,

Can you please take a few minutes and help fill out this spreadsheet I
created to track the servers in our infrastructure, their purpose, and
the jobs running on them?

https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AsrQdQZYlWyydDhjaW10bWFJdFJGZ2hYOE9EZ1kyRXc#gid=3

I know we have the rather thorough wiki page on the hardware itself
(https://wiki.canonical.com/UbuntuEngineering/QA/Lab), but I would
like something that helps us identify what hardware we can recycle for
other use and what jobs we can cull.

For example, why do we still have a ton of pandas when we now have the
Calxeda? Are they wired up to anything? Can we bin them?

If there are systems/jobs outside the remit of CI, I want to know why
we're running those and on whose behalf.

So please start to review the Jenkins jobs and help identify the
owners and whether these are really needed anymore.

Our goal should be to get our infrastructure pared down to just what
we absolutely need so that when we move to 1SS we're not doing a lot
of extra work or taking lots of cruft with us. Think of it like doing
a spring cleaning before you move house.

Thanks!