>>Generally speaking, our requirements for equipment to be used as >>buildd/porter >> machines are as follows: >> >> * reliability - The stable release manager requires that we operate >> three machines for each port: two buildd machines in different >> locations and one porter machine. These machines must be reliable. > >We already got ipa.debian.net, if David can give more nodes to Debian, >then I think the requirement can be fulfilled.
That we can do! Will I arrange this offline with someone in particular? > >> * out of band management - We require the ability to manage the machines >> independently of their primary network interface: serial console or >> better, remotely-controllable power. > >David, could you also allow Debian admins into IPMI interface? Yup, shouldn¹t be a problem. > >> * supportability - We require that the machines be commercialy available >> (within financial constraints) and that they be supportable through a >> warranty or post-warranty support or are otherwise easy to replace. > >Those machines are selling commercially now. > >> * stability - We require that the machine's architecture have an >> actively-maintained stable kernel in the archive. > >Currently, there is an effort on going, as I explained above, but it >is not yet finished, just starting: > < http://packages.debian.org/unstable/linux-image-3.9-1-armmp > > >> * environment - We require that packages critical for DSA operations be >> available: puppet, samhain, syslog-ng, ferm/pf, etc. > >The armhf port already contains those. > >> We would prefer to house such equipment in one of the data centres >>where we >> have an existing presence (grnet (Greece), man-da (Germany), ubcece >>(Canada)) >> but we are amenable to a discussion regarding having a business host the >> equipment on our behalf as long as the above requirements are met. These will need to remotely accessed - we have a 24 node system that we use for customer to benchmark/test remotely. I can allocate one or two nodes on this but unfortunately couldn't provide a full chassis. In response to some of the other threads, I'll give some of the suggestions a try (kernel 3.9.1) and report back. Thanks, Dave >> >> Please let me know how you'd like to proceed. >> >> And thank you for your offer. It is *only* through the generous >>donation of >> time, equipment and/or funds from businesses and/or individuals such as >> yourself that volunteers are able to make the operating system known as >>Debian. >> >> Thanks again, >> >> Luca >> >> Debian System Administration Team >> Debian Hardware Donations Team >> >> -- >> Luca Filipozzi >> http://www.crowdrise.com/SupportDebian > >Regards, >-- > Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. > > Debian ARM porter > Debian ARM buildd admin > DISCLAIMER: The information contained in this email is confidential and may be legally privileged. It is intended solely for the addressee and access by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our customers, any information contained in this e-mail is subject to our standard terms and conditions. The views in this email may not necessarily reflect the views of the company. Please note that Boston uses the services of credit insurance agencies and cheque guarantee companies, therefore, customer details may be divulged as required by such companies. This information will be stored in their databases and may be exchanged with other credit reference agencies. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cdf33e0d.60309%david.po...@boston.co.uk
