Re: [tools-dev] requirements for a Windows build bot and cws box
Martin Hollmichel wrote: Hi, finally I come to the following proposal: 1 virtual machine running a Windows7 64bit instance with Visual Studio Standard installed for the Windows tinderbox. 2 additional virtual windows machines available for Developers, with the Express Version installed. In case we discover that we need more parallel sessions available, we consider the installation of Windows Server. the Virtual Boxes will be hosted on a Quad Core, 12 GB RAM machine in a data center any comments ? Martin http://wiki.services.openoffice.org/wiki/Community_Council/Funding_And_Budgets/Developer/WindowsBox#Proposal_for_a_Windows_Box Pavel, Thorsten, you may want to comment or approve these spendings for the developer budget ? Martin Martin Hollmichel wrote: All, I got a request to do some funding for a Windows build bot (to be funded be the OOo project, not by Sun as my mail adress suggest). build bots are now integrated in the EIS and are of invaluable help for development and QA. I can think of several scenarios: minimal buildbot: a virtual windows (home) instance on some already existent hardware plus a MS Compiler professional license (estimated cost: ca. 1000 € once). fast build bot: windows box on bare iron or virtualized in a hosting center with good bandwidth for providing install sets (my estimated extra costs: ca. 1200 € per year extra) fast developer machine: windows server allowing up to five 5 users, allowing remove building and debugging for developers with no windows access, several build bot instances (i have no real idea for the estimated hosting and license costs). Two questions: * what are our real demands and requirement for such a thing. * is there anyone volunteering for collecting real prices and costs for the various scenarios and maintaining the resulting setup ? Martin - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
Re: [tools-dev] requirements for a Windows build bot and cws box
Hi, 900 € per year sounds reasonable compared to the price for - buying an equivalent machine - rooming - power - bandwith - hardware repairs / upgrades now I understand. The price of 69EUR is not for a hosting only, but for hosting and rent of the hardware. Hmm, then big +1 for the proposal. In our country we strongly separate hosting of own server in the computing center and renting already hosted server owned by the hosting company (either physical or virtual). -- Pavel Janík - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
Re: [tools-dev] requirements for a Windows build bot and cws box
Martin Hollmichel wrote: Pavel, Thorsten, you may want to comment or approve these spendings for the developer budget ? +1 for the Windows box/server. We desperately need communi Windows machine. I;d go with terminal services directly from the beginning. -1 for the regular yearly payment for the hosting services. Can we do it better/cheeper? Can anyone offer/sponsor this service for us? please keep in mind that this yearly payment includes 100MBit and unlimitted traffic, that also will allow the download of builded cws, I think it's worth the price, but I'm open for better or cheaper offers, how long we want to wait for those offers ? +1 for the full package; if someone finds a cheaper offer that's of course fine by me. Win32 builds are a pain point for me, and historically the dev budget has not been fully spent, so no point in haggling too much here. What about reviewing the hosting options again next year? Cheers, -- Thorsten pgpIBr6yMwHjZ.pgp Description: PGP signature
Re: [tools-dev] requirements for a Windows build bot and cws box
Pavel Janík wrote, On 01/08/10 15:00: Hi, 900 € per year sounds reasonable compared to the price for - buying an equivalent machine - rooming - power - bandwith - hardware repairs / upgrades now I understand. The price of 69EUR is not for a hosting only, but for hosting and rent of the hardware Well, at least that was my impression by reading the wiki page. Otherwise it would have stated the HW costs, and not only the licensing costs. Martin might correct me in case my interpretation was wrong. Malte. . Hmm, then big +1 for the proposal. In our country we strongly separate hosting of own server in the computing center and renting already hosted server owned by the hosting company (either physical or virtual). - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
RE: [tools-dev] requirements for a Windows build bot and cws box
If you are going to do the build bot as a virtual machine, would it be possible to make the VM image(s) available to third parties? We redistribute OpenOffice with our product unmodified. We download a copy of the source for the version we are redistributing so that we can be in compliance with the licensing. Back when 2.x first shipped we tried to get a Windows build going but not having someone who could devote full time to it we spent months working on it off and on but never got it working. It would be a huge help to small companies like us if we could download a VM image of a build environment we could use to build OpenOffice. That way we can be sure that the source we have matches the version we are redistributing. Having a build environment we could work with locally would also make it easier to try and fix any problems we find on our own rather than file a bug report and pray. Thanks. -Original Message- From: martin.hollmic...@sun.com [mailto:martin.hollmic...@sun.com] Sent: Wednesday, October 07, 2009 8:20 AM To: dev@tools.openoffice.org Subject: [tools-dev] requirements for a Windows build bot and cws box All, I got a request to do some funding for a Windows build bot (to be funded be the OOo project, not by Sun as my mail adress suggest). build bots are now integrated in the EIS and are of invaluable help for development and QA. I can think of several scenarios: minimal buildbot: a virtual windows (home) instance on some already existent hardware plus a MS Compiler professional license (estimated cost: ca. 1000 € once). fast build bot: windows box on bare iron or virtualized in a hosting center with good bandwidth for providing install sets (my estimated extra costs: ca. 1200 € per year extra) fast developer machine: windows server allowing up to five 5 users, allowing remove building and debugging for developers with no windows access, several build bot instances (i have no real idea for the estimated hosting and license costs). Two questions: * what are our real demands and requirement for such a thing. * is there anyone volunteering for collecting real prices and costs for the various scenarios and maintaining the resulting setup ? Martin - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
Re: [tools-dev] requirements for a Windows build bot and cws box
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote: On Wed, 07 Oct 2009 15:19:55 +0200 Martin Hollmichel martin.hollmic...@sun.com wrote: All, I got a request to do some funding for a Windows build bot (to be funded be the OOo project, not by Sun as my mail adress suggest). build bots are now integrated in the EIS and are of invaluable help for development and QA. I can think of several scenarios: [...] fast developer machine: windows server allowing up to five 5 users, allowing remove building and debugging for developers with no windows access, several build bot instances (i have no real idea for the estimated hosting and license costs). Two questions: * what are our real demands and requirement for such a thing. * is there anyone volunteering for collecting real prices and costs for the various scenarios and maintaining the resulting setup ? IMHO, mixing buildbots and debugging on one machine is just asking for trouble. If there is a need for both and funding is available those should be two separate boxes (or at least two separate virtual boxes). ok, running the developer machine in a virtual environment should not be the problem. I know it might be tempting for licensing reasons (*) to use just one machine, but I really think it wouldnt work in practice. the main objective is to be in compliance with the licenses, that's why I am asking for reasonable configurations. Once we know about the costs for the various configuration we can decide what will be the most appropriate to choose. Best Regards, Bjoern Martin (*) BTW: Are there even CALs available for Visual Studio? - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
Re: [tools-dev] requirements for a Windows build bot and cws box
Herter, S. wrote: If you are going to do the build bot as a virtual machine, would it be possible to make the VM image(s) available to third parties? In theory this should be possible if you have the required licenses for those images. But I personally have not enough knowledge about the MS technologies if it is possible to ensure that an valid license will be verified for those images. Maybe some expert is around who is able to answer this question ?! We redistribute OpenOffice with our product unmodified. We download a copy of the source for the version we are redistributing so that we can be in compliance with the licensing. Back when 2.x first shipped we tried to get a Windows build going but not having someone who could devote full time to it we spent months working on it off and on but never got it working. It would be a huge help to small companies like us if we could download a VM image of a build environment we could use to build OpenOffice. That way we can be sure that the source we have matches the version we are redistributing. Having a build environment we could work with locally would also make it easier to try and fix any problems we find on our own rather than file a bug report and pray. Thanks. Martin - To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
