X-Git-Url: https://git.adam-barratt.org.uk/?a=blobdiff_plain;f=input%2Fhardware-wishlist.creole;h=d51e172e6d5acf0179029e29457f6140549bbd55;hb=01de3807987b4eeb78be0bc249e98b028937f4e1;hp=562f2f292b2e31e91f0086a0af006f1500294b60;hpb=8fd58e3ebd7109f61b907bb42b2c544fa6b61466;p=mirror%2Fdsa-wiki.git diff --git a/input/hardware-wishlist.creole b/input/hardware-wishlist.creole index 562f2f2..d51e172 100644 --- a/input/hardware-wishlist.creole +++ b/input/hardware-wishlist.creole @@ -36,59 +36,6 @@ Proposers: * ftpteam/Joerg Jaspert -== new debian mail setup == - -A set of systems that will handle all incoming mail for all debian systems. -Currently our incoming mail handling is on the individual host hosting a -service, i.e. on master.debian.org for @debian.org, on bugs.debian.org for the -bug tracking system, on lists.debian.org for our mailinglists and on several -other systems for their individual, smaller email traffic. - -Centralizing email handling will allow us to maintain our anti-spam measures in -a single point, avoiding duplicate work and hopefully improving our success. - -Requirements: - -* Four or so systems, in at least two different locations, capable of handling - modern anti-spam software. This probably needs a bit of CPU. -* remote management stuff - -Proposers: - -* Martin Zobel-Helas -* Stephen Gran - -We probably have sufficient hardware for this. Current plan involves using one -new box from HP, murphy, a new old sparc that zobel gets from some place, and -puccini that will soon no longer have packages on it. - -== new bugs.d.o == - -Currently bugs runs on a single DL385g1 system which cannot keep up with the -load that the BTS causes. - -Owner@bugs would like to split the BTS accross multiple hosts: two for incoming -email and spam filtering (would not be required if we had the setup mentioned -above), one master, and at least two user-facing web servers. - -Requirements (assuming the above mentioned mail system is in place, else add -two mail servers): - -* two systems with fast disks (we don't need that much storage, some 200 gigs - should suffice easily for a while - say 4x140 gig raid10), some ram for - caching (say 16g?), and the CPU to handle the scripts (if we can get two quad - cores per box that would be great) -* one master that processes incoming email, changing bugs as required, and - pushes the changes to the web facing servers - -Proposers: - -* Don Armstrong - -If the snapshot hosts go through we might be able to put the bugs front end -webservers on them too. Probably a question of load but it can't hardly be -worse than rietz at the moment. - == merge.d.o == @@ -141,3 +88,79 @@ much spare space. We should be looking at replacing that eventually. A raid6 of big SATA disks would probably provide the required robustness and be cost-effective. + += Historical = + +These proposals probably are no longer relevant: + +== new debian mail setup == + +A set of systems that will handle all incoming mail for all debian systems. +Currently our incoming mail handling is on the individual host hosting a +service, i.e. on master.debian.org for @debian.org, on bugs.debian.org for the +bug tracking system, on lists.debian.org for our mailinglists and on several +other systems for their individual, smaller email traffic. + +Centralizing email handling will allow us to maintain our anti-spam measures in +a single point, avoiding duplicate work and hopefully improving our success. + +Requirements: + +* Four or so systems, in at least two different locations, capable of handling + modern anti-spam software. This probably needs a bit of CPU. +* remote management stuff + +Proposers: + +* Martin Zobel-Helas +* Stephen Gran + +We probably have sufficient hardware for this. Current plan involves using one +new box from HP, murphy, a new old sparc that zobel gets from some place, and +puccini that will soon no longer have packages on it. + +Status (2009-05-02): + +We probably still eventually want to move to a more cenralized setup for all +the low-traffic leaf-sites, but momentum on the Big Mail Setup Change seems +to have pretty much died. Since Stephen put quite a lot of work into making +our exim setup more readable, maintainable and we are using the same config now +everywhere, at least some of the reasons for this proposal are no longer valid. +It still might make sense to eventually move @debian.org mail from master to a new +system but we don't need 4 dedicated hosts for that, probably. (weasel) + +== new bugs.d.o == + +Currently bugs runs on a single DL385g1 system which cannot keep up with the +load that the BTS causes. + +Owner@bugs would like to split the BTS accross multiple hosts: two for incoming +email and spam filtering (would not be required if we had the setup mentioned +above), one master, and at least two user-facing web servers. + +Requirements (assuming the above mentioned mail system is in place, else add +two mail servers): + +* two systems with fast disks (we don't need that much storage, some 200 gigs + should suffice easily for a while - say 4x140 gig raid10), some ram for + caching (say 16g?), and the CPU to handle the scripts (if we can get two quad + cores per box that would be great). +* one master that processes incoming email, changing bugs as required, and + pushes the changes to the web facing servers. + +Proposers: + +* Don Armstrong + +If the snapshot hosts go through we might be able to put the bugs front end +webservers on them too. Probably a question of load but it can't hardly be +worse than rietz at the moment. + +Status (2009-05-04): + +We were quite successful in using other hosts as bugs web mirrors (even if +right now we aren't running any due to other hardware failing), so that is +a more or less solved problem. We also intent to move bugs-master to a kvm +domain at ubc/ece once the blade there is fixed. And we can probably move +incoming MX to a blade instance in darmstadt and another one at the same +place as new bugs-master will be if the bugs folks still want that.